Backup and recovery is the practice of regularly copying business data to a safe place and being able to restore it quickly after loss, damage, error or attack.
Data · Reviewed by Ray Rasouli
Ask about backup and recovery
Plain answers, with your setup in mind.
Ask anything about backup and recovery. For example, how it works in your current tools.
A scripted guide for now. It does not store what you type.
Backups protect against deleted files, failed hardware, bad updates and ransomware. Recovery is the part people forget: a backup only matters if you can actually restore from it, in time.
A small manufacturer backs up its server every night to an external drive kept in the same room. When a flood damages the room, both are lost. A better setup keeps at least one copy offsite or in the cloud, and one copy that cannot be changed or deleted by an attacker.
Two questions guide the plan: how much recent data can you afford to lose, and how long can you be down? The answers set how often you back up and how fast restores must be.
The usual flow, step by step.
In practice
Restores are never tested.
Backups look fine until the day they are needed and turn out to be incomplete or unreadable.
All copies are in one place.
Fire, flood or ransomware can take out the original and the backup together.
SaaS data is assumed to be backed up.
Many cloud vendors protect their platform, but restoring your deleted records may be limited or your own responsibility.
Keep three copies of your data, on two different types of storage, with one copy offsite. Many teams also keep one copy that cannot be altered.
Recovery point objective (RPO) is how much data you can afford to lose, measured in time. Recovery time objective (RTO) is how long you can be down before systems must be back.
A 30-minute discovery call with Ray, then a clear list of what to fix first. No obligation.
With Ray Rasouli. No obligation.