The wrong drive letter can be handled if you assign to the drive for the backup, a drive letter versus the end of the alphabet e.g. x/y/z. Windows remembers the drive letters and only changes them when another drive occupies them. Panagiotis
Aigle, this is purely a guess on my part Their initial offering price of $68 is expiring after midnight tonight... and a 20% OFF Coupon floating around the net is also expiring tonight. At that point, I think any initial surge for the "licensed" product will probably be over and Macrium may now consider releasing their FREE version since it probably won't affect their initial sales surge. But when it arrives, you can count on the fact that it will be hamstrung in some way... maybe no INC/DIFF options, probably no Rapid Data Restore, maybe no template scheduling, who knows what else.
Maybe there won't even be a free v6! Anyhoo, all of the MR6 'fanfare' around here has aroused my interest, so I'm now downloading a trial version.
Even when there are quite a few incrementals preceding the one you are restoring? Or are you referring to full & diffs?
I have done 2 restores both to the most recent daily snap and the restore time for each was about 5 min,,,,just saying each system will probably be different.
One of the tests I ran was when I wanted to trial the new Adobe. I have Adobe Acrobat Pro XI on my system. Installed it is a bit over 900mb. The trial of the new Adobe Acrobat DC was right at 1gb. When you install the trial of the new version it uninstalls the old version, so that is a large data swap. I didn't like the trial so I just restored the Incremental I save prior to the whole exercise. That restore was 1:48minutes. That is still remarkable for sure. Now for sure if all you do is one daily and restore it, the time will be longer. The other thing to know pvsurfer, is I have a 1tb c: drive that has 135gb on it. The other thing is the source and destination disk are both internal Pete
With Macrium v6 (and AX64), I've found that it's not the length of the chain that matters, but how old it is. e.g., with Macrium a chain of 30 hourly incrementals that is only 30 hours old takes 2m to restore (on my system). A chain of, say, 2 incrementals also only takes 2m. But if that chain of 30 hourly incrementals is (say) 4 weeks old, and hundreds of hourly incrementals have been taken (with the definition set to retain only the most-recent 30), the restore time will be 4m30s. The same applies to AX64, though possibly to a greater extent - with AX64 I found that a 3 month old chain could take 10-12m to restore (I haven't tested Macrium with such a long chain, but suspect it might not suffer quite as much). I'm not sure why this is, but would love to know - some kind of internal fragmentation perhaps? Personally I've avoided this issue by using a GFS setup - it avoids the slow down in restores, at the expense of needing two baselines.
The time to restore is going to depend on: type of drives: SSD, HDD, USB speed of drives: Sata 2 or 3 / USB 2 or 3 /5400 vs 7200 speed of connection: internal vs external fragmentation: HDD (source/target) size of GB to restore: differentials + incrementals (add up the sizes to get total) There are many combinations of the above, some are fast, some are slow. I keep base + 6 rolling incrementals, incrementals are normally about 220MB but can be larger if installing/updating software.
The feature comparison table on Macrium website has been updated for v6 free for a while now, even though they have not released v6 free yet. You can see which features from v6 paid are included in the free edition and which are not.
...as expected, no template scheduling, no RDR (Rapid Data Restore), no Inremental Forever (or Incremental MERGE), and since there's no mention of INC or DIFF at all (except INC "cloning" = NO), I'm not sure whether those functions are available either. If that's the case, v5 FREE is pretty much the same thing...
I am having problems with M6. This started originally with me moving it from the C drive to G drive. Initially the scheduled backups would not run. In talking to support they said that M6 could not find itself. So then I did a complete uninstall of it and re installed on G drive. That got over the problem. Up to now I have not been using M6 to backup the G drive. I have been trying it today and it gets to about 72% and then comes up with error 1117. This is to a new HD on eSATA. To prove the drive I used Active@ to make the backup and it also stalled at a similar point. I then realised that M6 was still running and after closing that Active@ continued to completion. I have a feeling that this is connected to the original problem in that M6 still thinks it is on C drive. I have cleaned the registry. Removed Macrium in C:\Program Data. Rebooted but still the error persists. I am stuck for ideas now. I am enclosing the latest logs from the failures. Would appreciate some help with this please. Code: Image ID - 4CEEBAC631529AC4 -------------------------------------------------------------------------------- Imaging Summary -------------------------------------------------------------------------------- Auto Verify: N Maximum File Size: Automatic Compression: Medium Password: N Intelligent Copy: Y Power Saving: N Total Selected: 23.43 GB -------------------------------------------------------------------------------- Destination: Backup Type: Full File Name: W:\Macrium\Programs\4CEEBAC631529AC4-00-00.mrimg -------------------------------------------------------------------------------- Operation 1 of 1 Hard Disk: 3 Drive Letter: G File System: NTFS Label: Programs Win 8 SSD Size: 67.89 GB Free: 44.46 GB Used: 23.43 GB -------------------------------------------------------------------------------- Starting Image - Sunday, May 03, 2015 16:15:34 Initializing Destination Drive: New Volume (W:) - Free Space 921.53 GB Free space threshold: Delete oldest backup sets when free space is less than 5.00 GB Creating Volume Snapshot - Please Wait Volume Snapshots Created Analyzing file system on volume G: -------------------------------------------------------------------------------- Saving Partition - Programs Win 8 SSD (G:) Reading File System Bitmap Saving Partition Gathering Windows Events - Please Wait -------------------------------------------------------------------------------- Backup aborted! - Unable to read from disk - Error Code 1117 - The request could not be performed because of an I/O device error. -------------------------------------------------------------------------------- I/O Performance: Read 1.5 Gb/s - Write 695.0 Mb/s Macrium Reflect Home Edition v6.0.567 - 36-Z64Q-H1DJ-PSQZ-SQNA-ZQAP-757MNWN Code: (Gathering writer metadata...) (Waiting for the asynchronous operation to finish...) Initialize writer metadata ... - Get exclude files - Enumerate components - Get file list descriptors - Get database descriptors - Get log descriptors - Get exclude files - Enumerate components - Get file list descriptors - Get database descriptors - Get log descriptors - Get exclude files - Enumerate components - Get file list descriptors - Get database descriptors - Get log descriptors - Get exclude files - Enumerate components - Get exclude files - Enumerate components - Get file list descriptors - Get database descriptors - Get log descriptors - Get exclude files - Enumerate components - Get file list descriptors - Get database descriptors - Get log descriptors - Get exclude files - Enumerate components - Get exclude files - Enumerate components - Get file list descriptors - Get database descriptors - Get log descriptors - Get exclude files - Enumerate components Discover directly excluded components ... - Excluding writer '' since it has no selected components for restore. - Excluding writer '' since it has no selected components for restore. - Excluding writer 'Shadow Copy Optimization Writer' since it has no selected components for restore. - Excluding writer 'BITS Writer' since it has no selected components for restore. - Excluding writer 'MSSearch Service Writer' since it has no selected components for restore. Discover components that reside outside the shadow set ... - Component '\TasksStore' from writer 'Task Scheduler Writer' is excluded from backup (it requires C:\ in the shadow set) - Component '\WriterMetadataStore' from writer 'VSS Metadata Store Writer' is excluded from backup (it requires C:\ in the shadow set) - Component '\PerformanceCounters' from writer 'Performance Counters Writer' is excluded from backup (it requires C:\ in the shadow set) - Component '\Registry' from writer 'Registry Writer' is excluded from backup (it requires C:\ in the shadow set) - Component '\COM+ REGDB' from writer 'COM+ REGDB Writer' is excluded from backup (it requires C:\ in the shadow set) - Component '\WMI' from writer 'WMI Writer' is excluded from backup (it requires C:\ in the shadow set) Discover all excluded components ... Discover excluded writers ... - The writer 'Task Scheduler Writer' is now entirely excluded from the backup: (it does not contain any components that can be potentially included in the backup) - The writer 'VSS Metadata Store Writer' is now entirely excluded from the backup: (it does not contain any components that can be potentially included in the backup) - The writer 'Performance Counters Writer' is now entirely excluded from the backup: (it does not contain any components that can be potentially included in the backup) - The writer 'Registry Writer' is now entirely excluded from the backup: (it does not contain any components that can be potentially included in the backup) - The writer 'COM+ REGDB Writer' is now entirely excluded from the backup: (it does not contain any components that can be potentially included in the backup) - The writer 'WMI Writer' is now entirely excluded from the backup: (it does not contain any components that can be potentially included in the backup) Discover explicitly included components ... Verifying explicitly specified writers/components ... Select explicitly included components ... Creating shadow set {c67beb14-f3df-4772-93c8-8b36ec5b8541} ... - Adding volume \\?\Volume{93c84167-8ec0-11e4-bf2f-806e6f6e6963}\ [G:\] to the shadow set... Preparing for backup ... (Waiting for the asynchronous operation to finish...) (Waiting for the asynchronous operation to finish...) Creating the shadow (DoSnapshotSet) ... (Waiting for the asynchronous operation to finish...) (Waiting for the asynchronous operation to finish...) Shadow copy set succesfully created. Saving the backup components document ... List of created shadow copies: Querying all shadow copies with the SnapshotSetID {c67beb14-f3df-4772-93c8-8b36ec5b8541} ... * SNAPSHOT ID = {ae6d51f2-3a0a-47f9-9334-aeabf1e20e2b} ... - Shadow copy Set: {c67beb14-f3df-4772-93c8-8b36ec5b8541} - Original count of shadow copies = 1 - Original Volume name: \\?\Volume{93c84167-8ec0-11e4-bf2f-806e6f6e6963}\ [G:\] - Creation Time: 03/05/2015 16:15:37 - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2 - Originating machine: David-PC - Service machine: David-PC - Not Exposed - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5} - Attributes: Auto_Release Differential Windows Events ***************************** Date 03/05/2015 16:15:35 Type Error Event 513 Source Microsoft-Windows-CAPI2 Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object. Details: AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol. System Error: Access is denied. .
Maybe you needed to Remove Licence before uninstalling from C and then install on G and input the licence... just a guess. If it's installed on G but thinks it's installed on C then uninstall from G and install on C Then Remove Licence, uninstall from C and install on G etc.
Interesting, but I had to insert the licence code again when reinstalling so that should have coped with that - or not??
Guys, I'm running Windows 7 x86 and I'm going to take my first backup of system partition with Macrium Reflect and I wonder if i should include System Reserved Partition as well or I can simply uncheck it. Are there any pros and cons of including/excluding System Reserved Partition? In another words will I encounter any problems if I don't back it up in the future when I need to restore my C: (system partition)? Sorry if it has been discussed before - I couldn't have found the answer.
I would include it, its not big and you might need it,,,,,like if you have to do a bare metal restore (for example).
