Surviving failure.
WHAT MUST BE PROTECTED
The database Configuration Customisation and integration code Documents held in the system
WHAT CLOUD PROVIDERS TYPICALLY DO
Back up their infrastructure.
WHAT THAT DOES NOT COVER
Your data deleted or corrupted by your own users.
WHY THAT MATTERS
It is a common cause of loss, and the provider's backup may not help.
WHAT TO ESTABLISH
Whether you can restore your own data, and how far back.
WHAT TO ARRANGE
Independent export of your data, regularly.
WHY
It is the only protection under your own control.
WHAT TO TEST
Restoration, actually performing it.
WHY
Untested backups fail when needed, routinely.
WHAT TO DEFINE
How much data loss is acceptable How long the business can operate without the system
WHAT THOSE DETERMINE
Backup frequency, and recovery arrangements.
WHAT CONTINUITY PLANNING MUST ADDRESS
Extended outage Connectivity loss Vendor failure
WHAT MANUAL FALLBACK MEANS
Operating on paper, temporarily.
WHY IT REMAINS NECESSARY
Power and connectivity interruptions are routine here.
WHAT TO DOCUMENT
The fallback procedure, and how records are entered afterwards.
WHAT TO REHEARSE
It, at least once.
