HADR Concepts Introduction
HADR Concepts Introduction
Recovery Concepts
Baro Technologies
After this module you will be able to
understand:
What is the
What is SOL Server What is SQL Server
difference between
High Availability Disaster Recover
High Availability and
(HA)? (DR)?
Disaster Recovery?
What is High Availability?
• Unplanned Downtime
• Datacenter failure
• Server failure
• I/O subsystem failure
• Human error
• Start planning now, because in almost all cases data loss can be
prevented and downtime can be minimized by using the
technologies in SQL Server.
Knowledge Check
1. What is High Availability?
Ans:- High availability is about putting a set of technologies into
place before a failure occurs to prevent the failure from affecting
the availability of data.
2. How many minutes of yearly downtime does "five nines"
translate to?
Ans- 5.26 minutes annually.
What is Disaster Recovery?
• High availability is not the same as disaster recovery, although the two terms are often
(erroneously) interchanged.
• High availability is about putting a set of technologies into place before a failure occurs in
order to prevent the failure from affecting the availability of data.
• Disaster recovery is about taking action after a failure occurs to recover any lost data and
to make the data available again.
What are the two main requirements for HA and DR?
• The two main requirements around high-availability are commonly known as RTO and RPO.
• RTO stands for Recovery Time Objective and is the maximum allowable downtime when a
failure occurs.
• RPO stands for Recovery Point Objective and is the maximum allowable data-loss when a
failure occurs.
What is your Disaster Recovery plan?
❖ Disaster recovery efforts address what is done to re-establish high
availability after the outage
❖ The scope of a sound disaster recovery plan should include:
• Granularity of failure and recovery.
• Investigative source material.
• Coordination of dependencies.
• Decision tree.
• Validation.
• Documentation.
• Recovery rehearsals.
• This type of documentation is commonly referred as a 'run book' or a 'cook
book
What are some common SOL solutions that
we had before?
• Database mirroring
• Log shipping
• Peer-to-Peer replication
• Failover Cluster Instances (FCI)
• AlwaysOn Failover