The MX100 had a firmware bug a while ago, not sure if this matters, but you could update the firmware of your MX100 and try again.
Thanks Oliverjia, I didn't think of checking that. Guess that's why Wilders is Crucial ( a tiny slight pun intended) for the important tid bits of wisdom and knowledge. I'll give it a try, I bought the drives in June 2014 but wasn't in a hurry to make the switch, my bad.
Hi Barry (bgoodman) After your voiced concern re incremental chains, I ran another test. But first test background. I run on a midlevel gaming machine, with 3 internal drives, so tests are from internal to internal drives. Drive c: is 1tb and has about 125gb in use. 80% of the files don't change much. Full image time is 15 minutes, and restore time is about 5:51. Incrementals take on average 1 minute. I had a chain started that was about 7 files, a mix of incrementals and differentals. I switched it to incrementals and let it take incrementals until last night when I had 41 incrementals. Last night I did a restore, and it was perfect taking 5 minutes 56 seconds. So I would say if you take care not to do anything to damage the chain, and occasionally run chkdsk to check on your file system you should be fine.
I am using FREE but wonder why Macrium suggests using the default name for the Image file? I always uncheck that option and make the file mean something like Before Installing RCForb Software. Then, if I do need to restore I know just what the image was for. OH, before anyone asks it is a Ham Radio Software package.
Well... if you use your favorite name, when your GFS or other AUTOMATIC sheduling system is at work, and it's time to image another FULL, that really can't be done (as I see the naming) properly as all that's available is the "-<nn>-<nn>" part of the naming convention. New FULLs need different names so that follow-on DIFs and INCs can be named accordingly. I haven't tested what happens when you do this... but I'm sure I will.
Well... I just quickly tested it and when you use your own personal FileName for the images, Macrium just indexes that personal name when it needs to generate a new FULL image in your retention schedule, as in... Froggie-00-00 Froggie1-00-00 Froggie2-00-00
Well, since I ONLY do full images (only takes 4 minutes) I can keep doing what I have been doing. OH, and a restore is only 4 minutes, if that long.
MSPAN, I'm a bit curious here... Since you only do FULL images and RESTOREs, what is it that Macrium offers you over other imagers that do FULL images and RESTORES?
Some time ago I installed Macrium V5 Pro but found it so counter-intuitive that I gave up and retreated back to old faithful DS and SP. The release of Macrium V6 with all the positive feedback I am seeing has made me re-visit V5 to try to make sense of it again. Despite having read everything I can find on the Macrium website, and watching the videos too, I have the following questions:- 1. I wish to create a "definition file" for a DIFFERENTIAL image of an existing FULL image. No problem actually making a Diff image when using the Full Definition file by selecting the Diff option, but I want a Diff Definition file which appends itself to the original Full image so that I have a separate Def file from the Full image Def file. I know it must be pretty obvious to others, but I fail to do it. 2. The other thing that I can not find, is when booting from the recovery environment, I see no option to take a Diff image on the screen. Is a Diff only possible within Windows? 3. I also use AX64 V1 without too many problems. Is there anything I should be aware of if using Macrium as an imaging solution with AX64? Many thanks for any help, and Im sure I am missing something very simple.
KennyBoy, the concept of a DEFINITION files does not include the type of imaging your doing... only the specifications of the storage being backed up with any special options selected, any scheduling specs and the retention specs. It is set up that way so that you can do any type of imaging (FULL, DIFFERENTIAL or INCREMENTAL) against that specification. That said, if you're in the "Backup Definition Files" TAB, you may select the DEF you would like to use, then use the "Create a desktop shortcut" tool from the toolbar to create what you need. During the creation process, it will ask you what type of image you'd like to perform (you choose) then it will create on your desktop a shortcut to do that very operation. Feel free to put that shortcut wherever you'd like to use it (I put it on my START menu/screen to use it as a one time operation when needed). The other two options on that toolbar, PowerShell and VBscripts, may do something similar (I don't use them) but you may have to edit the created scripts when done to do exactly what you want (type of backup). I believe that's true. The WinPE environment is meant primarily for recovery (restoration) purposes but offers the ability to take a FULL image in case you want to have access to the last CURRENT STATE of your system prior to the needed recovery. People usually use this feature to chase down files that may exist between the last snapshot and when the recovery is required. The WinPE is not meant to be a full standalone imaging system although it can image your system in an emergency. No problems... I do the very same. That being said, I find the Macrium RAPID DATA RESTORE (RDR) feature to be just as adequate as AX64's v2 WARM restore, and taking just a bit more time than AX64's HOT restore in v1. For me, Macrium's RDR has proven to be waaaay more reliable than AX64 in any type of restore operation.
I agree about the reliability. Read thru this thread, and you find several of us beat on this product before release. Did some absurd tests, and all passed with flying colors. It's true the hot restores of AX64 are super fast, but for the advantage is lost in the number times the AX64 tracking file got broken, and AX64 had to do full images. Not an issue with Macrium.
Well it seems that Macrium Reflect can't save me from my own stupidity... Using Windows 10 TP 9926 and got an automatic update to Windows 10 TP build 10041 or something like that... That update switched the Windows installation to UEFI which in turn created a new partition on my drive, the update also removed all my pinned applications on the start menu, so I made an image and went back to an image from build 9926, what I didn't realize is that my backup definition didn't backup this new partition meaning I didn't get the necessary boot stuffs, so when I tried to go back to build 10041... disaster... I'll give it that it at least let me go back to latest image of build 9923 so that I can do the update to build 10041 again.... I think that was a terrible re-telling of what happened, more concise: 1. Imaged build 9926 with only one partition. 2. Updated to build 10041 which switched the installation to UEFI and created another partition for boot stuffs (so 2 partitions now) 3. Create a new image but since my backup definition only had the first partition marked it didn't backup the second partition created in (2). 4. Restored back and forth and when tried to restore it didn't restore the second partition since it was never backed up which resulted in a broken boot... Fun times.... 5. Boot into macrium and restored image from (1) and redoing update now... So that was a lesson... Btw I freaking hate Windows... It seriously can't remember the Start Menu desktop applications when updating but it can remember the modern apps? Bull freaking ****, that's 100% intentional to freaking piss you off.
Strange I just updated my VM with win 10 and I didn't get that new build. Where did you get that build, full dvd or windows udpates.
Through the "new" modern settings screen, go to updates and make sure build updates are set to fast, then search for updates, should find "fbl_impressive 10041 Professional." Edit: Blech, horrible update experience there, it forced installed newer Nvidia Drivers which doesn't let you choose what components to install so it installed the 3D drivers (which f**ked up quite a lot) and then it also quite literally broke Spotify... out of all applications... And now I get this window at every start-up (See screenshot) anyone know how to get rid of it permanently?
"fbl_impressive " This name makes me puke. Yes their products are so impressive that I, and many have switched to Ubuntu. Keep boasting and you'll be gaining more market share, MS.
Myeeh I prefer giving Windows a taste of its own medicine, it it wants to forcefully install newer Nvidia drivers, then I will forcefully block that and keep my old ones, re-installation of Spotify fixed my issues and using Comodo Internet Security with HIPS to block the application that shows that window in the screenshot also worked quite well... I like to find solutions to problems, but that doesn't mean I don't get annoyed when problems appear. I'm also quite aware that I'm using an unfinished preview as my main OS and I accept the consequences that may follow. Although at this point I've pulled us off-topic, so I'm dropping this subject.
Just curious... what are the major differences between versions 5 and 6? I've used Reflect for years and have a license for what was called "Pro." Not sure they have 'Pro' anymore. Looks like it might now be either "Home" or "Workstation" -- not sure which one??
Tom, both of the new "models" (Home and Workstation) have exactly the same features (basically same as the old PRO)... the difference is the new SUPPORT models used to assist the license holder. The new v6 FREE edition hasn't been released yet (I think they're still trying to determine what features will be in there as well as not affect their initial sales efforts) As far as features are concerned, the two most outstanding (different) are the new RAPID DATA RESTORE (RDR) and the enhanced scheduling features. When using RDR during a restore operation, only the differences between where you are and the time point you're going to are restored. V5 would restore everything from the beginning of the Baseline to the current time point. The change provides for a huge difference in restoration time (unless you're restoring the image to a new volume, then of course, you need everything). The new scheduling system provides for some neat modes of backup management including a typical GRANDFATHER FATHER SON (GFS) model and incrementals that can merge themselves forward. I can't get into to much more detail but their v6 on-line User's Guide may help a bit.
