Rollback and Recovery
Rollback and recovery is the planning that lets a team return to the previous version after a bad release. It covers the code, the database changes and a restore that has been practised.
Why going back is harder than it sounds
Code is easy to revert. Data is not. A release changes the shape of a table, customers write into it for an hour, and returning to the old version stops being a single command. That is the problem worth solving in advance.
What is put in place
The data that cannot be recovered
Recovery has a cost even when it works. Orders taken in the hour before a restore may be lost, and somebody has to re-enter them. That exposure is stated in advance, so the decision to roll back is made with the facts.
Frequently asked questions
How fast can rollback and recovery return us to the previous version?
Reversing code is usually quick once the previous build is kept ready. Anything involving a database restore takes longer, and that time is measured during practice and not estimated.
Can you roll back without losing recent data?
Sometimes, when only the code changed. Where a release altered data, some manual re-entry may be needed, and the written procedure states exactly what.
How often should a restore be tested?
It depends on how the business uses the system. Monthly is common, and a test is also due after any change to the backup arrangement. An untested backup is an assumption.
Does this apply to a server in our own office?
Yes, and it matters more there. On-premise machines often have no snapshot facility, so the procedure has to be written and rehearsed properly.
Tell us what you need.
Share your requirements and one of our engineers will come back to you within one business day.
- No obligation
- A reply within one business day
- Your details stay private
Start with your requirements
Seven short steps that tell us what you need. An engineer reads them before getting in touch.
Share your requirements