Macrium Reflect or Shadow Protect Win 8

For some users it is. For some others it's not.

I have used and purchased every version of ghost from 3.1 to 9 (2003). And tested every later version of ghost. And I also had purchased licenses of acronis TI 8 and 9.
So yes, I know how they perform the file/based restores (ghost actually started as file based imaging app and moved to sector based when symantec acquired powerquest in 2003).
They open the image/archive, then create/format a new partition and in the end they restore the files/permissions (but the user sees only the final result).

Panagiotis

 

You have pointed out that it is inconvenient to SOME users.

I think users do not care it is backup by files or backup by sector, they just want it can be more flexible and convenient to use.
Generally, users do not care the processes, they concern the result.
Macrium Reflect can do something that ShadowProtect cannot do. And some people are needed this, especially when restoring image to SSD.

As I know, if an imaging software is backup by sector, it cannot restore image to smaller partition. I mean the last sector in source partition is greater than the size of target partition.

I think I should say clearly, I am talking Symantec Ghost, not Norton Ghost. It is still backup by files.

 

Andy,

The big disadvantage with file based restores is the files are restored in a compacted state. All squashed together. You have already expressed your dislike of compaction yet you are happy to accept compaction for all image restores, not just for restores to smaller partitions. Some folks prefer to have their OS defragged so recently changed files are in one area of the partition while older files are in another and the page file is in the middle of the partition. This is said to improve performance. Compaction would spoil this layout and a defrag would have to be done after the restore.

With sector based restores you might have to defrag after restoring to a smaller partition but not after restoring to the same sized partition and restores to the same sized partition are by far the majority.

 

Brian,

With file based restore, after restoration partition will not have fragments or just has very few fragments, so need not to defrag again.
HDD is slow, no matter how to allocate the position of sector, still very less in the improvement of performance. If you are using SSD, you need not to defrag.

As I say I do not want to resize/compact/defrag/shrink both source and target partition/image, I just lazy to type too much words. The whole sentence is "I do not want to resize/compact/defrag/shrink source partition/image and I do not want to resize/shrink target partition/image." I think you know it because with file based restore, no compact/defrag is needed.

The disadvantage of sector based imaging is that if you want to make sure your image is more flexible, you may need to resize/compact/defrag/shrink source partition before you make an image. It is in order to gain the least required partition size to restore an image to target partition if you want to restore to smaller partition, especially for SSD.
As for HDD, if your source partition has fragments, you also need to defrag again after image is restored.
If sector based restore can restore to a smaller partition, I think the sector structure will not change, just as the same in the source.

 

I, too, have used Ghost since MSDOS days. That aside, I do not believe even 3.1 was file based... ?? Even if I'm wrong, it would allow you to copy the necessary sectors to make a bootable copy of an OS drive (and later partition even.) I seem to recall these old versions giving the user feedback in sector counts (or something similar) as opposed to file counts.

I remember in order to image or clone a drive you had to create a boot floppy (and later a boot CD) to boot from. That wouldn't have been necessary in the MSDOS days for a file based backup solution. I 'spose I may be thinking pre 3.1 days, I don't recall what version they started using a Windows app. But I don't understand why they'd go backwards from file based to sector based then go back to sector based later on... Windows Ghost versions I've used since the acquisition of PowerQuest (at least) let you set up a "file backup" or an image backup and I've always either assumed or known the image backup is sector based... This document seems to indicate otherwise and, at least as of 2003, you have the choice when imaging to either use a sector by sector backup or a "native backup" which is described thusly: "Native cloning is much faster because Ghost recognizes the file system and clones only the disk structure information and the files."

This page seems to indicate the initial Ghost release could do sector by sector copies too: "Initially, Ghost supported only FAT filesystems directly, but it could also copy (although not resize) other filesystems by performing a sector copy."

If all that's true, you at least taught me something new. When what Ghost refers to as a native cloning process (where file system is recognized and used) it is only a file copy along with the sectors needed for the file system and booting. It makes me wonder if pretty much all cloning programs work the same way.

