Backing Up Business Data in the Cloud: What Stays Your Responsibility
Many companies assume the cloud means no backups are needed. In reality, mass deletion by a user is the most common risk.
Two different risks
Infrastructure failure is handled by the provider, with redundant data centres and internal backups. Human and configuration error, such as a bad import, mass deletion or a mistaken automation rule, stays your responsibility.
Three sensible layers
- Periodic exports of key data to storage you control.
- A backup before major changes, such as an import or a structural change.
- Configuration documentation: automation rules, layouts and access rights, so it can be rebuilt if needed.
The third layer is forgotten most often, yet rebuilding configuration usually takes longer than restoring data.
Test the restore
A backup that is never tested is an assumption, not a guarantee. Once a year, restore part of the data into a test environment and record how long it took. That number is the real answer to the board's readiness question.
Who controls the account
Make sure the company, not an individual or vendor, holds the primary account and its billing. This is part of business continuity that people usually notice only after the person has left.
The data protection angle
Recovery plans and backup storage also involve personal data. Apply the same access restrictions to backup files. See account security and access rights.