Case Study: Backup and Recovery
Backup was created, but no one checked the restoration
The company saw successful backup job tasks but was unsure if the copy would open after a failure and how long it would take to restore critical services.
A copy is only valuable after verification
Needed to identify critical data, acceptable loss of changes and actual recovery sequence for servers.
Data Map
Divided systems by criticality and determined frequency, retention period, and recovery points.
Separate storage
Set up copies so that a failure or ransomware on the main server does not destroy the backup.
Recovery test
Set up a test environment and confirmed file, database, and configuration recovery.
Description is anonymized: technical details and customer data are not disclosed.
Result
- A clear backup policy has been established.
- Backup errors are monitored, not left only in logs.
- Responsibilities and procedures in case of an incident are recorded.
- Restoration was practically tested, not just by task status.
Not sure if the backup will recover?
Will check existing copies and perform a safe recovery test.