Macrium Reflect

is right that before a restore there are few second to cancel it?

the log is always save inside the system reserved partition

and i hope RDR is 100% safe !

for example for terabyte team write changed sector only was 100% safe for all the drive, after they found out that doesn't work with some drive

 

Hello,

A new update has been released, version 6.0.753:
Download Page: http://www.macrium.com/Download.aspx?type=home
Release Notes: http://updates.macrium.com/reflect/v6/v6.0.753/details6.0.753.htm

 

Yes, just updated OK and created new Rescue Media with v6 FREE as well.

 

I really like this feature. Unfortunately it does not offer the native resolution of my flat screen (2560x1440; they do offer 1900x1440 though).

How do they determine what kind of resolutions to show? How can I ask them to change that? (If technically possible with "default" video drivers?)

(I'm a paying customer, but I don't have created an account on their support forum yet; is there another way to do this?)

 

Macrium are very generous with their free versions of Reflect.

 

I absolutely agree with you!

 

Welcome to viBoot!
July 22, 2015 Saul Painter
As our latest version of Macrium Reflect continues to get rave reviews in the marketplace, we’re excited to add a new tool to the family, with Macrium viBoot.

viBoot enables you to instantly create, start and manage Microsoft Hyper-V virtual machines using one or more Macrium Reflect image files as the basis of the virtual machine sub-system. viBoot allows you to boot into the images you have made using Macrium Reflect for recovery validation purposes, or as a DR tool to instantly recover vital systems. If you’re working at an enterprise level, you could recover your vital Exchange or SQL systems in mere minutes! This will ensure no down time and no lengthy virtual disk conversion or restore. We’re here to make your lives easier!

We have built Macrium viBoot on a new device driver that presents a virtual Windows drive contained within a Macrium Reflect image file as a physical hard drive to the Windows storage sub-system. This allows any Windows based virtualization software that can boot from a physical drive, to boot from Macrium Reflect image files.

There are a number of ways that viBoot could be utilised. Use it to create a copy of your live environment to test new software, or use it as a performance test platform as part of your Physical to Virtual rollout strategy. Most importantly it enables IT administrators to quickly recover and make available critical systems for business continuity purposes.

You can download Macrium viBoot now from http://www.macrium.com/viboot.aspx
For more information on downloading, setting repository folders etc, please visit http://knowledgebase.macrium.com/display/KNOW/Macrium viBoot

 

Doesn't appear to be working in Windows 10

https://i.imgur.com/CIUqCMW.png

 

Did my first C drive restore since moving to version 6. I was shocked! 85 GB on my SSD drive restored in 3.5 minutes! Obviously only updating the changes. But still, WOW!!

 

sadly the support even the forum is for client only
i 'm testing it right now , i would like to have to possibility to have the feature to select the place (folder or drive) the log file

 

Mantra, send Macrium support an email about your question, tell them that you are a free version user but you are thinking of upgrading to the paid version. Then tell them about this log file concern that is preventing you from doing that. I am 110% sure they will respond.

By the way, do you know how you got the log file? I mean did you just do a restore or was the log file created when you made the WinPE RE from Macrium. The reason I ask is that I recently did an RDR restore and no log file was created on my C drive. But I do remember a log file there a few weeks ago (I manually deleted it immediately), but I cannot remember what I did that resulted in the creation of the log file.

 

^Peter, I don't think mantra is talking about those logs. Those logs are created inside C:\ProgramData\Macrium\Reflect\ and they can be configured from inside Macrium to be purged after 1 day. Mantra is talking about a txt file that is left on the C partition, SRP for him. I remember seeing this log file on my C partition and I remember manually deleting it. I have not seen it since and cannot remember how it was created.

 

Just wondering if you do a backup and have chosen to have it validated as part of the backup- can you abort during validation? Will the newly created image still be there and be fine or does the abort affect everything? Only asking because I am using Macrium free today for the backup of a drive of data (huge) and did not consider how much longer this would take than on a normal OS drive.

 

The image remains in place, unvalidated, following a VALIDATION cancellation.

 

Then the log file should have been created on the root of your C drive. I think the log file is only created when you make a Macrium RE.

 

Froggie, thanks for that. Just wanted to ensure that the image is actually created in this case as the validation process is happening as part of the imaging. I did wait for it to end and did not test it, so was just curious. I understand that if a validation on its own is cancelled, then that would/should only affect the validation process but thought if you askfor validation in the original backup process, then any cancellation might have voided the whole process including image creation.

 

B... I've the validation many times without issue (except a failed log entry for the operation)

 

Validation process is only for ensuring the peace of mind of the user. It has no effect on the image. If the image file was created and you can see it in the destination folder, then everything is fine. Just cancelling the validation does not do anything to the image file.

By the way, I have never validated any of the Macrium images, and as I have been imaging and restoring with Macrium for the last 5+ years, and nothing untoward has happened, so I do not recommend wasting time running validation of your images.

 

Validation is not a check of whether you have a good backup file. It's a check of whether your hardware will be able to restore the backup file. The Validate option "serves primarily to catch errors that occur between the system memory and the target drive. This includes the CPU, mainboard caches, data cables, the IDE/SATA/USB/IEEE 1394 controller, and the target drive itself."

The main cause of failed restores is bad RAM and this should be caught by a Validate.