Non contiguous backup scheme recovery
Perhaps the title is a bit vague, but my confidence is always shattered with Acronis when a backup scheme involving many incremental backup chains becomes somehow broken.
Let's say my scheme with auto cleanup (after 5 chains) looks something like this:
(F = Full, I = Incremental, P = Problem)
F I I I I I : F I I I I I : F I I I I I : F I I P
Now at this stage, P means the backup failed, became corrupted or something else to stop successful backups.
Is Acronis smart enough to recover the chain if I delete the problem archive and perhaps one incremental? Or do I have to perform a special 'repair' or 'consolidate' function to get Acronis back on track?
Hi SS (if I can call you that?)
Space is ok but I understand why you would ask. I was just curious and I guess I base my question on a bit of experience as well. I just wondered on how well Acronis recovered from issues like this.
The following event occurred (where V = Virus):
F I I I I I : F I I V
Windows would not boot as a consequence. We decided to go back to the last Full backup which being daily backups was back to a Saturday. I should have deleted or renamed the 2 redundant incrementals because as far as the restored Acronis was concerned it hadn't created them yet. (a time paradox!)
Now Acronis of a few days ago is not creating new backups and is reporting errors. Of course I am not prepared as the problem is on the customer's computer and not with me. It even tried to create a new Full:
F I I I I I : F Ix Ix V : F
But after last look, there were error logs. I will look to make sure the errors are not because there backups are no longer contiguous.
But after last look, there were error logs. I will look to make sure the errors are not because there backups are no longer contiguous.
Richard,
When you review the logs, I suspect this is what you will find. If the version chain becomes broken, Acronis will be unable to create the next archive because of the dependency. Usually, you can deleted this back up set from view within the program, Back Up and Recovery tab, then close and reopen the app. Have it scan for back ups which updates the archive.xml database and allows back ups to contine on a chain. This usually works, so please try and update with those results.
Thank you SS, I think we're getting somewhere.
So if I understand you correctly, I don't delete any .tib files from the chains, but instead look for the scheme in the Back Up and Recovery tab, delete that (which WON'T delete tib files!) then just scan for any backups? Will it analyse the chains and work out for itself what tib files are part of the contiguous backup set?