Key Concepts 7.10 and 7.11 Implement recovery strategies/Implement disaster recovery processes Flashcards

Domain 7 (36 cards)

1
Q
  • Scope and requirements. Identifying critical data and systems that require backup
    protection, which will influence the backup solutions selected.
  • Backup methodology. Selecting appropriate backup methods (e.g., full, incremental,
    differential) based on recovery time objectives (RTO) and recovery point objectives (RPO).
  • Storage media. Implementing secure and redundant backup storage solutions (e.g., disk,
    tape, cloud).
  • Periodic testing. Testing backup integrity and recoverability regularly to ensure effectiveness.
  • Security. Encrypting backup data to protect against unauthorized access or disclosure.
A

Key Considerations for Backup Storage Strategies

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

is a backup strategy that automatically transfers data in bulk to an offsite
storage facility over a network connection, typically used for critical data that needs frequent
backups and provides quick recovery in case of data loss. Due to the quantity of data, data
may not be immediately available for recovery

A

Electronic vaulting

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

continuously records changes made to data in real-time and transmits these changes to a remote backup site, allowing for point-in-time recovery and maintaining
an up-to-date copy of data offsite.

A

Remote journaling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

creates an exact copy of data at a remote location, either synchronously (in
real-time) or asynchronously (with a slight delay), providing a fully functional duplicate of the
primary system ideal for disaster recovery and high availability needs.

A

Remote mirroring

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q
  • A backup copies all selected files and data from your system.
  • Frequency: Typically done less frequently due to size and time.
  • Restore: Restoring data requires only the most recent full backup.
A

Full Backup

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q
  • Backs up only the data that has changed since the last backup, whether it was a full
    or another incremental backup.
  • Frequency: Can be done more frequently because it’s smaller in size.
  • Restore: Requires the most recent full backup plus all subsequent
    backups to restore data fully.
A

Incremental Backup

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Backs up all data that has changed since the last full backup.
* Frequency: More frequent than full but less than incremental in terms of data size
growth.
* Restore: Needs only the most recent full backup and the latest backup to
restore data, simplifying the restore process compared to incremental

A

Differential Backup

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

is essentially just data center space, power, and network
connectivity that’s ready and waiting for whenever you might need it. It’s essentially a
standby facility with no preinstalled hardware or software.
TO RECOVER: If disaster strikes, your engineering and logistical support teams can
readily help you move your hardware into the data center and get you back up and
running.

A

Cold Site

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

allows you to pre-install your hardware and pre-configure
your bandwidth needs. TO RECOVER: If disaster strikes, all you have to do is load your software and data to restore your business systems.

A

Warm Site

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

allows you to keep servers and a live backup site up and
running in the event of a disaster. You replicate your production environment in that data
center. TO RECOVER: This allows for an immediate cutover in case of disaster at your primary site. A hot site is a must for mission critical sites.

A

Hot Site

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q
A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

is a company that leases computer time. Own large server farms and often fields of workstations.

A

service bureau

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

sometimes called reciprocal agreements, provide
an inexpensive alternative to disaster recovery sites. It poses a risk to organizations
participating, as multiple organizations may also be shut down by the same disaster.
It raises confidentiality concerns. They are also considered difficult to enforce. For all these reasons, they are relatively uncommon.

A

Mutual assistance agreements (MAAs)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

is any component that, if it fails, will cause the entire
system to fail. Identifying and eliminating it is crucial for improving availability

A

Single Point of Failure (SPOF)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

This refers to a system’s ability to maintain acceptable performance levels during and after disruptions. It involves designing systems to adapt to changing conditions
and recover quickly from failures.

A

System Resilience

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

This refers to a system’s ability to continuously operate without experiencing
significant downtime. It’s achieved through redundancy and fault tolerance, ensuring that if
one component fails, another can take over seamlessly. This often involves redundancy and
rapid failover mechanisms.

A

High Availability

17
Q

system continues to operate correctly even when one or more
of its components fail. This typically involves redundancy and the ability to detect and isolate
faults.

A

Fault Tolerance

18
Q

Improves read/write performance through disk striping, but doesn’t offer redundancy.

19
Q

Provides redundancy through disk mirroring.

20
Q

Offers better storage efficiency with distributed parity.

21
Q

Combines mirroring (RAID 1) and striping (RAID 0) for both performance and
redundancy.

22
Q

Multiple servers work together as a single system. Clustering is a strategy commonly used with database servers

23
Q

Distributes workloads across multiple servers. It is
commonly used with web servers (HTTPS), but generally support other protocols

A

Load Balancing

24
Q

involves creating alternate paths for network traffic, often using redundant
switches, routers, and connections. Two sources of internet connectivity for a facility,
entering the site at opposite ends of the facility, will reduce odds that both are impacted by a
single event.

