Skip to main content

Reverting back to previous backup

Thread needs solution

I get sequential backups. Suppose I revert to a backup 4 sequences ago to get rid of a suspected problem. Everything works, and I am gratefull for my backup program.  Now some time later I again revert to a previous backup. Has Acronis skipped over the bad versions? Could I inadvertently revert to my bad version? What does the backup program do with the copies it skipped over?

Is there some housekeeping that I should have done to remove the supected bad backups?

Thank you for your time

0 Users found this helpful

You will have to do the house-keeping yourself if you want to avoid reverting to a backup image that contains a problem / issue.

Taking your example.  You have a problem and revert back to an image taken say 2 weeks earlier.

Your problem is now resolved and you continue to take regular backup images from this point forward.

You encounter a further problem and want to revert to a backup image from before the problem manifested - you now have to ensure that you only go back as far as your time immediately after resolving the first problem, assuming that having recovered from the initial problem you then took a new backup once you had confirmed the problem was actually resolved fully.

As far as Acronis is concerned, there is no problem with any of the backup images that you have made and the only actions that they will take are those that you have asked to happen, i.e. to consolidate your backup images, make a new full backup image after x number of incremental or differential images, clean-up older images based on your criteria etc.

When reverting back and resolving a problem, you have to decide whether to delete any later images that may contain the issue that caused the problem you hit.  One reason for not deleting these later images immediately is if you have made other changes in that same period and need to recover data related to this to allow these same changes to be incorporated in your reverted system.

One of the rules I practice myself and recommend to others is that anytime I do a restore of my system, I stop using the existing tasks and create all new tasks.  The restore puts the system back to a different spot in time and is now not fully in sync or not 100% the same now as it was then. For example, the tib files which was used as a restore exists now in the storage bin but did NOT exist at time of the backup--it had yet to be created. For me, starting over with new tasks removes any issues as to where the system was at any given time in the old backups. I try to avoid time spent troubleshooting if it can be prevented in the first place. Users choice.