Skip to main content

Old backups reappeared after update

Thread needs solution

I just updated our server (Running on Sever 2016) from 12.5.11010 to the latest version as of today.  Now old backups and old backup locations (locations that no longer exist) have reappeared.  If I try to delete these non existent backups, it gets an error because those files don't exist any more.  

Why did all of these old things come back?  I need to get rid of them because many of these computers have been migrated to other locations, and have no backups there.

 

TOL: Failed to execute the command. Deleting recovery pointsCannot find archive 'COMPANYPC000702.ourcompanyurl.com-8F0BDC7A-59C0-49DE-986A-837B76CD1092-F0F8D867-B822-41C7-B917-FDD0BF7ACCD3A'.Error code 0x01350016+0x01350016+0x01350016+0x01350016+0x01350016+0x01350016+0x01350016+0x00A100DB+0x00A10021+0x00A100C9+0x00A10007
May 22, 2019, 02:13 PMMore details
TOL: Failed to execute the command. Deleting recovery pointsCannot find archive 'COMPANYPC001038.ourcompanyurl.com-8F0BDC7A-59C0-49DE-986A-837B76CD1092-EEF7979F-9A17-4B2F-BAEE-4274D37671A8A'.Error code 0x01350016+0x01350016+0x01350016+0x01350016+0x01350016+0x01350016+0x01350016+0x00A100DB+0x00A10021+0x00A100C9+0x00A10007
May 22, 2019, 02:13 PMMore details
Cannot find archive 'COMPANYPC001038.ourcompanyurl.com-8F0BDC7A-59C0-49DE-986A-837B76CD1092-EEF7979F-9A17-4B2F-BAEE-4274D37671A8A'.
DATE AND TIMEMay 22, 2019, 02:13:27 PM
CODE0x01350016+0x01350016+0x01350016+0x01350016+0x01350016+0x01350016+0x01350016+0x00A100DB+0x00A10021+0x00A100C9+0x00A10007
MODULE309
MESSAGETOL: Failed to execute the command. Deleting recovery points
Additional info:------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB819597
Fields: {"$module":"management_server_vsa64_13160","CommandID":"19926590-DC92-4835-8458-34CE45061FAD"}
Message: TOL: Failed to execute the command. Deleting recovery points
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB819597
Fields: {"$module":"ams_dms_vsa64_13160","CommandID":"19926590-DC92-4835-8458-34CE45061FAD"}
Message: TOL: Failed to execute the command. Deleting recovery points
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"$module":"mms_vsa64_11010","CommandID":"ADB12096-4F68-4B48-B2D2-23CF5B6EAC4B"}
Message: TOL: Failed to execute the command. Deleting archives
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"$module":"staging_command_vsa64_11010","CommandID":"ADB12096-4F68-4B48-B2D2-23CF5B6EAC4B"}
Message: TOL: Failed to execute the command. Deleting archives
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"$module":"mms_vsa64_11010","CommandID":"4504F8D4-2727-42AB-BB4F-A42EDBB790A0"}
Message: TOL: Failed to execute the command. Tol::IsolateCommand
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"$module":"service_process_vsa64_11010","CommandID":"1ACDF6BD-769F-42B5-9C7A-1FC8B1B297E1"}
Message: TOL: Failed to execute the command. Deleting archives
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"$module":"staging_command_vsa64_11010","CommandID":"1ACDF6BD-769F-42B5-9C7A-1FC8B1B297E1"}
Message: TOL: Failed to execute the command. Deleting archives
------------------------
Error code: 219
Module: 161
LineInfo: 0x0B320396ADFE3D39
Fields: {"IsReturnCode":"1","$module":"disk_bundle_vsa64_11010"}
Message: Failed to delete the archives.
------------------------
Error code: 33
Module: 161
LineInfo: 0xA0F87A51D6F9CCF8
Fields: {"$module":"disk_bundle_vsa64_11010"}
Message: Failed to read backup information. The specified vault is probably unavailable.
------------------------
Error code: 201
Module: 161
LineInfo: 0xD5796A33131EEB98
Fields: {"$module":"disk_bundle_vsa64_11010"}
Message: Failed to get information about the archives.
------------------------
Error code: 7
Module: 161
LineInfo: 0xD5796A33131EEB91
Fields: {"$module":"disk_bundle_vsa64_11010"}
Message: Cannot find archive 'COMPANYPC001038.ourcompanyurl.com-8F0BDC7A-59C0-49DE-986A-837B76CD1092-EEF7979F-9A17-4B2F-BAEE-4274D37671A8A'.
 

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello Stonent,

welcome to Acronis forums!

Thanks for sharing your log file. The Agents and Acronis Management Server got out of sync since only AMS is updated to build #13400 while Agents still have build #11010. Please make sure that all Acronis Backup 12.5 components are updated to the same build.

If the issue still persists after the update, please collect Acronis System Reports from AMS and the Agent where you browse the backup location from (plus make a screenshot of this backup location) and share these with Acronis Support Team engineers for investigation purposes.

This system is so touchy.  There needs to be an ability in it to notice that backups are missing and just let you wipe the records out once the next backup takes place.

Some sort of self healing.

I think it's fixed now.  It wasn't related to the version mismatch, or at least the solution wasn't that.  I needed to go to the file shares and do a refresh and that seemed to clear out the old backups.

It would be nice if it could do this automatically.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello Stonent.

Thanks for sharing your solution with forum users. We are glad that the issue is solved.