The disaster recovery options with a hyper-converged today are:
- Multiple clusters utilizing Storage Replica
- Hyper-V Replica between clusters
- Backup and Restore
Multiple clusters utilizing Storage Replica
- Storage Replica enables the replication of volumes and supports both synchronous and asynchronous replication.
- synchronous replication, it will sequentially write to both ends at the same time.
- asynchronous replication, writes will replicate very fast but could still be lost.
- Storage Replica is a block level copy mechanism versus file level; meaning, it does not matter what types of data being replicated
- can utilize different types of drives between the replication partners
- can be run in Azure as well as on-premises.
The following considerations apply when deploying Storage Replica.
- Configuring replication is done outside of Failover Clustering
Choosing the method of replication will be dependent upon your network latency and RPO (Recovery Point Objective) requirement.
In the case of a disaster, failovers between the clusters are not automatic and need to be orchestrated manually through the Storage Replica PowerShell cmdlets
A new virtual machine or Scale Out File Server (SOFS) utilizing this data would need to be created inside Failover Cluster Manager on the replica partner.
Hyper-V Replica provides virtual machine level replication for disaster recovery on hyper-converged infrastructures.
How you wish the initial copy to be sent to the corresponding replica cluster(s).
- Send the initial copy over the network
- Send the initial copy to external media so that it can be copied onto your server manually
- Use an existing virtual machine already created on the replica hosts
Hyper-V Replica Broker
you must have the Hyper-V Replica Broker resource created in each cluster. This resource does several things:
- Gives you a single namespace for each cluster for Hyper-V Replica to connect to.
- Determines which node within that cluster the replica (or extended replica) will reside on when it first receives the copy.
- Keeps track of which node owns the replica (or extended replica) in case the virtual machine moves to another node.
Backup and restore
It is always a recommendation to have periodic backups of the hyper-converged infrastructure.
Methods for Restoring the cluster or the database
- If you only need to restore a cluster node (and the cluster registry database) and all current cluster information good, you would restore using non-authoritative.
- Non-Authoritative restores can be done through the Windows NT Backup interface or the command line WBADMIN.EXE.
- restore the node
- let it join the cluster.
- update the cluster information (run test cluster without storage test)
- takes the cluster configuration back in time.
- should only be accomplished when the cluster information itself has been lost and needs restored.
- Run WBADMIN.EXE
Wbadmin get versions
- Determine if the version backup you have has the cluster registry information in it as a component.
wbadmin get items -backuptarget:\\backupserver\location
- Start the authoritative restore to recover only the cluster registry version you need
wbadmin start recovery -version:01/03/2018-02:04 -itemtype:app -items:cluster
Once the restore has taken place, this node must be the one to start the Cluster Service first and form the cluster. All other nodes would then need to be started and join the cluster.