Error and Destination Full Messages - Incremental Backup


Author
Message
Phlipster
Phlipster
New Member
New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)
Group: Forum Members
Posts: 14, Visits: 35
Good Day All - 

First let me start off with - I'm a novice.  I get a headache when I start trying to figure out all the possible iterations of grandfather-father-son, synthetic back-ups, incremental vs. differential options, etc.

So when I started getting error messages and then the back-ups simply stopped, I was stumped.

First there is a checksum error that has been happening silently for about two months, and I just noticed it when the incremental back-ups stopped.

Then there is the destination out of space error that shouldn't be, since I configured to delete the oldest back-up at 5 GB of remaining space.  Which I figured would be plenty for incremental back-ups.

Here is what I set up, based on my original research on this site:

http://forum.macrium.com/uploads/images/6eb570c7-3f99-4c49-be63-703e.png

Here is the most recent error log:

Macrium Reflect Log

Image ID - 08B238C200A071B3
Imaging Summary

Backup Definition File:c:\users\xxx\documents\reflect\my backup.xml
Auto Verify:Y
Maximum File Size:Automatic
Compression:Medium
Password:N
Intelligent Copy:Y
Power Saving:N
Email On Success:N
Email On Failure:N
Total Selected:528.41 GB

Retention Rules
Rules will be applied to all matching backup sets in the destination folder
Incremental:Retain 30 incremental images
Create a Synthetic Full backup if possible.
Incremental Backups:156 found
Consolidation:Merging '08B238C200A071B3-00-00.mrimg' to '08B238C200A071B3-243-243.mrimg'
Failed: Failed to load 'G:\MacriumBU\08B238C200A071B3-00-00.mrimg' MD5 Checksum Failure - file is corrupt

An error has occurred when reading file 'G:\MacriumBU\08B238C200A071B3-00-00.mrimg'
Process failed
Successfully recovered from failed consolidation

Destination:
Backup Type:Incremental
File Name:Append to recent image in directory 'G:\MacriumBU\'
G:\MacriumBU\08B238C200A071B3-273-273.mrimg

Operation 1 of 2
Hard Disk:2
Drive Letter:N/A
File System:NTFS
Label:System Reserved
Size:100.0 MB
Free:69.6 MB
Used:30.4 MB

Operation 2 of 2
Hard Disk:2
Drive Letter:C
File System:NTFS
Label:
Size:931.41 GB
Free:403.03 GB
Used:528.38 GB

