Backup strategy + DR plan
We build a backup strategy and a disaster recovery (DR) plan: what, how often and where to back up, where to store copies and exactly how to recover after a failure, hack or data loss. So that an incident does not turn into a loss of the business. Honestly upfront: a backup reduces the risk of data loss and gives the ability to recover, but its value is determined by a TESTED restore — an untested backup is not a guarantee, and some data between copies can still be lost.
Backup strategy + DR plan — overview
A backup strategy and DR plan is the design of reliable backup and a clear recovery procedure: we define what is critical to back up (DB, files, configs), the frequency, the storage scheme (the rule of several copies, separate/remote storage, protection from ransomware), retention periods, and — most importantly — the recovery procedure: a step-by-step plan, who does what, how long it takes. Honestly about the key thing, this is the heart of the service: a backup without a TESTED restore is an illusion of safety. 'Copies are being made' ≠ 'you will be able to recover': a backup can be corrupted, incomplete or unrecoverable. So we build in a restore test — without it there is no guarantee. Honestly about the loss window: there is always a gap between two backups, and the data for that gap can be lost on a failure — how much exactly is acceptable to lose (this is RPO) we define deliberately (in more detail — service 771). Honestly about prevention: backup and DR do NOT prevent an incident (a hack, failure, error) — they give the ability to RECOVER after it; these are different tasks (prevention is WAF/validation/monitoring). Honestly about the DR plan: a plan is a document and a procedure; the real recovery speed depends on the infrastructure, access and who executes it — we make the plan realistic and verifiable, not 'for show'. Honestly about costs: storage for the copies (especially remote) is paid separately and on an ongoing basis. Honestly about access: access to the servers/data is needed. An important boundary: this is a backup strategy and DR plan; the formal definition of RTO/RPO targets is an adjacent service 771, availability mirrors are 769. Picture this: instead of 'the site was hacked/went down — the data is lost, nothing to recover from' — there are tested copies and a clear plan by which you return to work. The base price starts from 20,000 ₽ (excluding storage cost); it depends on the data volume and infrastructure.
Problems we solve
- Backups are not made, or are made but no one has tested the restore.
- Copies sit next to the production data — ransomware will take them too.
- No plan: on a failure it is unclear who does what and how long it takes.
- It is unclear how much data is acceptable to lose and in what time to recover.
What's included in the Backup strategy + DR plan service
- Defining critical data to back up (DB/files/configs)
- Strategy: frequency, storage scheme, ransomware protection
- Separate/remote storage of copies and retention periods
- A restore test — not 'copies for the sake of copies'
- A step-by-step DR plan: who/what/how long on a failure
- Indicating boundaries (recovery, not prevention; the loss window)
- Pairing with RTO/RPO targets (771) if needed
- Handover and review with you
What you get
- Critical data is reliably copied and stored separately
- Recovery is tested, not assumed
- There is a clear step-by-step plan for a failure/hack
- Reduced risk of losing the business (incident prevention — separate)
How the work goes: steps
- We define critical data, acceptable losses and access; collect access
- We build the storage strategy, set up backups, do a restore test
- We write a realistic DR plan, review boundaries and costs with you
Why PDV Expert
- Fixed price and timeline — no surprises on the invoice.
- Report and recommendations in plain language — clear without a technical background.
- In touch at every step and answering questions about the result.
FAQ
We do make backups — is that enough?
Not necessarily. 'Copies are being made' ≠ 'you will be able to recover': a backup can be corrupted, incomplete or unrecoverable, and if copies sit next to the production data — ransomware will take them too. The value of a backup is determined by a TESTED restore and separate storage — that is exactly what we build in.
Will a backup protect against hacking?
No, this is about recovery, not prevention. Backup and DR will not stop a hack, failure or error — they give the ability to return to work AFTER an incident with minimal losses. Prevention is other measures (WAF, validation, monitoring). The right way is to have both.
How much data can be lost on a failure?
Honestly: there is always a gap between two backups, and the data for it can be lost on a failure. How much exactly is acceptable to lose and in what time to recover — these are RPO/RTO targets, which we define deliberately for your business (in more detail — a separate service 771). The smaller the acceptable losses — the more frequent and expensive the backups.
About the provider
The «Backup strategy + DR plan» service is provided by PDV Expert — a team specialising in «Site quality». We work under contract and deliver a written report with recommendations.