Sweet, muchas gracias, I hope it works when needed... I fear the day my new laptop with W10 arrives...
The following was probably more of a PC issue than a MR issue, however, this is a really active forum so I'll describe it here. I incrementally back up to four drives (this is a good example why you should have more than one), two internal and two external. The first internal and I'll call it my primary one is E (SATA III 6GB) followed by F and then the two USB's G and H. I used to schedule all but now I just do them manually working from H to E. I plugged in G and H but didn't notice when W10 was asking what I wanted to do that it was calling "G" "E," so when I tried to backup to G it could not find it. No matter how many times I plugged "G" back in it was labeling it E and indeed, with it unplugged, when I tried to run the backup to E, it could not see/find it. When all else fails reboot and dang if everything was back to normal. Any theories as to what might have caused this? Thank you!
Well, it has happened again. I went to do a Delta restore to this mornings snap and it took 49 min to complete. The only thing that I did on my PC today was check my e-mails and I reverted because I had an e-mail, apparently from a client, that I was uncomfortable with. I did notice, at the point that MR was checking for changes to my C drive that the next line in the progress description was "Performing Full Copy". Why would it do that? Would this indicate that the snap it was looking at was corrupted? Did it actually do a restore or did it only do a full copy? What do I do now? Not liking this at all.
Barry, it made a decision during the volume examination that it could not do a RDR-type of restore and did a FULL restore instead. It wasn't that any part of the backup chain was in error, there was somthing about the current machine state that it didn't like during the FileSystem comparisons. The machine state after the restoration should be fine. I don't know the criteria it used to make that decision... I have a question in at their Forums to try and find out. When I do, I'll be happy to pass it along.
The only reasons I'm aware of is if the existing partition (Current System State at the time of the RDR request) changed size in some way or the actual FileSystem it was doing the compare against was not the right system (not the same one it had imaged previously). There may be other subtle reasons but I sure don't know what they are. When I hear more I'll be back.
Barry... from the always happy Reflect Developers group... A Full restore will occur if the file system on the restored volume has a different 64 bit creation time stamp, volume length or MFT cluster offset to that in the backup. A full restore may also occur if the target MFT cannot be read for any reason, is corrupt or if the file system is shrunk during the restore. The restore will always err on the side of caution and perform a Full restore. It does seem that in your situation an RDR should have been OK, but it isn't possible to know why this didn't happen without an in depth debug of the process. I'm now trying to find out if there's any way to gather additional information from the Recovery Media when the error occurs to help narrow down the issue... I'll letcha know when I hear something. Suffice it to say your system is just fine following the anomaly.
Thanks for the info Froggie. I must say that the whole thing confuses me since the only thing that I did between the creation of the snap and the restore was to check my e-mails. I don't see how any of the changes you mentioned could have occurred. Anyway the PC seems to be functioning without issue this time whereas the last time it was wonky and I had to go back 3 days to eliminate the problems so thats a good thing.
I received these presentations from Macrium and thought I would share for those who didn't receive them. Interview with Macrium CEO Nick Sills by Manchester Business Radio CEO of Macrium Software Nick Sills in his interview to Manchester Business Radio talks about his personal disaster and gives an insight into Macrium's plans for the future. IPExpo Manchester 2016 - Macrium Software Defence against the Dark Arts - Backup As Part Of Data Security If you did not have a chance to attend IP Expo in Manchester here is a recording of the Macrium seminar "Defence against the Dark Arts. Making backup part of your security strategy". During the seminar Stephen Macpherson, Sales Director at Macrium Software, highlighted the biggest threats to data security and explained how to strengthen your data security with Macrium Reflect.
I followed the suggestions of: http://www.everydaylinuxuser.com/2015/11/how-to-backup-windows-10-safe-way-with.html http://www.howtogeek.com/223139/how-to-create-an-image-of-your-pc-before-upgrading-to-windows-10/ Well, coming from v4 a lot has changed - but has it for the better? We shall see. 1st When choosing Win PE v5 one of the drivers was yellow, when choosing PE v10 it was all good, so I went with this one, downloaded the PE as their MR Package Download couldn't load on my old Vaio and proceeded with the Create bootable rescue media' but USB option was not to be selected. So where did it go? I have only C: drive - 250 crucial SSD. 2nd I went on to the step: Add A Macrium Boot Menu Option and it can be clearly seen during the boot up.. which is great but knowing it will be needed once a year... how do I configure it not to be seen so to speak? 3rd I hit 'image the disc' and pointed the destination folder to the EHDD, creation of which took around an hour. SHould I test it? I am slightly scared it may fail. I used to be a worshipper of the linux never-fail approach of V 4. edit// don't count your chickens... Write operation failed - The semaphore timeout period has expired what now? http://knowledgebase.macrium.com/pages/viewpage.action?pageId=3768432
I use both Macrium and AX64 (version 1). I have MR set for a GFS backup Monday-Friday. However, on Saturday, I wanted to update my Cooking/Recipe program (which is pretty expensive) and on a whim, I did an AX64 backup (not a new chain). Upon updating Cook'N, it wouldn't start. I received an error message. Since this is a paid product, I sent support an email asking for assistance. Of course, being the weekend, they didn't respond until Monday afternoon. By that time, MR had done an automatic incremental backup. The email from the Cook'N support indicated that they have recently changed their support to paid-only support ($15 per month) and can't help me. (I'm beyond pissed.) So, I'm left with a dilemma. Re-install the Cook'N software hoping that it will fix the problem, or reverting to the AX64 save from the weekend. Of course, now it is Tuesday and my machine has run 2 MR backup incrementals since then. I'm looking for suggestions. Will it create a problem for MR if I revert back to a saved AX64 "snapshot"? What will happen to my MR chain? P.S. I'll be posting everywhere I can about how much DVO (the company that sells Cook'N) sucks and I'll be finding an alternative.
Restore your Macrium incremental from Friday (prior to the upgrade), that should get the cooking program back to a working state. If that fixes the problem, you can delete the last two incrementals since they were done when the cooking program wasn't working. Future incrementals will continue just fine. The other option is to restore the AX64 image, if that works you should still delete the Macrium incrementals that were done after the cooking program broke.
You have nothing to lose by reverting using the AX64 image (or trying to reinstall the cooking program for that matter), if it fails you can try using a cold AX64 revert and if for some reason this fails you can still use the image from 3 snaps back from Macrium. Before you delete the 2 intervening MR snaps make sure you have recovered any files that may have been created since the rolled back to snap by mounting the most recent snap as a virtual drive and copying the newer files..
Now I get: 'Macrium Reflect aborted write failed system cannot find the file specified' It's killing me. Absolutely no problems on W7 x64 with v4.2 and here cannot complete a basic task. Here's what it looks like: see the attachment. Perhaps I should only image the #3 NTFS Primary? Do I need all of them? After applying the suggestion : http://knowledgebase.macrium.com/di...ot be performed because of an IO device error It was so close to finishing, but again ABORT and we're nowhere. p.s. I have run chkdsk on both SSD and the external, no errors found. http://kb.macrium.com/KnowledgebaseArticle50215.aspx Help Please
korben, Can you write an Entire Drive image (all partitions) of Disk 1 to Disk 2? Is Disk 2 an internal hard drive? Is this a Win10 OS?
Brian, Thank yo for showing up mate! That's what I have been trying, 4 times already. D2 is External HDD that had been originally installed on my new Dell with W 10 Home and then replaced with Crucial SSD 250GB.
korben, So the original HD is in a USB enclosure. That may be significant. Do you have another USB external HD you can use as a target for your image or another computer you can use as a network target? I suspect a bad external HD.
I have no idea why it took me so much time to figure out this one... Sure I have, an old WD, and you know what? The image has been completed within in 9:21, not 59 minutes and fail like on the new one! That's saying a lot! However, the new image has been cut into 4 parts, but that's logical, right? edit// HGST 1000.2B Health Status GOOD What gives?
Is the HD formatted with FAT32? File size is limited to 4 GB. It's probably the cable or interface that's causing your problem. I'd try a different brand USB enclosure.
Did you transfer the Dell partitions from the HD to the SSD or did you do a fresh Win10 install? If the former, how did you do it?
I hear you. I opted for a different one, slightly more costly, but the guy advised this one saying it should suffice. Now I'm angry at myself. Thankfully I have my image but I'm not satisfied. Anyhow, I wish to thank you from the bottom of my heart fro all the suggestions mate ps. as advised, the techs at the shop did the cloning for me. peace
It looks like they failed to copy the Win10 Recovery partition so you have no Recovery Environment. When Miicrosoft provide the Win10 upgrade in July you will most likely get a 450 MB Recovery partition at the end of the drive. The Win10 partition will be resized 450 MB smaller.