Starting Image - Sunday, March 05, 2017 03:14:26
Initializing
Destination Drive:xxxPassport (GSmile - Free Space 520.3 MB
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
Analyzing file system on volume C:

Saving Partition - System Reserved
Reading File System Bitmap
Looking for changes
Saving Partition

Saving Partition - (CSmile
Reading File System Bitmap
Saving Partition
Verifying '08B238C200A071B3-273-273.mrimg'
Ok. Continuing...
New File: 514 MB08B238C200A071B3-273-273.mrimg
No space on destination.
Gathering Windows Events - Please Wait

Backup aborted! - Timed out waiting for response.

I/O Performance:Read 557.1 Mb/s - Write 592.7 Mb/s

Macrium Reflect Home Edition v6.2.1549 - 
_____________________________________________________________________________
And the VSS Log File:
_____________________________________________________________________________
(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 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 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 ...
Discover all excluded components ...
Discover excluded writers ...
Discover explicitly included components ...
Verifying explicitly specified writers/components ...
Select explicitly included components ...
* Writer 'Task Scheduler Writer':
 - Add component \TasksStore
* Writer 'VSS Metadata Store Writer':
 - Add component \WriterMetadataStore
* Writer 'Performance Counters Writer':
 - Add component \PerformanceCounters
* Writer 'WMI Writer':
 - Add component \WMI
* Writer 'Registry Writer':
 - Add component \Registry
* Writer 'COM+ REGDB Writer':
 - Add component \COM+ REGDB
Creating shadow set {c8a6a2f6-79dd-4cb7-8a9b-770a199a41e3} ...
- Adding volume \\?\Volume{b41c38c6-d98e-11e5-9d99-806e6f6e6963}\ [C:\] 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 {c8a6a2f6-79dd-4cb7-8a9b-770a199a41e3} ...

* SNAPSHOT ID = {10cde2a1-ce4d-4453-905a-42aefad06b04} ...
 - Shadow copy Set: {c8a6a2f6-79dd-4cb7-8a9b-770a199a41e3}
 - Original count of shadow copies = 1
 - Original Volume name: \\?\Volume{b41c38c6-d98e-11e5-9d99-806e6f6e6963}\ [C:\]
 - Creation Time: 3/5/2017 3:20:32 AM
 - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy12
 - Originating machine: xxxFamily
 - Service machine: xxxFamily
 - Not Exposed
 - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
 - Attributes: Auto_Release Differential
_______________________________________________________________________

I'm backing up a 1TB SSHD drive with about 500GB of data to a 2 TB WD Passport USB 3.0 drive.  Windows 7 Ultimate 64 bit latest SP.

Just got the update notification for Macrium so I know the application needs to be updated today.  But this problem has been persisting for a while, both the error message and the destination space problem.

Any assistance would be appreciated.

Phlip
jphughan
jphughan
Most Valuable Professional
Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)
Group: Forum Members
Posts: 2.2K, Visits: 14K
Hey Philip,

Ok, the first red flag is that Reflect is somehow finding 156 Incrementals despite being configured to only retain 30.  My guess is that this is related to the second red flag, namely the Synthetic Full merge failure.  If merges can't happen, then no backups can be deleted without destroying the integrity of the chain, which means your retention rules can't be applied -- "no merge, no purge", so to speak. I'm surprised Reflect is even able to continue creating Incrementals given that it's saying your Full backup (the file name ending 00-00) is corrupt, which is the third red flag -- although Reflect could be determining that AFTER attempting the merge and then rolling the Full back to its pre-merge (and hopefully intact) state.

If it's at all a viable option for you, I would honestly just blow away all of your backups and then manually execute your backup job, which will automatically generate a Full that time and give you a fresh start, since something has obviously gone haywire in your current backup set.  But some additional information for you upfront since this may become relevant even when things start to work as expected: Since you're using Incrementals Forever with Synthetic Fulls, your purge option at 5GB of remaining space will never have any effect.  That option purges entire older backup SETS to free up space, but the CURRENT set is never considered for purging.  An Incrementals Forever with Synthetic Fulls strategy only ever has one backup set, so there are no "older sets" to purge, and it would be dangerous to purge the entire current set and then restart a new Full because if your system died mid-backup, you could be left with no system and no backups. The only way there would ever be an older set with your backup strategy would be if you manually ran a new Full without deleting existing backups, in which case the previous backups would become an older set (and therefore eligible for purging under this option if necessary) and future Incrementals would be built off the new Full.  The normal scenario where that purge option comes into play would be for example if you had a policy to keep 3 Full backups (captured on Monday) and 6 Incrementals (one on each other day of the week).  Let's say you'd accumulated 2 Fulls and 12 total Incrementals (6 built off of each Full), and now your disk is running low on space trying to store that third Full.  In that case, the purge option would delete the oldest Full and all of its child Incrementals (again, that option deletes entire backup SETS) in order to free up space to carry on.  In your case, the answer is simple: If after fixing your 156 Incremental chain you still run into space issues, you would either need to retain fewer Incrementals or get a larger disk. If you opt for the former option, I believe at the first backup job after reducing your retention policy, Reflect will consolidate multiple old backups into the Full in one shot to free up space and become compliant with your new policy. If you don't have enough space to complete a new backup job for that "multi-consolidation" to occur by the time you reduce your retention policy, Macrium offers a standalone Consolidate.exe file you can run to do that yourself as a one-time effort to free up enough space for things to resume as normal, after which Reflect should take care of the rest.  Good luck! Smile

On an unrelated note, I would also recommend that you consider enabling encryption on your backups.  It's just good practice given how easy it is nowadays, and with modern CPUs the disk will still be the bottleneck, so the only requirement is storing the password somewhere.  Same goes for safeguarding your actual source disk, e.g. BitLocker perhaps, since you're running Win7 Ultimate.

Edited 7 March 2017 2:57 AM by jphughan
Phlipster
Phlipster
New Member
New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)
Group: Forum Members
Posts: 14, Visits: 35
Thanks JP. I think I understand. If I have this right, I need to reduce the number of incrementals and allow for more frequent full back-ups, so that the two/six option rotates forward, deleting a potential third, based on space.

I'm wide open to other options. I picked the one I have as it seemed the easiest pre-fab method available when I purchased the product. To be frank, Macrium may well be so powerful as to be beyond my simple understanding, which is unfortunate because I believe it is the best back-up and recovery software I have found. Just very very technical, which is probably great for professional IT folks, not so much for us duffers.

I'll see where changing the increment and full strategy gets me, I'm not married to the past back-ups so I can start fresh with no problem.

Any suggestions you or the other pros have would be appreciated.

Phlip
jphughan
jphughan
Most Valuable Professional
Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)
Group: Forum Members
Posts: 2.2K, Visits: 14K
Phlipster - 10 March 2017 6:21 PM
Thanks JP. I think I understand. If I have this right, I need to reduce the number of incrementals and allow for more frequent full back-ups, so that the two/six option rotates forward, deleting a potential third, based on space.I'm wide open to other options. I picked the one I have as it seemed the easiest pre-fab method available when I purchased the product. To be frank, Macrium may well be so powerful as to be beyond my simple understanding, which is unfortunate because I believe it is the best back-up and recovery software I have found. Just very very technical, which is probably great for professional IT folks, not so much for us duffers.I'll see where changing the increment and full strategy gets me, I'm not married to the past back-ups so I can start fresh with no problem.Any suggestions you or the other pros have would be appreciated.Phlip

Reflect is the best solution I've found as well as long as you don't require functionality that it simply doesn't offer (tape backups, enterprise-grade management, etc), which is fine with me since the features it doesn't offer tend to cause the products that DO offer it to become bloated and cumbersome.  But as for whether you have it right, it depends on what your goals/priorities are.  For example, I'm perfectly fine with the out-of-the-box "Incrementals Forever with Synthetic Fulls" even though the synthetic merge can take 1-2 hours in my setup because the backup runs weeknights at 11PM when nobody is doing anything on the server, so an extra 1-2 hours doesn't matter in the least, and this strategy is more efficient in terms of storage capacity consumption than storing multiple Fulls.  But if for example I had a scenario where the server was being used 24x7 during the week and was only free for the weekend, I would probably use a strategy that retained 2 Full backups and 5 Incrementals, with the long-running Fulls captured during the weekend downtime and the fast, non-merging Incrementals captured each weekday.  As long as I had enough capacity to temporarily store a third Full backup, I would even be able to tell Reflect not to purge until AFTER the new job completed.

So how do you prioritize your backup properties?  Long backup history, granular backup history (i.e. lots of snapshots within a given time period), fast job execution, efficient use of storage?  That will guide the most appropriate strategy for you.

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search