A

Network Redundancy

25
includes using uninterruptible power supplies (UPS) and backup generators to ensure continuous power supply.
Power Redundancy
26
involves implementing monitoring systems, predictive maintenance, and rapid replacement procedures. Automated recovery (systems designed to self-heal or failover automatically) is generally preferable to manual recovery (human intervention to restore systems).
Hardware/Software Failure Management
27
phase of disaster recovery involves the initial actions taken to assess the impact of the event, activate the disaster recovery plan, and mobilize the necessary resources. Key considerations for the this phase include: * Establishing clear roles and responsibilities for the disaster recovery team and other key stakeholders. * Conducting an initial assessment of the scope and severity of the event to inform response prioritization and resource allocation. * Activating the disaster recovery plan and notifying relevant parties (e.g., employees, customers, vendors). * Implementing emergency response procedures to ensure the safety and well-being of personnel and protect critical assets.
Response
28
is a critical aspect of disaster recovery, as the availability and effectiveness of key staff can significantly impact the success of recovery efforts. Important considerations for it include: * Identifying and training key personnel in their disaster recovery roles and responsibilities * Establishing clear communication and coordination protocols for personnel during a disaster event * Ensuring that personnel have the necessary resources and support to perform their duties effectively (e.g., equipment, access, transportation) * Providing support for personnel well-being and stress management during and after the disaster event
Personnel management
29
is essential for coordinating response and recovery efforts, managing stakeholder expectations, and minimizing confusion and misinformation during a disaster event. Key aspects include: * Establishing clear communication channels and protocols for internal and external stakeholders. * Developing pre-scripted messaging templates for various disaster scenarios to ensure consistent and accurate information dissemination. * Leveraging multiple communication methods (e.g., email, phone, text, social media) to reach all relevant parties using the medium most appropriate/comfortable for them. * Regularly updating stakeholders on the status of recovery efforts and any changes to the recovery timeline or objectives.
Communications
30
is an ongoing process throughout the disaster recovery lifecycle, involving the evaluation of the event’s impact, the effectiveness of the response and recovery efforts, and the identification of areas for improvement. Important aspects of it include: * Conducting a thorough post-event analysis to document the timeline, impact, and root causes of the disaster. * Evaluating the performance of the disaster recovery plan and identifying any gaps or deficiencies in the response and recovery processes. * Assessing the financial, operational, and reputational impacts of the disaster event. * Identifying opportunities for improvement and updating the disaster recovery plan and processes accordingly.
Assessment
31
Focuses on ensuring business continuity in the immediate aftermath of a disaster by establishing operations at a secondary site.
Recovery
32
Involves rebuilding and repairing the primary site to its original state, allowing the organization to eventually return to normal operations
Restoration
33
is primarily responsible for ensuring business continuity in the aftermath of a disaster. – Swift Implementation of the Disaster Recovery Plan (DRP): The recovery team must quickly activate the DRP to guide the organization’s response. – Restoring IT Capabilities: They work to restore essential IT systems and infrastructure at the recovery site, enabling critical business functions to resume operations. – Meeting Time-Sensitive Metrics: The recovery team is often under strict time constraints (MTD/RTO) to minimize business disruption. Failure to meet these deadlines can have severe consequences for the organization.
Recovery Team
34
is tasked with restoring the primary site to operational capacity after a disaster. Their focus is on: – Repairs and Restoration: The salvage team works to repair damaged infrastructure, equipment, and facilities at the primary site. – Data Recovery: They may also be involved in recovering lost or corrupted data from the primary site. – Preventing Recurrence: The salvage team may implement measures to reduce the likelihood of future disasters or minimize their impact.
Salvage Team
35
are critical for ensuring that personnel are prepared to effectively respond to and recover from a disaster event. Important aspects of training and awareness include: * Providing regular training and education on disaster recovery roles, responsibilities, and procedures for all relevant personnel. * Conducting tabletop exercises and simulations to practice and validate the effectiveness of the disaster recovery plan. * Raising awareness of potential disaster scenarios and the importance of preparedness and resilience among all employees. * Updating training and awareness programs based on lessons learned from actual events and industry best practices.
Training and awareness
36
is essential for continuously improving an organization’s disaster recovery capabilities. Key considerations for lessons learned include: * Conducting post-event reviews and debriefs to gather feedback and insights from personnel involved in the response and recovery efforts. * Documenting and analyzing the successes, challenges, and areas for improvement identified during the disaster event. * Sharing lessons learned with relevant stakeholders and incorporating them into future training and awareness programs. * Updating the disaster recovery plan and processes based on the lessons learned to enhance the organization’s preparedness and resilience.
Lessons learned