A Few Macrium Reflect Questions

[RolandJS]

I got lost because I need more coffee! Somebody mentioned paths to where the backup image files are being placed. If I remember correctly, the rescue media created for DVDs or for USB sticks "cares not" about storing the paths. When booted, the provided menu asks user to tree-climb to where the backup files are located and then indicate where does the user want to restore said backup image file. And, if one makes a MR7 report of a specific backup, one can still override the pointers.

 

[BuckSkin]

I am going to get a bit further into this Macrium imaging business and set it up to run on a schedule.
This may be a silly question, actually two; does it make any difference if I have open programs when the backup is run; and, if I am editing photos or such and it decides to run the backup, will what I may be doing affect the backup and vice-versa ?
I have been manually running differential backups and have to dig up and read the instructions every time; I thought it might be easier to just let it do it's thing.

Thanks for reading and all help is appreciated.

 

[ian50]

BuckSpin


>"does it make any difference if I have open programs when the backup is run; and, if I am editing photos or such and it decides to run the backup, will what I may be doing affect the backup and vice-versa ?"


I've used both Macrium and Aoemi to recover from disk maelstroms. Previously I used Acronis with Win2k and WinXT. I backup with both Macrium and Aoemi (Win7) every 2 weeks now on a differential basis. I use external disks to store the backup files on, not networked disks, because I don't trust the broadband connection not to drop out before restore is completed (ponder on the stress if that happens). Sure, the external disks can also go down, but less likely than broadband connections, and at what point do we have enough redundancy ? I suppose you could trust "The Cloud".



Apart from not using network backup, both Macrium and Aomei have performed perfectly for some years now.


Yes, you may set the backup imaging in process with either programme and continue working on something else entirely without worry about corruption. I do that all the time, it's one of the nicest features of backup imaging. This works with scheduled backups too.



I can't tell you which version of some file you were editing at the time of backup is saved within the backup - that is decided when the backup process reaches that particular file set for compiling into the backup record. When the backup image is completed, you can inspect the image file by mounting it (either Macrium or Aomei do this) and examining the file you were editing at the time.

 

[BuckSkin]

Yes, you may set the backup imaging in process with either programme and continue working on something else entirely without worry about corruption. I do that all the time, it's one of the nicest features of backup imaging. This works with scheduled backups too.

Thanks for that; it is what I was hoping for.

I recently had a HDD in a laptop just die in the middle of the road (not this machine).

I had played around with Macrium a couple years before the catastrophe and miraculously had saved an image of the laptop.
I installed a new SSD, popped in the Macrium Rescue Disc that I had previously made, found the backup image, and set it to work.
When it was done, the laptop booted up as if nothing had ever happened.
There were a couple programs I had added during the interim that I had to reinstall; other than that, it was as good as ever.
All the photos were backed up in so many places that I didn't lose a thing.
That episode gave me a lot of confidence in Macrium.

I did use to use AOMEI, but I had some headaches trying to deal with some problems I was having and lost confidence in it.
I did, however, manage to clone several disks with AOMEI that worked perfectly.

 

[RolandJS]

"...have open programs when the backup is run; and, if I am editing photos or such..."
VSS normally smooths things over during backup operation.