Whole thing falls apart
I am not sure what happened. I have it set to backup entire PC every Wed. All was well, but last week there are two files, b5s3v1 and b5s3v2. So today when it goes to back up it says that there is no file. I restart computer and point it first to v2, no go. then to v1 and its just hanging, "calculating time remaining..."
Also at the top before I restarted after stopping the stalled backups, it said last backup last week, not it says .....
I looked at the support doc that came up, but it had nothing to do with this. I am not even sure why there is a problem nor what to do about it.
Thanks for any help.
I tried to change the file to V3, but did not work. So then tried again per this
https://kb.acronis.com/content/24462
sticks at Calculating Time Remaining.
Do not try changing the name. I would validate the backup and when error messages appear click on "ignore". To validate, select the backup task and right click on the inverted v next to the backup name, then select 'Validate".
Hopefully this will solve the problem.
Ian
No validate on this task, I see one on the files backup task, but not the entire PC task
I assume then if I cannot validate it, it is corrupted somehow and not able to be fixed?
If that is the case, can I clone it to a new task and make this one run "never"?
What else should I do. Thanks.
Let me deal with a misunderstanding from earlier in this topic where you reported that ATI said it cannot find version 3 but that you have b5s3v1 and b5s3v2
Version 3 in this context refers to the B3 version of this backup chain, not to V3 for your B5 chain.
As this is the ATI 2016 Forum, assuming that this is also the version of ATI you have, then you first need to ensure that you have a complete backup chain here, i.e. a full backup file as shown by having _full_b5_s1_v1 along with any other files in the same b5 chain, such as _inc_b5... or _diff_b5... files. If this is an incremental backup scheme, then you must have all the members of the chain and not be missing any files in the sequence, i.e. s1, s2, s3...
The normal cause of messages like 'cannot find version 3...' is that these have been deleted manually outside of ATI by using Windows Explorer. Doing this does not update the Acronis Database information for the backup task where ATI records what files it has created for the backup task, and hence why it complains when they are missing!
I never got this message before and it was backing up weekly. I have the b1s1v1, b4s1-s11 and then b5s1, b5s2 and b5s3v1 and b5s3v2. That seems to be where things went wrong. I never deleted anything and these are deleted per the schema that keeps the last chain and deletes all previous ones except the first b1s1.
I am not sure why there was a v1 and v2 on the back up last week. Perhaps the computer was restarted, but I am not sure about that, I would doubt it.
What is the best way to get back on track? Thank you for your help, I appreciate it.
The presence of v1 & v2 for the same backup sequence b5s3 would suggest that either an issue was encountered or that the backup was interrupted and continued. This normally happens when a specific file size is set or if using FTP which imposes a 2GB file size, so the backup is split into multiple files each with a new v? number.
The only way to know more information for this particular backup situation would be to review the log files for when these files were created by using the MVP Log File viewer tool (see Community Tools link in my signature).
One way of getting back on track would be to clone this backup task to create a new task prefixed by (1) then the same name. I would recommend changing the Destination for the cloned task to point to a different folder on the backup drive, then test that you can run this task to create a new _full_b1_s1_v1 file in the new folder.
Once the cloned backup looks good, then remove the old task settings, keeping the files from that backup until you are sure that you will not need them.
I have another question. I also back up daily certain selected files/folders. The scheme says Create a full version after 25 incremental versions. However, I just got b13s26v1. I thought after s25 it would go to b14s1v1. What is the problem here? Thanks.
I just did a clone of the EntirePC and ran it and got the same message, cannot find Version 3. There is no validate in the drop down either.
When you do the clone of the task, you need to ensure that you are using a new/unique task name so that you are not matching any task names that you may have used previously and which are known in the Acronis Database.
For your other question, "Create a full version after 25 incremental versions." = 1 x Full plus 25 Incremental version files, hence = 26 files in total where the first is b?_s1 and the last will be b?_s26 - so the next run should give you a new full file.
Sorry, I ran the old one by mistake. I am running the new one and it is really slow. After over an hour, it just went to calculating time remaining 46MB to 548MB, then 1.03.... now an hour later its up 11GB and says 1 day 12 hours. Not sure why its so slow. But it looks like it is working
Glad the new task is running, and hopefully has either finished or getting close to doing so by now.
I just ran a files backup and got the following error message twice, on b14s1v1 and b14s1v2, although there is a file with a correct size.
"The last bu failed. Failed to exclusively access backup F:...../(1)Files_Backup_Inc_b12_s26_v1.tib during consoldiation. Make sure the backup file is not opened in other applications."
b12_s26_v1 is there in the same folder that 14/1/2 is saved in. Should I ignore this error message or are the files not properly backing up? Thank you
I clicked on 14/2/1.tib and it slowly opened and showed 2 files 14/1/1 and 14/2/1. Then I clicked on 14/2/1 and the window froze, I cannot close it with Task Mgr.
I clicked 13/26/1 and it slowly opened, but never ended up opening anything.
The error message given above is speaking about automatic cleanup which is shown as 'consolidation' in the logs. This should mean that the actual backup was successful and the issue was encountered when ATI was trying to delete the oldest backup files for some reason.