Corrupted backup due to forced quit - how to fix?
I was forced to reboot my PC in the middle of a backup (don't ask) and now the backup is corrupted. VSS Doctor reports a few "Volume Shadow Copy Service" errors due to the shutdown but nothing to fix.
So at this point I have two backup jobs, #1 is a "Files & Folders" type and #2 is a "Disks & Partitions" backup, both doing daily incrementals. So now, #2 on the Recovery tab shows a collection of backups from BOTH backup jobs, which is completely bizarre. I can tell because backup #1 runs at 6am and backup #2 runs at 7am and for backup #2 I see a mixture of backups from the same day, one at 6am and one at 7am, every day. In other words the list of backups on Recovery tab for #2 is a jumble from BOTH jobs.
Then, backup #1 is empty on the Recovery tab, and I can't add those backups as an existing backup. I tried removing the backup job completely and adding it as an existing, which it seems to be trying to do, the UI is unresponsive for quite some time, but then nothing happens, no backup, no error.
So... I've got a mess, it is actually possible to recover files from job #1 if I look at the backups for Job #2. All the backups from #1 are mixed up in the list for job #2 and those show a "Due to an internal error, you can only recover files from this backup" which actually does work.
I also noticed that the last backup in the chain for #1 (which just happens to be a full backup) is far too small, since it was interrupted. I tried renaming it some garbage and I still can't add #1 as an existing backup. So I put it back.
So my guess is that I can't add job 1 back in because all the backups are already incorrectly included in job #2's list of backups.
I'm doing a full backup right now using a separate job and it's working fine so far. Got a few hours to go.
Is there any hope getting this sorted out so I can access my backups? What can I send that would help diagnose this? File upload is not working and I can't paste links.... ugh
OK the database rebuild kind of worked. Not perfectly but good enough. After the database rebuild I had nothing under recovery for all backup tasks but simply adding existing backups... kinda worked. Sometimes "add existing" simply reconnected an existing backup task with all the old backups, making them all visible on the recovery tab. Yay!
However for some, it would populate the backup tab with some, but not all, old backups. I had to "add existing" to older backup chains to get them to show up, and they did, as a new, separate unscheduled backup task. Not great, but my old backups are alive again and easy to find. And this foils automatic cleanup since now the backup is split into two tasks.
In some cases a scheduled backup had nothing on Recover but one I added with "add existing" had all the old backups for the other, scheduled task, so it was easier to delete the empty one and just reconfigure the one I just added with all the old backups and that worked real well. In hindsight, it would have been easier to just delete all my backup jobs completely and "add existing" until everything showed up and reconfigure the most recent ones.
I'll just have to manually clean up old backups once in a while until the automatic cleanup kicks in for the new backups jobs since now things are split into a bunch of backup tasks. A small but manageable mess.
For one backup job, Validate gave me an error that it couldn't find my NAS, but I was able to actually recover a file from the backup tab, and oddly enough, this caused validate to work. Doing a single file restore reconnected or fixed something that was wrong and now that backup job looks fine, it validates.
Thanks much for your help!
Eric, glad the suggestions were helpful. One word of caution, when manually deleting any backup files, please either ensure that the task that created those files is not shown in the ATI GUI or else use the new 'Clean up versions' tool to do the deletes from within ATI. This will avoid errors for 'cannot find version X' being thrown later for your tasks.