Definition: Disaster recovery is an IT non-functional requirement that ensures that a system can recover from any catastrophic event or disaster, such as natural disasters, power outages, or cyber-attacks. This requirement involves creating a plan and implementing strategies to minimize the impact of such events on the system's functionality and data. The disaster recovery plan should include backup and recovery procedures, redundant systems, and failover mechanisms to ensure that the system can quickly and efficiently recover from any disaster. The goal of disaster recovery is to minimize downtime, data loss, and ensure business continuity.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Disaster Recovery is a non-functional requirement that refers to the ability of an IT system to recover from a catastrophic event or disaster. This requirement is essential for ensuring the continuity of business operations and minimizing the impact of disruptions on the organization.
The Disaster Recovery requirement includes the following elements:
1. Recovery Time Objective (RTO): This refers to the maximum amount of time that the IT system can be down before it must be restored to full functionality. The RTO is typically measured in hours or days and is determined by the criticality of the system to the business.
2. Recovery Point Objective (RPO): This refers to the maximum amount of data loss that the organization can tolerate in the event of a disaster. The RPO is typically measured in minutes or hours and is determined by the criticality of the data to the business.
3. Backup and Recovery Procedures: This refers to the processes and procedures that are in place to backup and restore the IT system in the event of a disaster. These procedures must be tested regularly to ensure that they are effective and can be executed quickly and efficiently.
4. Disaster Recovery Plan: This refers to the overall plan that outlines the steps that must be taken to recover the IT system in the event of a disaster. The plan must be comprehensive and include all necessary information, such as contact information for key personnel, backup and recovery procedures, and communication protocols.
5. Testing and Maintenance: This refers to the ongoing testing and maintenance of the Disaster Recovery plan and procedures to ensure that they remain effective and up-to-date. Testing must be conducted regularly to identify any weaknesses or gaps in the plan and to ensure that all personnel are familiar with their roles and responsibilities.
Overall, the Disaster Recovery requirement is critical for ensuring the continuity of business operations in the event of a catastrophic event or disaster. Organizations must ensure that they have a comprehensive plan in place that includes backup and recovery procedures, testing and maintenance, and clear communication protocols to minimize the impact of disruptions on the organization.
Example: In the event of a natural disaster or system failure, the system must be able to recover all data and functionality within 24 hours with minimal data loss.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DisasterRecoveryRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:DisasterRecoveryRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/DisasterrecoveryRequirement
dct:title: Disaster recovery Non-Functional Requirement
|
|
dct:modified | 2024-01-28 |
dct:identifier | http://data.europa.eu/dr8/egovera/DisasterrecoveryRequirement |
dct:title | Disaster recovery Non-Functional Requirement |
skos:example | In the event of a natural disaster or system failure, the system must be able to recover all data and functionality within 24 hours with minimal data loss. |
skos:definition | Disaster recovery is an IT non-functional requirement that ensures that a system can recover from any catastrophic event or disaster, such as natural disasters, power outages, or cyber-attacks. This requirement involves creating a plan and implementing strategies to minimize the impact of such events on the system's functionality and data. The disaster recovery plan should include backup and recovery procedures, redundant systems, and failover mechanisms to ensure that the system can quickly and efficiently recover from any disaster. The goal of disaster recovery is to minimize downtime, data loss, and ensure business continuity. |
eira:concept | eira:ArchitectureBuildingBlock |
eira:definitionSource | TOGAF |
eira:definitionSourceReference | https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html |
skos:note | According to the TOGAF specification, Disaster Recovery is a non-functional requirement that refers to the ability of an IT system to recover from a catastrophic event or disaster. This requirement is essential for ensuring the continuity of business operations and minimizing the impact of disruptions on the organization.
The Disaster Recovery requirement includes the following elements:
1. Recovery Time Objective (RTO): This refers to the maximum amount of time that the IT system can be down before it must be restored to full functionality. The RTO is typically measured in hours or days and is determined by the criticality of the system to the business.
2. Recovery Point Objective (RPO): This refers to the maximum amount of data loss that the organization can tolerate in the event of a disaster. The RPO is typically measured in minutes or hours and is determined by the criticality of the data to the business.
3. Backup and Recovery Procedures: This refers to the processes and procedures that are in place to backup and restore the IT system in the event of a disaster. These procedures must be tested regularly to ensure that they are effective and can be executed quickly and efficiently.
4. Disaster Recovery Plan: This refers to the overall plan that outlines the steps that must be taken to recover the IT system in the event of a disaster. The plan must be comprehensive and include all necessary information, such as contact information for key personnel, backup and recovery procedures, and communication protocols.
5. Testing and Maintenance: This refers to the ongoing testing and maintenance of the Disaster Recovery plan and procedures to ensure that they remain effective and up-to-date. Testing must be conducted regularly to identify any weaknesses or gaps in the plan and to ensure that all personnel are familiar with their roles and responsibilities.
Overall, the Disaster Recovery requirement is critical for ensuring the continuity of business operations in the event of a catastrophic event or disaster. Organizations must ensure that they have a comprehensive plan in place that includes backup and recovery procedures, testing and maintenance, and clear communication protocols to minimize the impact of disruptions on the organization. |
eira:PURI | http://data.europa.eu/dr8/DisasterRecoveryRequirement |
dct:type | eira:DisasterRecoveryRequirement |
eira:view | Digital Solution Non-Functional Requirements Catalogue view |
eira:eifLayer | N/A |
skos:broader | http://data.europa.eu/dr8/DigitalSolutionNonFunctionalRequirementRequirement |