Backup controls and business continuity planning
Learning outcome statements
The learning outcome statements relevant for this section are:
- identify and describe the types of storage controls and demonstrate an understanding of when and why they are used
- explain the importance of backing up all program and data files regularly, and storing the backups at a secure remote site
- define business continuity planning
- define the objective of a disaster recovery plan and identify the components of such a plan including hot, warm, and cold sites
Backup controls
Backups provide a crucial safeguard against data loss due to hardware failure, cyberattacks, natural disasters, or human error.
To enhance their effectiveness, backup processes must be supported by robust controls, including:
- Access controls: Restrict who can create, modify, or delete backup data.
- Encryption: Encrypt backup files to protect data confidentiality during storage and transmission.
- Regular testing: Periodically test backup restorations to verify data integrity and the effectiveness of recovery procedures.
- Automated scheduling: Use automated systems to ensure backups occur regularly and consistently without manual intervention.
- Backup logs and audit trails: Maintain records of all backup activity for monitoring and compliance.
- Physical security: Protect onsite and offsite backup media from theft, damage, or unauthorized access through locked storage, surveillance, and environmental controls.
Importance of backup controls
- Regularly backing up program and data files is essential for maintaining operational continuity and preventing significant disruptions.
- Storing backups at a secure remote site, either physically offsite or through cloud-based solutions, protects against localized threats such as fires, floods, or physical theft.
- Backups help organizations meet regulatory and compliance requirements related to data retention and disaster recovery planning.
Common backup methods
- Full backups: Capture all data and system files at a given point in time. This method is comprehensive but requires more storage space and time.
- Incremental backups: Only back up data that has changed since the last backup, saving time and storage but requiring more effort during restoration.
- Differential backups: Back up data changed since the last full backup, offering a balance between speed and comprehensiveness.
- Cloud backups: Store backup data on cloud platforms, offering accessibility, scalability, and often geographic redundancy.
- Disk and tape backups: Store data on physical media, which can be archived offsite for long-term retention and disaster recovery.
- Real-time replication: Continuously mirror data from a primary system to a backup system, allowing for minimal downtime in high-availability environments.
Example: Restoring after a Thursday failure
A system runs a full backup every Sunday, plus daily backups the rest of the week. If the system fails on Thursday:
- With incremental backups, you restore Sunday’s full backup, then apply each incremental backup in order: Monday, Tuesday, and Wednesday.
- With differential backups, you restore Sunday’s full backup, then apply only Wednesday’s differential backup, since it already contains all the changes made since Sunday.
Establishing a formal backup policy is essential to ensure that backup controls are reliable and effective when needed.
Business continuity planning
The goal of BCP is to ensure that critical business functions can continue or be restored promptly with minimal disruption.
Disaster recovery plan (DRP) is a key component of business continuity. Its primary objective is to restore IT systems, data, and infrastructure after an outage or disaster. A well-designed DRP includes clearly defined recovery procedures, assigned responsibilities, communication plans, and documentation of recovery time objectives (RTOs) and recovery point objectives (RPOs). RTO is the maximum acceptable downtime before a system must be restored, and RPO is the maximum acceptable amount of data loss, measured as the time since the last usable backup. A low RTO or RPO tolerance pushes an organization toward a hot site and frequent backups, while a longer tolerance allows for a warm or cold site with less frequent backups.
Key components of a disaster recovery plan
- Inventory of critical systems, applications, and data
- Designated recovery personnel and their contact details
- Emergency communication procedures
- Step-by-step recovery procedures for each system
- Regular testing and updating of the plan
Types of recovery sites
Organizations often prepare secondary locations, known as recovery sites, where operations can be temporarily resumed in the event of a disaster. These sites vary in readiness and cost:
Each type of site has trade-offs between cost and recovery speed. Organizations choose based on their risk tolerance, business impact analysis, and available resources.
1. Hot site
A hot site is a fully operational and fully equipped facility that mirrors the original production environment, including hardware, software, and real-time or near real-time data replication. In the event of a disaster, business operations can be switched over to a hot site almost immediately with minimal interruption.
This type of site is ideal for organizations with very low tolerance for downtime or data loss. However, the comprehensive infrastructure and continuous data synchronization involved make hot sites the most expensive option among disaster recovery alternatives.
2. Warm site
A warm site is a recovery facility that includes some pre-installed hardware and network connectivity, but it is not fully operational until additional setup is completed. Unlike a hot site, a warm site does not receive continuously synchronized data; it relies on periodic backups or replication instead. This means that during a disaster, organizations must first update or restore current data before resuming operations.
Warm sites offer a middle ground between cost and recovery time, making them a viable option for companies that need to recover within hours or days but do not require immediate failover capabilities.
3. Cold site
A cold site is a bare-bones facility with power, internet access, and physical space, but no installed IT infrastructure or live data. In the event of a disaster, the organization must deliver and install hardware, set up systems, and restore data from backups. This results in the longest recovery time among the three site types.
Cold sites are appropriate for non-critical operations or as part of a layered recovery strategy where full redundancy is not required.
Example: Choosing a recovery site
A financial institution that must resume customer transactions without delay maintains a hot site for near-instant failover. A regional office that can tolerate a short delay uses a warm site, restoring the latest backup data before resuming work. A small business with minimal uptime requirements uses a cold site, accepting a longer recovery time in exchange for lower cost.