Alienstech
Security
Backup and Disaster Recovery
Backups that are verified by restoring from them, with a written recovery plan and a realistic idea of how long recovery takes.
Nearly every business has a backup. Considerably fewer have a restore. The difference tends to surface on the worst possible day.
Two numbers decide what the backup needs to look like: how much work you can afford to lose, and how long you can be down. Once those are agreed, the design follows from them instead of from whatever product was installed at the time.
Sound familiar?
- Backups run but nobody checks the results
- No restore has ever been tested
- Everything is backed up to a drive sitting next to the server
- Microsoft 365 data is assumed to be backed up by Microsoft
- Nobody knows how long a full recovery would take
- Ransomware could reach the backups as easily as the live data
How Alienstech handles it
The design starts with the two numbers above, then applies the usual rule: more than one copy, more than one type of storage, at least one copy off site, and at least one copy that cannot be altered or deleted from the network it protects.
- Servers, workstations that hold local data, and cloud services including Microsoft 365
- Off site copies with retention long enough to survive a problem that goes unnoticed for weeks
- Copies that ransomware on the network cannot reach or encrypt
- Backup results reviewed on a schedule, with failures treated as faults rather than noise
- Test restores performed and recorded, including a full machine at least once
- A written recovery plan with the order to bring systems back and who to call
What you get
- Restores you have watched work
- A realistic recovery time you can plan around
- Backup copies that ransomware cannot reach
- Microsoft 365 data covered by a real backup
- A written plan for the day it matters