Protect related data together
An application can depend on files, databases, configuration and keys. Include data outside the server, such as connected storage or external services.
Backup and recovery
Backup scope, retention and recovery need to suit your data. We help select and test the backup approach.
Process
Describe the protection objective
Define how old recovered data may be and the intended maximum time for recovery.
Configure the backup
Agree scope, schedule, retention, storage and responsibilities for the selected solution.
Test recovery
Verify data and application behaviour in an appropriate test environment; document duration and dependencies.
Adapt to change
Account for new applications, increased data volumes and changed permissions in the backup plan.
Terms that make planning clearer
| Term | Meaning | Your planning question |
|---|---|---|
| RPO | Objective for maximum acceptable data loss expressed as time | How old may the recovered data be? |
| RTO | Objective for time until recovery | How long can the affected process pause? |
| Retention | How long backup versions remain available | Which previous states need to remain accessible? |
Which data do you need after an incident?
An accidentally deleted file, a faulty update and the loss of an entire environment require different recovery paths. Related data and the time your operation can allow for recovery are crucial. We discuss these requirements in the context of your selected platform.
Consider access and storage location
A backup on the same system may be affected by the same failure. Separate storage, permissions and additional protection options are planned around the risk.
Measure success through recovery
A completed backup job does not show that an application works again. Check selected files and test recovery of the environment that your workflow needs.
Your backup plan should answer
- Which components and data are protected?
- Where are backups stored and who has access?
- How are failures detected and handled?
- Who can request and accept a recovery?
Frequently asked questions
Is synchronisation a backup?
Synchronisation distributes changes and can propagate deletions. A backup plan also considers previous versions, retention and recovery.
Is every backup immutable?
No. Immutability, separate access and additional storage locations are properties of the chosen solution and should be explicitly agreed.
Request a proposal
Tell us your application, user count and the support you need.