M55341A

Module 5
Overview of high
availability and disaster
recovery
 • Defining levels of availability
• Planning high availability and disaster recovery solutions
Module
with Hyper-V virtual machines
Overview • Backing up and restoring by using Windows Server Backup
• High Availability with failover clustering in Windows Server
Lesson 1: Defining levels of availability

What is high availability?

What is continuous availability?
What is business continuity?
Creating a disaster recovery plan
Highly available networking
Highly available storage
Highly available compute or hardware functions
What is high availability?

All parts of an application and the infrastructure it relies on must be highly

available:
• Data center infrastructure
• Server hardware
• Storage
• Network infrastructure
• Internet
• Network services
What is continuous availability?

• To provide continuous availability:

• Perform business impact analysis

• Perform risk analysis
• Perform application specific analysis
• Create different continuous availability strategies for different
applications
What is business continuity?

• Requirements for business continuity planning should include:

• SLAs for the IT systems

• Contact info and technical background of personnel assigned to recovery
• A secondary site
• Workaround solutions
• Maximum outages allowed for applications
Business continuity technologies and data collection

• You can collect business continuity data from:

• Business impact analysis
• Risk analysis

• Technologies for business continuity include:

• NLB
• Failover clustering on physical or virtual machines
• Application-aware high availability
• Conventional data backups
• Online backups
• Virtual machine backups
Creating a disaster recovery plan

• Developing a recovery plan includes:

• Performing a risk analysis
• Define what data should be recovered
• Define where data should be recovered
• Define when to recover data

• Recovery plan should be

• tested on a regular basis
• Recovery plan should be
• evaluated on a regular basis
SLA components

• SLA components can include:

• Hours of operation
• Service availability
• Recovery point objective
• Recovery time objective
• Retention objectives
• System performance
Highly available networking

• Planning for high availability in networking should include redundancy for:

• Network adapters
• Multipath I/O
• Local Area Network
• Wide Area Network
• Internet connectivity
Highly available storage

• When planning high availability for storage, consider following technologies:

• RAID
• DAS
• NAS
• SAN
• Cloud services
Highly available compute or hardware functions

• Consider using the high availability features that are built in to the operating system:

• Failover clustering
• Network Load Balancing
• RAID

• Follow the best practice guidelines and recommendations for the specific application
Lesson 2: Planning high availability and disaster
recovery solutions with Hyper-V virtual machines

High availability considerations with Hyper-V virtual machines

Overview of Live Migration
Live migration requirements
Demonstration: Configuring live migration (optional)
Providing high availability with storage migration
Demonstration: Configuring storage migration (optional)
Overview of Hyper-V Replica
Planning for Hyper-V Replica
Implementing Hyper-V Replica
High availability considerations with Hyper-V virtual machines

High availability options Description

Host clustering • Virtual machines are highly available
• Does not require virtual machine operating system or
application to be cluster aware

Guest clustering • Virtual machines are failover cluster nodes

• Virtual machine applications must be cluster aware
• Requires iSCSI or virtual Fibre Channel interface for
shared storage connections

NLB • Virtual machines are NLB cluster nodes

• Use for web-based applications
Virtual machine migration options

• Available options for moving virtual machines are:

• Virtual machine and storage migration

• Quick Migration
• Live Migration
• Hyper-V Replica
• Export or import of a virtual machine
Overview of live migration
Live migration requirements

• Live migration requirements include:

• Live migration enabled

• Host computers processor requirements
• Host computers domain membership and user accounts configured
• Hyper-V roles and management tools installed
• Host computers authentication configured
• Host computers performance, network, and bandwidth configured
Demonstration: Configuring live migration
(optional)

In this demonstration, you will see how to enable and configure live migration
Providing high availability with storage migration

• Virtual Machine and Storage Migration technology enables you to move a

virtual machine and its storage to another location without downtime.

• During migration, the virtual machine hard disk is copied from one location to another
• Changes are written to both the source and destination drive
• You can move virtual machine storage to the same host, another host, or an SMB
share
• Storage and virtual machine configuration can be in different locations
Demonstration: : Configuring storage
migration (optional)

In this demonstration, you will see how to enable and configure storage migration
Overview of Hyper-V Replica
Planning for Hyper-V Replica

• Use Hyper-V Replica features in Windows Server to:

• Change the replication frequency to either 30 seconds, 5 minutes, or 15 minutes

• Extend replication to include a third host
Implementing Hyper-V Replica

• Hyper-V Replica has the following prerequisites:

• The server hardware supports the Hyper-V role on Windows Server

• Sufficient storage exists on both the primary and replica servers
• Network connectivity exists between the locations that host the primary and replica
servers
• Firewall rules are correctly configured to enable replication between the primary and
replica sites (default is TCP port 80 or 443).
• An X.509v3 certificate exists to support Mutual Authentication with certificates
Enabling a Virtual Machine for Replication – 1/2
• Replication is enabled per virtual machine
• Enable Replication Wizard
• Replica server
• Connection parameters
• Choose replication VHDs
• Chose replication frequency
• Configure additional recovery points
• Choose initial replication method
• Failover TCP/IP Settings
• Preconfigure IP address for replica virtual machine
• Requires integration services
• Should be configured on both the primary and replica server
Enabling a Virtual Machine for Replication – 2/2
Demonstration: Implementing Hyper-V
Replica (optional)

In this demonstration, you will see how to implement Hyper-V Replica

