Recoverability
The degree to which datasets are preserved in the event of incident.
- •Ability to restore data and resume business operations quickly after an incident (e.g., system failure, cyber-attack, disaster).
- •Minimized data loss and reduced downtime in a crisis.
- •Compliance with business continuity and disaster recovery requirements.
- •Increased organizational resilience and stakeholder confidence.
- •Significant data loss or prolonged downtime following an incident, leading to severe financial and operational impact.
- •Inability to meet Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO).
- •Non-compliance with business continuity regulations or contractual obligations.
- •Damage to reputation and loss of customer trust if data cannot be recovered.
Story
Logistics: Databases for critical systems are backed up daily to an offsite, secure location, with regularly tested recovery procedures to ensure data can be restored within a defined Recovery Time Objective (RTO).
Finance: Financial systems utilize database replication to a secondary disaster recovery site, allowing for quick failover and minimal data loss in case of a primary site outage.
Research: Research datasets are backed up to multiple locations, including cloud storage, and version control is used to track changes and allow rollback if needed.
Logistics: Critical operational data from the Terminal Operating System is only stored locally on a single server with no automated backups or disaster recovery plan.
Finance: The only copy of the company's general ledger database exists on a primary server; a hardware failure could lead to permanent data loss.
Research: Years of irreplaceable research data are stored on a single external hard drive without any secondary copies.