Hello I am using the free version and backing up to a USB 3 Ultra USB stick. Since I still really don't know much about Macruim I am wondering about something. Not sure I will explain it right but I have a screen shot of images. I have only manually created two that I know of and wondering where the rest came from since I always remove the stick after recovery ? never leave it plugged in. yes I am a very newbie when it come to this. can somebody help me understand what I am looking at please? and I don't see anymore since 5/15/2016 edit: I have used the oldest backup about three times from 5/15 Also most backups were about the same size except for the last one on 5/15 was way smaller.
Boredog, those images have been created by an automatic scheduler that, apparently, you selected when you created your image DEFINITION file. If you only want to create MANUAL images only, you must edit your created imaging definition and remove all the scheduling entries.
ok but what bi am saying is I did not have the usb stick inserted for another backups, so where did they come from?
What I see are FOUR distinct backups, broken up into small pieces. The reason they're brolen up is most likely that your stick is formatted to FAT32 which only allows a file size slightly larger than 4gB. If the Reflect backup image is larger than that, it will create 4+gB pieces to complete the backup. I see at least four of them like that. If this stick was created as a Recovery Media, I believe it asks to have that media formatted to FAT32. If it's only a place to keep images and not use as a Recovery Media... it may be reformatted to NTFS at which point there will be no image size limitations. Not to worry, though... all those backups, even in their multiple piece form, are fully recognizable and usable by Reflect. PS- your 5/15 backup was much LARGER than the previous ones... and it is the NEWEST of the backups, not the oldest.
Thank you that makes sense. I did create it as the recovery media. although I got hit by a fake Trojan yesterday and had the dang stick in at the time. only time I get hit and I have the stick in. so now not sure it is safe. was strange with all the security software I have and never got a peep. downloaded nod32 later to find the creepy thing.
Given the enthusiasm in this thread, I decided to install MR 6.1.1366 (trial version) on my test computer running Win7(x64)SP1. The installation went smoothly and I created a Win PE 3.1 rescue disk. I next created an image backup of the C-partition and then restored the backup (using the rescue disk), which was totally successful. I next attempted to add the recovery boot menu option, but that failed - as shown below! So I next downloaded/built a Win PE 10 file and successfully created another rescue disk, but again when attempting to add a boot menu option it failed with the same error message! Is the boot menu option not functional in the trial version?
Ok, but I installed the Reflect TRIAL (not the Free version), so I'd like to know if the boot menu option is supported in the TRIAL version (and if so, what could be causing the reported error)?
Frog, I'd truly appreciate your assistance - as trial users are not permitted to post on the MR forums (as you must know).
According to their website: About the Trial Edition All editions of Macrium Reflect can be downloaded for a 30 day trial. The trial is fully functional except that the ReDeploy functionality to restore images to dissimilar hardware is not included. The decision to remove this functionality was made on commercial grounds. http://www.macrium.com/Download.aspx?type=home
JoAnn's FREE edition supports the Local BOOT function without a problem. The error she's getting is happening at the end of creating the special WIM needed for the Local BOOT option... it should work just fine.
JoAnn, what do you see when your run BCDEDIT at an elevated (as Administrator) Command Prompt? Start/All Programs/Accessories/<right-click>Command Prompt (Run as administrator)
Hi Frog, here is a snip of BCDEDIT on the PC that (consistently) reports an error while unmounting the WIM:
Jo Ann, while we're waiting, can you enter the "Add a BOOT menu option" and select "No menu" then "OK" out of that... then try and add a BOOT menu item once again. Lemme know what happens.
Frog, I did what you suggested above, but (unfortunately) it was to no avail - I received the exact same "error while unmounting the WIM". PS. I then disabled the PC's antivirus and again followed your suggestion ...and I still got the very same error!
I haven't done this since upgrading to Windows 10. Peter informed me that I need to do so. I am assuming that I should choose PE10 when I do the re-build?
Alex, you may use any PE you wish, they all work. The advantage with PE10 is a richer driver set for use with all machines.
...and I must add the following caveat. Although PE10 has a much richer driver library available when using it, under the current release from Macrium, there is a bug (see HERE) if you try and mount/browse an existing time point while running under PE10. Macrium is aware of this anomaly and is working diligently with MicroSloth to find a solution. If you need this capability while using your PE, it's best to use PE5 until the offending bug has been isolated and fixed.
bein @JA & TRF, Fwiw, a couple of months ago I incurred and reported (here) the very same error when attempting to add the MR Boot Menu Option (with the Version 6.1.1225 Trial). No one ever replied to my post so I never purchased the product (as I perceived that feature to be of value to me). Btw, I also reported this to Macrium via email, but being a trial user they would not provide any support (a foolish policy imho)!
I'm new to Macrium, I would like to know when backing up an image of Windows, MR suggests to backup all of the partitions on my HD ( 7 of them, see attachment). If I choose only (C) would that be the same? (the difference is not much in terms of GBs, 108 GB and 91 GB). It is on Windows 10, MR 6.1 Free (64 bit) [UEFI]. TIA
Do them all. If you lose that disk, you're gonna need most of them to put it back together. If you're gonna use periodic DIFFERENTIALs to manage the disk, most of those partitions will have very few changes to them so they won't add much heft to a DIFF image... almost all the ongoing changes will come from the Windows (C:\ ) partition.
