Work backwards from the restore.
Which systems need to return first? How much recent work can you afford to lose? How long can the service be unavailable? The answers give the backup plan its priorities.
05 / Backup & recovery
Design the recovery before you need the backup. Start with the data you cannot lose and the time you can afford to be without it.
Plan your recoveryCopies, retention and restoration must be agreed and validated. Recovery is not implied to be automatic.
Your configuration
Which systems need to return first? How much recent work can you afford to lose? How long can the service be unavailable? The answers give the backup plan its priorities.
Decide where copies live, who can access them and how long they remain available. Include application consistency and independent storage where required. A snapshot alone may share the failure risks of its source.
Assign responsibility for checking jobs, investigating failures, requesting restores and validating the result. Agree the scope of testing and the recovery objectives for your service.
Your order identifies the systems covered, frequency, retention and restore assistance. Recovery objectives become commitments only where expressly agreed. Keep appropriate independent copies of critical data.
Before you begin
A defined dataset, schedule, retention period, destination and restore process. The exact coverage belongs in your order; there is no single schedule applied to every 3NT service.
Tell us your separation and data-residency requirements. We will confirm available destinations and the relevant transfer arrangements.
The next step
Identify the systems, data and recovery priorities. We will work through the backup destinations, retention and restore assistance your service needs.
Plan your recovery requirements