Hyper-V Replication Health – 1/3
• Normal
• Less than 20% replication cycles are missed
• Last synchronization point was less than an hour ago
• Average latency is less than the configured limit
• Warning
• More than 20% of replication cycles have been missed
• More than hour since the last send replica
• Initial replication has not been completed
• Failover initiated, but not ‘reverse replication’
• Primary virtual machine replication is paused
• Critical
• Replica paused on the replica virtual machine
• Primary server unable to send the replica data
Hyper-V Replication Health – 2/3

Number of replications based on replication frequency

Replication frequency 1 hour 12 hours 24 hours 1 week
30 seconds 120 1,440 2,880 20,160
5 minutes 12 144 288 2,016
15 minutes 4 48 96 672

Successful replications for Normal replication health

Replication cycles Successful Failed % Success Replication health
12 10 2 80 Normal
144 116 28 80 Normal
288 231 57 80 Normal
2,016 1,613 403 80 Normal
Hyper-V Replication Health – 3/3
Test Failover, Planned Failover, and Failover – 1/2

• Test failover
• Non-disruptive testing, with zero downtime
• New virtual machine created in recovery site
• From the replica checkpoint
• Turned off and not connected
• Stop Test Failover
• Planned failover
• Initiated at primary virtual machine, which is turned off
• Sends data that has not yet been replicated
• Fail over to replica server
• Start the replica virtual machine
• Reverse the replication after primary site is restored
Test Failover, Planned Failover, and Failover – 2/2

• Failover
• Initiated at the replica virtual machine
• Primary virtual machine has failed (turned off or unavailable)
• Data loss can occur
• Reverse the replication after the primary site is recovered
• Other replication-related actions
• Pause Replication and Resume Replication
• View Replication Health
• Extend Replication
• Remove Recovery Points
• Remove Replication
Hyper-V Replica Resynchronization

• When normal replication process is interrupted

• Change tracking issues on primary server
• Replication issues with tracking logs
• Problems linking virtual hard disk with parent
• Time travel – virtual machine restored from backup
• Reverse replication after failover process
• Processor, storage, and network intensive
• Configured on primary virtual machine
• Manual, automatic, or during scheduled time
• If more than 6 hours, perform full initial replication
What Is the Hyper-V Replica Broker Role?
Lab: Planning and implementing a high availability and disaster recovery
solution
Lab scenario

Adatum Corporation is looking to assess and configure the new high availability features and
technologies that they can leverage. As the system administrator, you have been tasked with
performing that assessment and implementation.

Objectives

Exercise 1: Exercise 2: Exercise 3:

Determine the Implementing Configuring Hyper-V
appropriate high storage migration Replicas
availability and
disaster recovery
solution
 How can you extend Hyper-V Replica in Windows Server?
Lab Review
What is the difference between Live Migration and Storage
Migration?
Lesson 3: Backing up and restoring by using
Windows Server Backup

Overview of Windows Server Backup

• Implementing backup and restore
Overview of Windows Server Backup

• By using Windows Server Backup you can:

• Perform a full server backup and bare-metal restore
• Back up and restore system state
• Back up and restore individual files and folders
• Exclude selected files or file types
• Select from more storage locations
• Perform a Microsoft Azure Online Backup
Implementing backup and restore

• Backup and restore operations include:

• Backing up and restoring Hyper-V hosts
• Backing up and restoring VMs
• Backing up and restoring AD DS, file servers, and web servers
• Azure Site Recovery
Lesson 4: High availability with failover clustering
in Windows Server

What is failover clustering?

High availability with failover clustering
Clustering terminology
Clustering categories and types
Failover clustering components
• Technology redundancy comparison
What is failover clustering?
Failover Cluster Networks

• Have at least two network paths between nodes

• Multiple (fast) network cards are recommended
• Can use NIC Teaming and virtual network adapters
• Cluster network types:
• Allow cluster network communication on this network
• Allow clients to connect through this network
• Do not allow cluster network communication
• Single network can support intranode and clients
• Not recommended
• Failover Cluster Virtual Adapter
• Fault-tolerant connections across all available interfaces
• Similar to an internal NIC Teaming for clustering
What Is CSV?

• A LUN is owned by single node at any time

• Multiple nodes can access a CSV simultaneously
• Application failover without drive ownership change
• Concurrent access to a single file system
• Single consistent file namespace across cluster nodes
• Better use of disk space
• Virtual machine resources in a single logical location
• No special hardware is required
• Simple CSV setup
• Hyper-V, SQL Server, and file server can use CSV
• Use Storage Spaces to deploy CSV
• Deduplication and tiered storage spaces are supported
What Is Encrypted Cluster Volume?

• BitLocker-encrypted cluster disks

• Support for traditional failover disks and CSV
• Can be enabled before or after a disk is added
• Add the failover cluster AD DS identity as a BitLocker protector to the target
disk volumes
• Minimal performance impact
• Requirements
• BitLocker is installed
• BitLocker PowerShell module or Manage-BDE
Technology redundancy comparison

Hardware Data deletion/ Automatic

Zero Downtime Site Failures
Failures corruption failover

Live Migration Yes No No No No

Depends on Depends on
Clustering Yes No Yes
application application

Hyper-V Depends on
No Yes Yes No
Replica application

Windows Server Depends on

No Yes Yes No
Backup scenario
 Review Questions
Module Review
and Takeaways Tools
• Common Issues and Troubleshooting Tips
End of presentation