Consolidation Recovery


Author
Message
walam
walam
New Member
New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)
Group: Forum Members
Posts: 15, Visits: 53
I have a "consolidation recovery failed" error.  This has occurred in a stable environment with the NAS showing no errors.  The error does not correct itself over a few days.  Could someone advise where I can find a procedure for diagnosing and correcting this problem.
The computer is a surface pro 3 with Win 10.  MR is 7.3 build 5365.
Thanks 
Wal Lamberth
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)
Group: Forum Members
Posts: 14K, Visits: 83K
If you don't want to wait for another backup in order for another consolidation attempt to occur, Macrium includes a standalone utility called Consolidate.exe that can perform consolidations independently of any backups.  You'll find it in the Reflect application folder.  If you can reproduce the failure using that utility, you might also get more information about the error itself.

Also, you posted this in the V6 section of the forum.  Just fyi for the future.

Edited 2 December 2020 4:16 AM by jphughan
walam
walam
New Member
New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)
Group: Forum Members
Posts: 15, Visits: 53
jphughan - 2 December 2020 4:16 AM
If you don't want to wait for another backup in order for another consolidation attempt to occur, Macrium includes a standalone utility called Consolidate.exe that can perform consolidations independently of any backups.  You'll find it in the Reflect application folder.  If you can reproduce the failure using that utility, you might also get more information about the error itself.

Also, you posted this in the V6 section of the forum.  Just fyi for the future.

Sorry I posted to the wrong section.  I'll seek out that utility and give it a try.
Wal Lamberth
walam
walam
New Member
New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)
Group: Forum Members
Posts: 15, Visits: 53
walam - 2 December 2020 4:45 AM
jphughan - 2 December 2020 4:16 AM
If you don't want to wait for another backup in order for another consolidation attempt to occur, Macrium includes a standalone utility called Consolidate.exe that can perform consolidations independently of any backups.  You'll find it in the Reflect application folder.  If you can reproduce the failure using that utility, you might also get more information about the error itself.

Also, you posted this in the V6 section of the forum.  Just fyi for the future.

Sorry I posted to the wrong section.  I'll seek out that utility and give it a try.
Wal Lamberth

jphughan,  I did try to run consolidate.exe but it wanted to know the source and destination files and I don't know the answers.
On further inspection of the MR error log I note that the first time the error was flagged in the log was on 27.12.20.  The log reported that it was merging the day 27 file into the day 26 file. 
Now, 2.12.20,  the error log reports that it is trying to merge the 27.12.20 file into itself!  It issued a warning 'Write file failed - 59 consolidation recovery failed'.   I don't know what error 59 is.  I would be tempted to delete these files but experience would tell me these problems almost always come back.  How can I deal with this?
Wal


jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)
Group: Forum Members
Posts: 14K, Visits: 83K
Sorry, I should have included a link to the KB page explaining how to use that utility. You can ignore the download link since the utility is now bundled with Refleft, but the instructions are still current: https://knowledgebase.macrium.com/plugins/servlet/mobile?contentId=7734680#content/view/7734680

If you want to reattempt the consolidation that failed, the From and To backups should match the ones shown in the log of the job that showed a failed consolidation. That will usually be either the root Full and oldest Incrementals or the oldest two Incrementals depending on whether you use Synthetic Fulls, but if you’re behind on consolidations due to past failures, then sometimes you’d consolidate across a larger number of backups to be able to purge more than one.

Can you post the whole log from the job saying Reflect tried to consolidate a file into itself? That doesn’t make sense and I’ve never seen that. Remember to omit your license key, which appears at the bottom of the log, when posting it here.
walam
walam
New Member
New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)
Group: Forum Members
Posts: 15, Visits: 53
jphughan, Red face here!  The actual message was:
"Merging '617EF08B9185686D-27-27.mrimg' into '617EF08B9185686D-26-26.mrimg'
Warning: WriteFile failed - 59
Consolidation recovery failed "
I noted that the two files had the same 16 character ID but failed to note that dates following were also part of the file.
I will do some more work on following up your suggestions before seeking your further assistance but can you tell me how to attach a MR log file to a forum post.
Thanks
Wal
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)
Group: Forum Members
Posts: 14K, Visits: 83K
No worries, I have plenty of moments like that myself! Smile  The numbers after the Image ID aren't dates though; they're just sequence numbers.  If they happen to correspond to days of the month in your case, that's just a coincidence.

