Version Chains Not Working & Other Issues
Problem 1:
Versions just keep on being created.
Setting - Create a new full every 6 incrementals
Clean up - Store no more then 3 version chains
I have like 16 versions with 6 incrementals. So the job is working correctly but no clean up is happenning. Used to be an option to consolidate the backups but that's been gone for a while.
I don't have TB's available to recreate the job. I am pretty sure just deleting the old jobs will probably corrupt the entire backupset. Is that correct?
Problem 2:
Auto update:
Build 5554 which says is up to date however I see 5555 is available. Is auto update broken or what? How do I force an update?
Problem 3:
Online dashboard reports the following dates but backups work daily and no issues. Even sends me emails for sucess completion notice. All machines seem to be stuck in time in November except for one. Clei
Last backup
Nov 15, 2016, 02:57 AM
Next backup
Nov 16, 2016, 02:00 AM
Local client backup status reports:
Today: 02:06 and Last Backup: Feb 01, 2017 02:06
7 or 8 systems are out of wack with reality and are reporting Status OK. All machines are online and there are no proxy servers. So what gives?
MikeO3, it is intended behavior that the auto-update does not detect a new version available. The version 5555 is a patch, a small file that you download and that updates existing installation. Patch 5555 fixes a very few number of issues. Updates that are distributed through the live update system are full installers that are downloaded and update the entire program installation.
Communication wtih Online Dashboard is done through the process "C:\Program Files (x86)\Common Files\Acronis\Infrastructure\mms_mini.exe". Maybe its activity is blocked by a 3rd party security software, or the corresponding Windows Service "Acronis Managed Machine Service Mini" is not running.
The other two issues (Online Dashboard and automatic deletion of backups) require additional investigation, I recommend you opening a support ticket for that.
Regards,
Slava
Thanks for the comments & guidance. Ill check the FW when I get back but I know for sure there is no FW or blockers on one of them which is not reporting.
I will place a service ticket for the backup job issue.
Mike, the logs may show more information on why your automatic cleanup rules are not firing correctly here. The Log File Viewer linked in my signature will work for the ATIH 2017 build 5554 / 5555 version (though not for the New Generation version - yet).
Thanks Steve for the utility. Very helpful.
Here is some relevant extracted information:
Sucessfull backup:
id=58; level=2; module=100; code=0; date/time=2017-02-03 02:05:36
message=The following backups have been successfully created: \\ajaxnas02\backups\cator116\backups\CATOR116_NAS_SSD_inc_b16_s4_v1.tib
id=85; level=2; module=316; code=6; date/time=2017-02-03 02:05:42
message=Operation has succeeded.
Some snips of errors. Appears it is reporting a permissions issue. The perms are the same for all files when I check the NAS files and you can see above the backups are performed with no issues. I use the same account for several other PC's so there is probably something corrupt in the job maybe. I will reset the permissions at the file level on the NAS folder and see if the job works overnight.
id=60; level=2; module=11; code=0; date/time=2017-02-03 02:05:36
message=Consolidate Backup Archive<tabpoint value=30><indent value=4>Location: <indent value=10><textcolor value=navyblue>\\ajaxnas02\backups\cator116\backups\CATOR116_NAS_SSD_inc_b16_s4_v1.tib</textcolor></indent><indent value=4>Destination: <indent value=10><textcolor value=navyblue>\\ajaxnas02\backups\cator116\backups\CATOR116_NAS_SSD_inc_b16_s4_v1_4D841EEC-1DEC-404D-A1B7-CC47C8283F0C.tib</textcolor></indent><indent value=4></indent>
id=61; level=4; module=495; code=38; date/time=2017-02-03 02:05:42
message=Failed to perform consolidation. Ensure that the credentials for accessing folder \\ajaxnas02\backups\cator116\backups\ are correct.; line_tag=0x6D5B4DCC0BA14A28
Error_Code=ASYA7wEoSqELzE1bbUZhaWxlZCB0byBwZXJmb3JtIGNvbnNvbGlkYXRpb24uIEVuc3VyZSB0aGF0IHRoZSBjcmVkZW50aWFscyBmb3IgYWNjZXNzaW5nIGZvbGRlciBcXGFqYXhuYXMwMlxiYWNrdXBzXGNhdG9yMTE2XGJhY2t1cHNcIGFyZSBjb3JyZWN0LgAkbW9kdWxlAEF0aV9kZW1vbl92c181NTU0ACRmaWxlAEFrOlw1NTU0XHByb2R1Y3RzXGltYWdlclxhcmNoaXZlXGltcGxcb3BlcmF0aW9uc1xhcmNoaXZlX29wZXJhdGlvbl9jbG9uZS5jcHAAJGZ1bmMAQVRydWVJbWFnZTo6QXJjaGl2ZTo6Q2xvbmVBcmNoaXZlT3BlcmF0aW9uSW1wbDo6Rm9ybUNvbnNvbGlkYXRpb25FcnJvcgAkbGluZQBOKgwAAAAAAAAA6wALAFcprwQJAmDUACRtb2R1bGUAQXRpX2RlbW9uX3ZzXzU1NTQAJGZpbGUAQWs6XDU1NTRccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVcaW1wbFx2b2x1bWVfbG9jYXRpb24uY3BwACRmdW5jAEFUcnVlSW1hZ2U6OkFyY2hpdmU6OlZvbHVtZUxvY2F0aW9uOjpPcGVuRGlyR2VudGx5ACRsaW5lAE6
id=62; level=4; module=11; code=235; date/time=2017-02-03 02:05:42
message= ; line_tag=0xD460020904AF2957; hide=1
id=63; level=4; module=4; code=20; date/time=2017-02-03 02:05:42
message=Access to the file is denied.; line_tag=0xF35F747B3B21FC2D; hide=1
id=64; level=4; module=0; code=65520; date/time=2017-02-03 02:05:42
message=The user name or password is incorrect; line_tag=0xBD28FDBD64EDB8F1; hide=1
id=65; level=4; module=11; code=1001; date/time=2017-02-03 02:05:42
message=Failed to open data stream. Try to remove the backup from the list, add it again by clicking 'Browse for backup' and recreate the backup settings.; line_tag=0x6D5B4DCC0BA1486A
id=66; level=4; module=485; code=6; date/time=2017-02-03 02:05:42
message=Failed to perform consolidation. Ensure that the credentials for accessing folder \\ajaxnas02\backups\cator116\backups\ are correct.; line_tag=0x6D5B4DCC0BA146A0; hide=1
Mike, the log file confirms a known issue - the backups are being created fine but the auto cleanup (aka consolidation) is hitting a permissions issue. I have the same issue on one of my Windows 7 systems backing up to my NAS.
There are some workarounds but personally I am waiting for the next build to be released which should have the fix for this issue included - this is due within a month or thereabouts per updates from Slava, one of the Acronis engineers.
In the interim, you can manually clean up your old version chains then run a Validation for the backup task that created them which will stop the error messages while the next version chain is being populated. The Validation is important to reconcile the Acronis Database files with the status of the remaining version chain files - you will get an error message for each deleted file that is found - just take the Ignore option for each file.
Having the same problem with version chains not being deleted. However, I have an additional problem - I can't validate my backups. It keeps claiming that it can't find a version number - I have no such version. It starts by looking for version 49, and if I click Ignore, it moves on to not finding version 48, and so on. There's a mystery folder on my backup disk - an empty folder named Disk_C. It's at the same level as my tib files, and it seems as if validate is looking in this empty folder.
Assuming I get the validation problem solved, how do I manually delete old version chains? My disk is now completely full, and the only solution I can come up with is to wipe the disk and start over. I'd rather not do that.
Validation failed with my backup set. I presume it "thinks" the chains have been purged. Therefore the whole set is probably useless.
Steve's suggestion of deleting a couple of chains and trying validation completly failed as well.
What I did was the following to free up space on my disk.
- Delete all chains except the last 2 and moved remaining to another folder.
- Cloned the backup and started a new backupset.
I am taking a huge chance here that the original backup is valid but I had no choice since I was out of space. Acronis/Windows 10 let's you mount backup tib files so that's what I was counting on in case of catastrophe.
I hope they fix this.
I suggest you provide in App backup (make sure the attach system report is ticked at the bottom of the dialouge box), include a link in the feedback to this thread.
Ian
For anyone facing validation failures with Acronis True Image running in Windows: please run the validation from bootable media environment. This will exclude possible issues with inconsistencies in the backup catalog in Windows, as well as known issues with accessing network shares in Windows application.
If the validation will still be failing, it could be due to issues with connection to the storage where the backup resides. For external USB drives and NAS devices we recommend temporarily copying them to an internal disk and run the validation against those copies. If such validation fails, then the backup must be indeed corrupted and should be deleted alongside with all the dependent incremental and differential backups.
To validate a backup from bootable media, boot the computer from the media, select Acronis True Image option from the boot menu, click on the "Recover" tab, add the backup through "Browse for backup" function, after that right-click the backup and select Validate archive, click Proceed.
Regards,
Slava
Not really a solution. I don't have a spare terabyte to copy the backup to, and I don't have room on the external drive to install a bootable system.
Any updates on a fix to auto-delte version chains?
Thanks for the advice Slava and maybe I can do with only 1 chain as my backup set is >4TB for several of the systems. Sorry, but I don't have the space as these are home systems and not business systems where we have 100's of TB's to perfom multiple copies. We don't use Acronis for our business systems/servers.
As Rick asks: When will a fix be available?
Mike, Rick,
Steve mentioned a known issue with accessing NAS devices that currently affects some users of "Acronis True Image 2017" builds 5554 and 5555. The fix will be included in the next update, expected within several weeks.
However, there are 2 more possible causes of the validation failure:
1) issues with the catalog/database of backups that Acronis True Image keeps in Windows. If for some reason a record appears pointing to a non-existing file or folde, errors are likely to appear during backup creation, cleanup and validation. By running a validation from bootable media (without even moving .TIBs) you can exclude the catalog/database factor completely, as bootable media does not use it at all.
2) if there is a problem with environment, backups may be created corrupted or become damaged later. In the end, a backup is just a file and like any other file it may become unreadable if the hardware fails. At the same time, a problem with environment may produce false alarms, when backup is good, but bad network connection, disk controller or even some third-party secutiry software interferes with validation procedure. See the short diagram here on how to troubleshoot this situation.
Regards,
Slava
I think maybe I don't understand what you mean by running the validation from Bootable Media. Your flowchart refers to running it from Arconis Bootable Media. What is Acronis Bootable Media? How is this different from simply running the validation from Windows? You want me to install and run Windows on my USB RAID?
Rick, you absolutely need to create a bootable media and know how to use it. In addition to its role in the troubleshooting of current validation issue, it has another very important purpose. The rescue media will be the only way for you to start Acronis program and recover your system in a catastrophic event when Windows fails to boot for any reason.
Having written the media, please figure out how to boot your computer from the media - manufacturers assign different keys for accessing BIOS and startup menu: it could be F2, Del, Esc, F10, F12 or some other key on the keyboard. Usually it is displayed on the screen during bootup. You need to reboot your computer and press that key to access BIOS/UEFI settings and choose to boot your computer from the rescue media.
Once you have started Acronis True Image from the bootable media, click on Recovery tab, then locate your backups using "Browse for backup..." button. If the backup is on a network drive, look under "Computers near me" section of the "Browse" dialog. After locating the backup, right-click it and select "Validate Archive" as shown on the picture attached to this message.
By the way, the attached screenshot also shows you the "Recover" option in the context menu - use it to recover your system if Windows will fail to boot at some point in the future.
And of course, you can always get further help from our Support Team, don't hesitate to enter our live chat service.
Regards,
Slava
