Skip to main content

Adding backup copied from other location does not work

Thread solved

I decided to dedicate an empty NAS with new harddisks for backing up only my most important desktop, so I would not have to delete versions before making a new full backup. The former backup destination is an identical NAS with different IP-adress, the backup working in my Acronis software. I wanted to move to the new harddisks, so I copied the backup files with robocopy from the old NAS to the new NAS. Then I tried to "add existing backup" with the copied files - when trying to add the full backup error message resulted Failed to add the backup to the backup list. The backup may be locked or corrupted. Also, make sure the folder contains the last volume of the backup, and does not contain a renamed copy of the same backup. More information about this error and solutions may be available online in the Acronis Knowledge Base. To access the online resource manually, enter the event code at: https://kb.acronis.com/errorcode/ Event code: 0x01010005+0x01010005+0x01E50015+0x01E5001A+0x003C0003 The error code did not yield a result, the file definitely is not in use by another program, all the backups are the same as in the original NAS. Question: What have I done wrong so the program refuses to add the backup at the new location? Additional suggestion for the forum software: Please install a button to save the postings befor sending, or save them automatically. I hit something somewhere, flew out from the website and the text was gone.

0 Users found this helpful

Did you remove the backup task from the ATI user interface; if not it will not allow you to add the same task back. What you need to do is to update the backup task with the new backup location. You will need to remove the old backup task (which may be problematic as the files have been moved).

With local backup you can avoid having to do that if you use ATI to move to the new location; it may be more complex moving from one NAS to another.

Ian

Hi Ia

Thanks for your input!

I have still kept the old files on the old NAS up to now. I have not deleted the older backup task to the older NAS. I thought the older task + older files will continue to exist and the newer files on the new NAS can be added as a new task. Shouldn't that be possible?

Franz, the process for moving the destination for backup tasks should be performed from within the ATI GUI and not by moving files using Explorer.

See the ATI 2019 User Guide: Backup operations menu

Move - click to move all the backup files to another location. The subsequent backup versions will be saved to the new location. If you change the backup destination by editing the backup settings, only new backup versions will be saved to the new location. The earlier backup versions will remain in the old location.

Hi Steve,

thanks again for your valuable advice!

I did the "Move" when the files were already in both loacations and no error message popped up neither was any long lasting file transfer started. Now the old task points to the new location. When checking for deletable backups, I found the backups offered in the new location. I entered the task options again and saved them. Starting the backup works and starts a differential backup as it should. Apparently the "Move" works also after manually transferring files but is essential for the task being transferred completely.

BTW, I ran into a problem after changing the names of the NAS devices. I expected that the IP-adress is defining the destination. I had to rename them again. I would rather change the name of the NAS - what can I do to make the tasks work despite the name change but the same IP-address?

BTW, I ran into a problem after changing the names of the NAS devices. I expected that the IP-adress is defining the destination. I had to rename them again. I would rather change the name of the NAS - what can I do to make the tasks work despite the name change but the same IP-address?

Franz, I would expect that you may need to clear the stored NAS credentials then re-establish them again to resolve the above issue.  

See  Acronis True Image 2016: Troubleshooting Issues Related To NAS Credentials | Knowledge Base