In terms of attaching a log file, there isn't a great way to do that because the log itself is an HTML file, but you'd want to remove your license key that appears at the bottom.  So I usually recommend just selecting the desired text and copy/pasting it into a post.  For something like that, putting it into a "code block" would be desirable.  To do that, mouse over the Insert button under the box where you write a post and then click the "</>" icon.  That will open a code window.  Paste your log into there, don't worry about the code language option, and click Add Code.  You'll end up with something like this:

This is a code block.
It uses a fixed width font and disables auto-formatting.  For example, typing :) outside of a code block
would cause those characters to be replaced with a smiley face, but not in here.
It also disables automatic line wrapping.
And it's just a handy visual cue to separate someone's post from their log.


If you had an extraordinarily long log from some other area of Reflect (i.e. not a backup job log), an alternative would be to paste the contents into a text file and simply attach that file to a post.

Edited 3 December 2020 1:23 AM by jphughan
Nick
Nick
Macrium Representative
Macrium Representative (5.4K reputation)Macrium Representative (5.4K reputation)Macrium Representative (5.4K reputation)Macrium Representative (5.4K reputation)Macrium Representative (5.4K reputation)Macrium Representative (5.4K reputation)Macrium Representative (5.4K reputation)Macrium Representative (5.4K reputation)Macrium Representative (5.4K reputation)Macrium Representative (5.4K reputation)
Group: Administrators
Posts: 3.2K, Visits: 22K
walam - 2 December 2020 6:31 AM
walam - 2 December 2020 4:45 AM
jphughan - 2 December 2020 4:16 AM
If you don't want to wait for another backup in order for another consolidation attempt to occur, Macrium includes a standalone utility called Consolidate.exe that can perform consolidations independently of any backups.  You'll find it in the Reflect application folder.  If you can reproduce the failure using that utility, you might also get more information about the error itself.

Also, you posted this in the V6 section of the forum.  Just fyi for the future.

Sorry I posted to the wrong section.  I'll seek out that utility and give it a try.
Wal Lamberth

jphughan,  I did try to run consolidate.exe but it wanted to know the source and destination files and I don't know the answers.
On further inspection of the MR error log I note that the first time the error was flagged in the log was on 27.12.20.  The log reported that it was merging the day 27 file into the day 26 file. 
Now, 2.12.20,  the error log reports that it is trying to merge the 27.12.20 file into itself!  It issued a warning 'Write file failed - 59 consolidation recovery failed'.   I don't know what error 59 is.  I would be tempted to delete these files but experience would tell me these problems almost always come back.  How can I deal with this?
Wal


Thanks for posting and sorry you are having problems.
It issued a warning 'Write file failed - 59 consolidation recovery failed'. I don't know what error 59 is.

Error 59 is a Windows error that translates into:

ERROR_UNEXP_NET_ERR  - 59 (0x3B)
An unexpected network error occurred

https://docs.microsoft.com/en-gb/windows/win32/debug/system-error-codes--0-499-


Kind Regards

Nick

Macrium Support

Next Webinar

See our reviews on

Trustpilot Logo
Trustpilot Stars


walam
walam
New Member
New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)
Group: Forum Members
Posts: 15, Visits: 53
Hi Nick,
Thanks for your input.  That error 59 occurred following the two prior days of MR consolidation errors.
Following suggestion of jphughan I have run the consolidation utility with no error and am now watching for a few days to see if performance returns to normal.
I do appreciate the outstanding service that Macrium and its supporters provide through your forum.
Many thanks to you and jphughan.
Wal
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search