5. Implement High Availability Flashcards
Hyper-v Replica
Allows you to create highly available VMs locally or on a remote site through asynchronous or synchronous replication of storage.
Hyper-v replica works off of snapshots so after the initial replication the only thing that needs to be sent over the network is the checkpoint.
kerberos
replica traffic will not be encrypted and the servers must be joined to the same or trusted domains.
requires constrained delegations to be established in active directory.
do not need to be signed into the server you are migrating from.
certification-based authentication
uses certificates for authentication for encrypted replica over the network. you can either self-sign certificates or have them signed externally.
Live migration
A feature that makes it possible to move a virtual machine from one hyper-v host to another while it is running with almost no interruption of service.
this is not a replacement for hyper-v replica because it does not move the virtual machines data files.
Simultaneous live migrations
allows you to specify how many live migrations the server can perform at the same time based on the bandwidth and traffic levels on the server. the default is 2 live migrations at a time.
credssp
an authentication protocol that does not require constrained delegations to be established.
requires that you be signed into the server you are migrating from.
shared nothing live migration
allows you to move vms that do not have shared storage by moving the storage alongside the vm.
basically a storage migration then a live migration.
must be members of the same or trusted domain.
the source and domain must be using the same processor family amd vs intel
minimum 1gb network
virtual switches should be configured identically between servers.
Storage migration
the process of moving vm storage to another vm.
Failover clustering
a group of two or more computers, physical or virtual, and runnin the same application that functions on a single entity to provide high availability, scalability, and fault tolerances.
64 computers
8000 virtual machines
1024 vms per node.
Single domain cluster
all of the servers in the failover cluster are joined to the same domain.
Multi-domain cluster
a failover cluster with servers running in multiple different domains.
workgroup cluster
a failover cluster of computers not joined to a domain at all.
SQL would work well in a domainless cluster.
file servers would not work well in a domainless cluster.
Quorum
a voting system in a cluster to prevent a split-brain scenario. The quorum keeps one side of the cluster up because it has a majority vote.
Disk witness
a dedicated disk in the cluster’s shared storage that contains a copy of the cluster database.
file share witness
an SMB file share on a windows server with a witness.log file containing information about the cluster.
cloud witness
a blob stored in azure that is designed for stretch clusters split among multiple data centers and remote sites. the purpose of the cloud witness is to remain independent of all of the data centers.
Dynamic Quorum Management
designed to function so that when a node leaves a cluster its vote leaves with it so that the cluster cna stay up without taking itself offline. allows a cluster to continue functioning until all of the nodes have failed.
Client Communication
Clients access to the application running on the cluster are the highest priority and this is usually the default shared network.
Cluster communication
cluster communication is the next highest networking priority. if the cluster cannot communicate with itself and register heartbeats the cluster will go down.
storage traffic
iSCSI and other types of storage traffic should be separated from all other types of traffic on the cluster network.
cluster storage types
Fibre Channel
SAS
iSCSI
cluster aware updating
allows you to update clusters with minimum downtime.
remove all active roles from a node then update it. bring the node online and do the same to the next one until you reach the final node.
self updating mode
a node in the cluster has the CAU role and starts to update all of the nodes in the cluster. when the CAU reaches itself it fails over and a new node assumes the role and updates the old CAU.