One thing that confuses me is that I asked Macrium if I used the sector by sector option in Reflect if I could clone or image the hard drive in my Tivo device which uses a proprietary file system. They told me it would not be possible because Reflect needs to be able to parse the partition table and the partition table on the Tivo hard drive isn't recognized by Reflect. (here) I probably show my lack of knowledge by saying I always assumed a sector by sector copy should be able to image a drive regardless of the partition table. I suppose on some level it makes sense that the partition table defines the sector layout though.

Sorry, thinking out loud and am obviously way off topic.

 

Hi Andy,

I agree that users care about convenience, but don't you think they also care about content? I mean you can use a convenient software all you want but if it doesn't backup the content you want then convenience is useless. In this case a byte/sector backup will contain the OS, installed applications, running services, configuration settings, as well as the data. File/folder backups are designed to allow someone to backup specific files/folders (e.g. a user's folder or just the /My Documents sub folder) which is often more useful to home users. Several comments in this thread have discussed how all the home user is doing is backing up family pictures, personal documents, and etc. In this case a file/folder backup provides the necessary content while a byte/sector backup provides the content and more. Convenience would seem to be only an issue of personal preference rather than a performance measurement in this example.

I have to disagree on your second point. An image based backup can restore to the image to a smaller partition. I've written several examples in this thread on exactly how to do this using StorageCraft's ShadowProtect. This is especially useful to home users (and businesses) which upgrade from a HDD to a SSD. When comparing equally priced SSD's and HDD's most people that buy the SSD trade the extra storage an HDD has for the faster performance an SSD has at the same price. This often means buying an SSD with less storage but faster read/write than the existing HDD in the system... and it means that an image-based backup of the existing system will have to fit on a smaller partition on the new SSD. This shows why the ability to easily transfer OS, applications, services and data from a larger HDD to a smaller SSD is important and why an image-based backup that can make this transfer is necessary.

Cheers!

 

Steven,

Imaging software is backup by files does not mean it is backup files/folders only. It can be used to backup an OS partition which is also can be included such as MBR. If you have tried backup by files' imagaing software such as Symantec Ghost or Acronis, I think you will know what I mean beacuse they are not designed for backup specific files/folders only. Therefore, I do not explain more.


As for the second point, I mean restoring image to smaller partition automatically without any manual steps.
Yup, you let me know ShadowProtect's image can be shrink. It seems not many backup by sector imaging software can do this. But it is strange that this process can be done in recovery environment only.

 

Yes, and I also said that it's not for some others.

But users care about the speed. File based imaging is much much slower than sector based imaging. So for the majority of the users sector based imaging is more convenient.
Also during the file based image restores, the apps have to restore correctly:
-the files
-the long file names
-the short file names (8.3)
-the permissions
-the junction points
-the metadata
Have you ever checked all those parameters before and after your restores to see if they really restored an exact image/clone of your system and not a somewhat close replicate?
Acronis, Macrium, norton/symantec (not ghost32.exe or ghost64.exe) and Paragon use sector based imaging for the backups and sector based or file based imaging during the restores (depends from the users settings and/or operations).
Both sector based and file based imaging have their pros and cons. Depends on the situation and what the user is trying to achieve. But for the vast majority of imaging operations sector based is better and faster and this is why almost all the imaging apps use it.
Personally the only imaging app that I trust for file based imaging backups/restores is imageX of microsoft.

Panagiotis

 

I have used Symantec Ghost from Windows XP to Windows 7.
But I do not find any problems.
As Symantec Ghost is slow in speed, therefore, I switch to Acronis.

As for "sector based or file based imaging during the restores", if what you are talking is right, you have pointed out the flexibility and convenience of such imaging software. And it is really what I want! Fast in speed and more flexible and convenience in usage.
But I cannot find any settings and/or operations in Acronis can choose sector based or file based imaging during the restores.

 

Hi Gorkster,

Yes, ghost always supported sector by sector (=copy all sectors) imaging.
Sector based imaging (where the app. reads the partition's filetable and then identifies and copies only the sectors where the files reside + the sectors occupied by the file table structure/files) is very different to sector by sector partition imaging.
About your macrium problem: it seems that (at least at the time) macrium did not support sector by sector disk imaging (=copying the disk as raw).

Panagiotis

 

Hl, Andy.
This is why, I told you in my initial post in the thread, that if you believe that ghost or acronis who offer this ability are superior programs or better suited for you, just use them and move on. No need to keep whining about it because not all imaging programs support it. Not every program is for everyone.
e.g.(1) Shadow Protect excels at fast continuing incrementals and hardware independent restore, for their customers those are the needed/wanted features, not file based restores.
e.g.(2) "Image for Windows" excels in high(extreme?) customization/control over the backups/restores and in compatibility (supports FAT16, FAT32, NTFS, HFS+, Ext2, Ext3, Ext4, ReiserFS, and XFS partitions). Is it for everyone? No. It is ideal for me though, but I do not pretend that all the imaging apps should support all those file systems because for me is convinient.
---end of rant----
In Acronis you cannot control it. It desides automatically what strategy to use when you perform a restore (e.g. when resizing to a smaller partition).

Panagiotis

 

But are you sure this saying is right?
I mean backup OS partition and restore the whole image , not individual files/folders only.

Acronis needs not to resize partition to restore an image to smaller partition.

 

A quick note about a recommendation in an earlier post. UltimateDefrag was suggested. It sounded interesting so I looked. It does not have a Win 8 version.

 

Hi Andylau,

Yes, I've tried imaging software such as Symantec Ghost or Acronis. They use the same technology we offer (and in some cases actually license our snapshot drivers to do it). So I'm very familiar with the benefits of image-based backups vs file/folder backups.

One of the drawbacks to file/folder backups is that they typically don't backup an ACL, byte/sector backups do. This isn't a big deal for home users but it is very important for permissions in any kind of networked environment.

Another drawback is that file/folder backups look at changes at the file level. Again, home users may not care as much, unless they run SQL or do graphic design or basically anything that involves large file sizes. In this example a large file (like a 200MB database, image, or video) would prompt the file/folder backup software to backup the ENTIRE FILE every time a minor change is made. A byte/sector backup will only backup the few changes at the disk level saving a LOT of backup storage and time.

Another drawback is that file/folder backups usually take a flat copy of the files on the system. This makes a bare metal restore difficult because the installed applications, services, configuration and etc will need to be recreated. Most people who use file/folder backups end up creating a vanilla OS install and copy back their files/folders. With an image-based backup you get EVERYTHING making it very easy to recreate your system from the backup disk image file.

There is definitely a difference in the two backup strategies and it's important to know how each works.

As for the needed Recovery Environment, I don't see anything strange about it. It makes complete sense that you would initiate an operating system from a flash drive or CD/DVD so that you could mount your hard disk and manipulate its contents as you shrink it. Most backup solutions out there offer recovery disks for this very purpose.

 

Yes, I am, but as I already said the user has no control over it; Acronis decides automatically what strategy will follow (sector or file) depending form the last sector that contains data and the targeted size of the partition (if the end of the partition is after the last occupied sector it will perform a sector based restore, if the end of the partition is before the last occupied sector it will switch to file base restore).

Restoring to a different size (smaller or larger) = resizing
http://kb.acronis.com/content/2770

Panagiotis

 

You are saying that Macrium is almost as fast as ShadowProtect.
You must then also take the restore time into consideration as well, which apparently is never talked about here. Because here shows that there are substantial differences do exist where ShadowProtect has a big advantage.
A couple of years ago I've tested different backup software (only backup and restore time) including Macrium and ShadowProtect. This showed that ShadowProtect was almost twice as fast to do a restore compared to Macrium.

I have gotta say that I have not bought ShadowProtect because of the high cost and activation issues.
Although I am now in doubt to buy it because apparantly the maintenance renewal is cheap, so you have to pay this high price just one time. Another problem that still exists is of course the activation issues.

 

I agree SP is quicker to restore but in my experience not by a massive amount. Speed of backup is more important IMO as we do more backups than restores. The Macrium recovery CD is certainly quicker to load than SP's.

I appreciate SP has to track changes to make the incrementals so quickly but any shutdowns it doesn't like cause the subsequent incrementals to take much longer.

I do like SP but Macrium seems to works for me.

 

Macrium has improved Reflect's backup and restore time within the past year.

 

Then I'll just have to make time to test this again.

 

I wanted to test Macrium Reflect Pro but it seems impossible to burn a Win Pe 3.1 or Win Pe 4.0 rescue cd with the trial version v5.2.6249.
Macrium Reflect always freezes about the same place. (see http://oi41.tinypic.com/2rw86qt.jpg and waiklog further).
And at the Macrium forum isn't it possible to report any problems for free or trial users.
So I think here it will ends. I think it outrageous that it's impossible for trial users to ask questions or to report problems. Such an attitude leads to the loss of potential customers.

Code:

waiklog:

Beginning Wim build - 19/06/2013 18:58
======================================

Copying PE files from pre-existing install - 19/06/2013 18:58
=============================================================

Looking for Zip file - 19/06/2013 18:58
=======================================

Downloading 328,5 MB of cab files - 19/06/2013 18:58
====================================================


Download to: C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\690b8ac88bc08254d351654d56805aea.cab
Download successful
Extracting 'fil642ac1bd3326d4b59398fe460db370b9' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim'
Deleting 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\690b8ac88bc08254d351654d56805aea.cab'

Download to: C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\5d984200acbde182fd99cbfbe9bad133.cab
Download successful
Extracting 'fil4db617e977c2929fa4a8a113dcc24567' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\Oscdimg\efisys.bin'
Extracting 'fil720cc132fbb53f3bed2e525eb77bdbc1' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\Oscdimg\oscdimg.exe'
Extracting 'fildc9e47de8509317bd346a3f0d9d130ef' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\Oscdimg\etfsboot.com'
Extracting 'filfd757739b60ada6742f727028aa2deb3' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\Oscdimg\efisys_noprompt.bin'
Deleting 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\5d984200acbde182fd99cbfbe9bad133.cab'

Download to: C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\a32918368eba6a062aaaaf73e3618131.cab
Download successful
Extracting 'fil1d6589792bc74325195585467d7a6afa' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\Media\Boot\memtest.exe'
Extracting 'fil2c982ca7ca0ed4898e594265a6b3f029' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\Media\bootmgr'
Extracting 'fil3ae9b0835c65f44ed796fafe895b87c2' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\Media\Boot\bootfix.bin'
Extracting 'fil40d924f19faec94916f6a919809dd149' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\Media\EFI\Microsoft\Boot\BCD'
Extracting 'fil449b5fde9c04d767ff20cb8c473aeaef' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\Media\EFI\Microsoft\Boot\memtest.efi'
Extracting 'fil9723970721c88cd8051382c9e1b62aae' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\Media\Boot\boot.sdi'
Extracting 'fild9193215ee5ca6461e2f3125cc89b346' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\Media\EFI\Boot\bootia32.efi'
Extracting 'file5d936f06cd0619d5a6e62c4f0dce751' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\Media\Boot\BCD'
Extracting 'filf508675f26b225af97accdeeffe018a0' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\Media\bootmgr.efi'
Deleting 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\a32918368eba6a062aaaaf73e3618131.cab'

Download to: C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\3b71855dfae6a44ab353293c119908b8.cab
Download successful
Extracting 'fil10d003e0b604815c724903d7d5f17948' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\folderprovider.dll'
Extracting 'fil1383cec7acc667d6fe43bae6cda11db3' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\dism.exe'
Extracting 'fil4c7d233f9eea93202e3adb1eb34eb93c' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\vhdprovider.dll'
Extracting 'fil50fe5ed8fe7056a37de8f12b782ee8a8' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\dismapi.dll'
Extracting 'fil57267ed4b1db4394c2dc793930bb8f60' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\dismprov.dll'
Extracting 'fil795afb414078cddc4437f68719329960' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\compatprovider.dll'
Extracting 'fil8ae4d5af6e0c129d3d1a01079e1f5335' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\dismcore.dll'
Extracting 'fil907f4817a8e0884cb235732d503884c6' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\imagingprovider.dll'
Extracting 'filc657d2c1a7cfc2d4304919271d4fc310' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\ssshim.dll'
Extracting 'fild149e76604f63fd6ffae127058fbe861' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\dismcoreps.dll'
Extracting 'fild4343079181aacb439ea24e12d34f9b1' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\wimprovider.dll'
Extracting 'filf4f9bbe16df79ad5a89b9bd11405feb9' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\logprovider.dll'
Deleting 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\3b71855dfae6a44ab353293c119908b8.cab'

Download to: C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\56dd07dea070851064af5d29cadfac56.cab
Download successful
Extracting 'fil164a3931a332bff48cf22110bad1673f' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\BCDBoot\bootsect.exe'
Extracting 'filabb9b7b3a769b02985edb9ab34c09e78' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\BCDBoot\bcdboot.exe'
Extracting 'fild2aad929af85a1a6e6a8dbd0889e2695' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\BCDBoot\bcdedit.exe'
Deleting 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\56dd07dea070851064af5d29cadfac56.cab'

Download to: C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\eacac0698d5fa03569c86b25f90113b5.cab
Download successful
Extracting 'fil58c39fa82e233b106f410d7b0be5ac88' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\wimgapi.dll'
Extracting 'fil6e1d5042624c9d5001511df2bfe4c40b' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\imagex.exe'
Extracting 'filc4034ebb53f3674f3f416d3ae1698e86' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\wimserv.exe'
Extracting 'fild279f499c78f937d41b7a8461270cb7f' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\DISM\wimmount.sys'
Deleting 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\eacac0698d5fa03569c86b25f90113b5.cab'

Download to: C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\630e2d20d5f2abcc3403b1d7783db037.cab
Download successful
Extracting 'fil9267dbb482c0a7aad0e660a7e31e93e9' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\BCDBoot\bootsect.exe'
Extracting 'filac4029d3d493e7dec0f6c52c7aed2d38' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\BCDBoot\bcdboot.exe'
Extracting 'filbdfcda1cc4582b6134469eed04bf0301' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\BCDBoot\bcdedit.exe'
Deleting 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\630e2d20d5f2abcc3403b1d7783db037.cab'

Download to: C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\a7eb3390a15bcd2c80a978c75f2dcc4f.cab
Download successful
Extracting 'fil2051206e8159d97acbeca53b2c6b0ae4' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\imagingprovider.dll'
Extracting 'fil23b7bb6723efd36fe466cd8fb59675a7' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimprovider.dll'
Extracting 'fil29a5cb24b27b5cacc29dd1b9e93f60bc' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dismcore.dll'
Extracting 'fil36e598a8fd9aee7b4ac8620ddd36cb08' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dismprov.dll'
Extracting 'fil46c001e61736775ceb28dc21d42dc139' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dismcoreps.dll'
Extracting 'fil4b70f9579a26a772fabf39372c923657' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\ssshim.dll'
Extracting 'fil5df4699ae9e87b34e1bba2136121ea7e' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe'
Extracting 'fil8175a3c715d1482ce03631c5035fc233' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\vhdprovider.dll'
Extracting 'fil8bcd27caf06f979ab8d9dfa9b7fbe3bf' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\folderprovider.dll'
Extracting 'filb69ab73380908496255dd9cfe059370e' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\compatprovider.dll'
Extracting 'file1467cef9b504782cdf6e4e203275454' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dismapi.dll'
Extracting 'file631ed944f2cd40f21aaade0b9273762' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\logprovider.dll'
Deleting 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\a7eb3390a15bcd2c80a978c75f2dcc4f.cab'

Download to: C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\d2611745022d67cf9a7703eb131ca487.cab
Download successful
Extracting 'fil468e14f4b37636acb529da9d11b55362' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimmount.sys'
Extracting 'fil4927034346f01b02536bd958141846b2' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\imagex.exe'
Extracting 'fil56c851945da6dfbb42939c1096ab33b5' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimserv.exe'
Extracting 'filbce32eb05faf5e2ec0537a0ccd32f04e' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll'
Deleting 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Downloads\d2611745022d67cf9a7703eb131ca487.cab'
Loading WimgApi - 19/06/2013 19:05
==================================

Unmounting the Wim - 19/06/2013 19:05
=====================================

CopyPE - 19/06/2013 19:08
=========================

Creating c:\boot\macrium\WADKFiles\media
Creating c:\boot\macrium\WADKFiles\mount
Creating c:\boot\macrium\WADKFiles\fwfiles
Creating c:\boot\macrium\WADKFiles\media\sources
Copying C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\media\ to c:\boot\macrium\WADKFiles\
Copying C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim to c:\boot\macrium\WADKFiles\media\sources\boot.wim
Copying C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\Oscdimg\efisys.bin to c:\boot\macrium\WADKFiles\fwfiles\efisys.bin
Copying C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\x86\Oscdimg\etfsboot.com to c:\boot\macrium\WADKFiles\fwfiles\etfsboot.com
CopyPE complete.

Copying c:\boot\macrium\WADKFiles\fwfiles\etfsboot.com to c:\boot\macrium\WADKFiles\media\boot\etfsboot.com - 19/06/2013 19:08
Copying c:\boot\macrium\WADKFiles\fwfiles\efisys.bin to c:\boot\macrium\WADKFiles\media\boot\efisys.bin - 19/06/2013 19:08
Mounting Wim: mount path c:\boot\macrium\WADKFiles\mount\ - Temp folder 'c:\boot\macrium\WADKFiles\temp\' -  Wim location 'c:\boot\macrium\WADKFiles\media\sources\boot.wim'

Mounting the Wim - 19/06/2013 19:08


Copying the base Wim from 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim' to 'c:\boot\macrium\WADKFiles\media\sources\boot.wim'- 19/06/2013 19:08
===============================================================================================================================================================================================================================================================================

OKCopying 'c:\boot\macrium\WADKFiles\mount\windows\boot\efi\bootmgfw.efi' to 'c:\boot\macrium\WADKFiles\media\bootmgfw.efi'
Copying 'c:\boot\macrium\WADKFiles\mount\windows\boot\efi\bootmgfw.efi' to 'C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86'
FAILED 5
Extracting Macrium PE Files - 19/06/2013 19:10
==============================================

Architecture to copy - X86 TrialCreating file 'c:\boot\macrium\WADKFiles\mount\program files\macrium\launch.exe'SUCCESSCreating file 'c:\boot\macrium\WADKFiles\mount\program files\macrium\aesdll.dll'SUCCESSCreating file 'c:\boot\macrium\WADKFiles\mount\program files\macrium\le5.dll'SUCCESSCreating file 'c:\boot\macrium\WADKFiles\mount\program files\macrium\networkshell.dll'SUCCESSCreating file 'c:\boot\macrium\WADKFiles\mount\program files\macrium\oledlg.dll'SUCCESSCreating file 'c:\boot\macrium\WADKFiles\mount\program files\macrium\peexplorer.exe'SUCCESSCreating file 'c:\boot\macrium\WADKFiles\mount\program files\macrium\textedit.exe'SUCCESSCreating file 'c:\boot\macrium\WADKFiles\mount\program files\macrium\diskrestore.exe'SUCCESSCreating file 'c:\boot\macrium\WADKFiles\mount\program files\macrium\PrimoBurner.dll'SUCCESSCreating file 'c:\boot\macrium\WADKFiles\mount\program files\macrium\taskbar.exe'SUCCESSCreating file 'c:\boot\macrium\WADKFiles\mount\program files\macrium\psmounterex.sys'SUCCESSCreating file 'c:\boot\macrium\WADKFiles\mount\program files\macrium\license.rtf'SUCCESSCreating file 'c:\boot\macrium\WADKFiles\mount\program files\macrium\syntaxedit.ini'SUCCESSCreating file 'c:\boot\macrium\WADKFiles\mount\windows\system32\Winpeshl.ini'SUCCESSCopying file to 'c:\boot\macrium\WADKFiles\mount\program files\macrium\reflect.exe'SUCCESS'"C:\Documents and Settings\All Users\Application Data\Macrium\Reflect\Windows AIK\Tools\Deployment Tools\x86\DISM\dism.exe" /image:c:\boot\macrium\WADKFiles\mount /Add-Driver /driver:"" /forceunsigned' FAILED - Exit Code 0

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.2.9200.16384

Scratch Space : 128MB

The operation completed successfully.
Unmounting the Wim - 19/06/2013 19:10
=====================================

 

I could be wrong but I thought the trial version won't create a WinPE based recovery CD.

They answered lots of questions for me before I made my purchase, you just contact them directly via email.

 

Very true. But the FREE version makes the WinPE recovery USB/CD/DVD. The FREE version lacks the incremental and differential features.

Best regards,

 

@aladdin
Thanks for the clarification. Had I taken the time to look at the screen shot he posted I'd have realized my error.

@ijskonijn
When I create rescue media in Reflect it normally pauses for an abnormally long time at the point in the posted graphic, but it eventually makes it through. I have seen others post a similar problem in the forums and Macrium has gotten them through it. From memory it seems there was another application interfering.

It sounds like you're done, but if not it might be worth your time to contact support at macrium.com directly. I'm guessing that, with the WIM file completely built (as it appears to be at the point your graphic shows you made it to), either rebooting or forcing Reflect to close and restarting it would allow you to create the bootable media since the creation of the WIM file wouldn't be necessary again.

 

Well, I have tried it with the computer to reboot and burned the rescue CD. I've got an working rescue cd, so I've tested the backup and restore time of ShadowProtect and Macrium Reflect Pro.

I don't know what Macrium Reflect has done to improve their software, but I was surprised that there was a clear progress.

I tested my C-partition which is 160 GB, of which is 139 GB used and 21 GB unused space.
ShadowProtect (trial):
- File size after backup: 114 GB
- Time to backup: 00:29:02
- Time to restore: 00:23:53

Macrium Reflect Pro (trial):
- File size after backup: 116 GB
- Time to backup: 00:37:00
- Time to restore: 00:26:36

The difference here is not so big, but for larger partitions (eg large hard drives) the difference is greater. Especially the time for taking a backup, it would take almost two hours longer for a 2 TB drive.
By conversion of the 139 GB (which is the space that was used on the drive), this should give the following for a hard drive of 1 TB and 2 TB (sizes which I own):
ShadowProtect
1 TB backup: 03:28:52
1 TB restore: 02:51:49

2 TB backup: 06:57:44
2 TB restore: 05:43:38

Macrium Reflect Pro
1 TB backup: 04:26:11
1 TB restore: 03:11:22

2 TB backup: 08:52:22
2 TB restore: 06:22:44

 

Thank you for taking the time and sharing your results. I'm surprised to see that big of a difference, actually. But then SP has that background process which always runs in the background to keep track of changes as they occur, whereas Reflect does not. I'm sure that is some of the time for Reflect. I prefer not to have the extra process, myself. I am happy to hear that you've seen an improvement in Reflect vs previous versions!

I know nothing about this, but I've read other peoples' posts that when SP is running it is not as "invisible" as Reflect is. That is something which is also important to me. When Reflect runs, I can easily continue my work with no noticeable slowdown.