Macrium Reflect

If it saw the v5.3 images, it was a v5.3 version on the created RE... v6 *CANNOT SEE* v5.3 images. Methinks you got what I did when trying to create a RE under the v6 TRIAL... a v5.3 image on the RE.

Thanks for the heads up!

 

Well... I have continued on a bit with my testing of the (slightly brain dead) TRIAL

Since I cannot test the RDR capability on my SYSTEM volume (no BOOT support for the v6 RE in the TRIAL or v6 RE creation of a RECOVERY MEDIA <only v5.3>), I've played with non-SYSTEM volumes and simple image changes (19.2 compressed partition BASELINE, 1gB removed, 1gB added for the INCREMENTAL). The RDR (Delta Restore) has worked very well in either direction, and appears quite quick... this makes it a possible snapshot tool in its emerging role.

I would've liked to test with my installed SSD but due to the above TRIAL limitations that was not possible.

Next... dig in a bit with non-LIVE file structure changes (PE-based) and see if Macrium's RDR picks everything up as expected.

 

Hey guys, I could use some help getting started with MR. On Monday I started a 30 day trial of MRpro v5.3.7277, at which time I made a full image of my C-drive. At that time I noticed it defaulted to creating an XML file (on my C-drive), which I chose to not do. What's the benefit of doing that?

Furthermore, I thought I would make an incremental or differential image today but it's not clear to me how to do that?

 

As expected, all changes made outside the purview of the LIVE Windows system were discovered nicely by Macrium's "file changes" search prior to imaging and imaged accordingly. But please remember, these are changes made legitimately through the Windows on disk file structure (via a PE-based running environment) rather than direct surface data modification that can be made outside of these types of controls (Direct disk I/O).

So far, RAPID DATA RESTORE looks very promising as far as speeding up recoveries are concerned, and especially promising in the similar arena of HOT restores (snapshotting operations) to non-SYSTEM volumes. I suspect that when I get to test the licensed version of the WARM restore of LIVE SYSTEM volumes, the restore operations, other than the time it takes to BOOT into the restore environment, should be very similar.

Off to play with SCHEDULING and FOREVER INCREMENTALS...

 

Scott, that XML file remembers all the specs of your initial BASELINE image so you don't have to redirect Macrium each time. Using the "Backup Definitiion" TAB under Backup would have allowed you to <right-click> on that definition file and select "Run now/<whatever type of operation you want>." This way you don't have to redefine your SOURCE/DESTINATION partitions or any other specs each time you do a backup.

 

Are you sure you guys a testing with the very latest build? v6 has not been released officially...

 

Ahhhh, apparently you've never used website scrubbers before (entire sites may be scanned for interesting information)... and don't ask

 

Hmm, that all seems kind of convoluted to me, compared to other imagers that present simple menu-selection (or check box) for making a full/incr/diff image.

 

Perhaps, but how come other imagers don't need to do that? And since the XML file is on the C-drive what value is it if the C-drive isn't bootable?

 

Xml is needed if you schedule backup. Restore can be done without xml file as long as you have access to image backup.

 

Scott, when you get to the window where it asks about creating the XML and running the image, you may, at that point, tell Macrium wherever you'd like that XML file managed... it doesn't have to be on the SYSTEM volume (although it's nice to know that they'll be backed up whenever the system is).

 

If the C: drive isn't BOOTable, you'll be BOOTing from the RECOVERY MEDIA, selecting a backup to restore (from where you saved them) and restoring it... what else do you need to know at that point?

If you're gonna use the RECOVERY MEDIA to "manage" your images, and for some reason that XML is unavailable, you can use the RESTORE pane, select the last incremental, select other options and make whatever kind of image you wish. There's nothing really missing here...

 

Ok, but it still seems like an extra procedure (and file) that other imagers don't require. I've just been using the MR trial for a few days to see what it has that makes it so popular around here of late ...and so far I don't get it.

 

Well... for me personally, it's one of the most reliable imagers I have ever used (and I have used a few). I have found it to have have one of the fastest INCREMENTAL imaging capabilities around.

Of late, the excitement is mostly around the imminent v6 release, which will have one of the fastest restore operations among current imaging applications, and some excellent scheduling features which many data center managers require in their system management.

As far as the XML is concerned, it contains all the specs of your original imaging operation, which may be different for different volumes. To be able to simply select that set of specs then ask it to FULL/INCREMENTAL/DIFFERENTIAL what it already knows (the partition in question, selected compression, validate or not, etc., etc.) seems really simple to me. I don't even have to go find the stored partition image (which you can do also in the RESTORATION environment) to do this... the XML knows.

 

Scott that xml file is actually one of the strong points of Macrium. One example: You want to take incrementals but you do not want to schedule them. Just place a shortcut of that xml file on the desktop and when you want to create another incremental, you simple doubleclick the shortcut... and you go to prepare a coffee.

Panagiotis

 

If the XML is so useful in the MR scheme of things it seems to me they should just create the XML automatically (without prompting) and store it in the same drive/folder as the image file!

 

I agree. Storing it by default in folder where image is saved would be better solution. Creating it automatically wouldn't be better for all users, so it could be an option in settings.

 

All imagers save backup job parameters in some way somewhere. If not an XML, then something else. Macrium is not the only one.

 

Right, but most of, if not all of the others do not prompt you to create it with every full image and they automatically save it along with the full image, wherever that may be.

 

It's up to you if you want to save the job or not. You don't have to. If you think that alone is a major failure of Macrium, then don't use it.

 

Scott, remember... if you use the XML (I <right-click> on it in the "Backup/Backup Definition Files" area and select the "Run Now" function) you can do any kind of image based on the original (FULL, INCREMENTAL/DIFFERENTAIL) that you like... without any additional dialogue.

 

Marc, please understand that I'm just a new trial user trying to decide if MR is right for me.