- Key Features
- VM Backup
- Agentless VM Backup
- Backup VMs on Standalone Host
- Backup VMs on Hyper-V Cluster
- Backup VMs on CSV
- Backup VMs on SMB
- Backup Storage Targets
- RTO RPO < 15 mins
- VM/Disk Exclusion
- Application-aware Backup
- Flexible Backup Scheduling
- RCT based Incremental Backup
- Synthetic Full Backup
- Basic Retention
- GFS Retention
- Backup Data Encryption
- VM Backup to Cloud
- Create Backup using Template
- VM Recovery
- VM Replication
- Disaster Recovery
- Management
- Backup Settings
VM Failover
BDRSuite’s VM Replication feature lets you replicate business critical VMs from one Hyper-V host to another host on the same or different site.
In the event of a VM crash or any other disaster, the VM Failover feature allows you to instantly start the replicated VM on another site.
How it works
Failover process switches the workload to the replica VMs from the source VM for a while, when the source VM is temporarily not available due to corruption or system crash. After failing over to the replica VM, it will act as source machine and handles all the production activities temporarily.
If the VM replication is configured with Network and IP-Remapping, the replica VM will run with the configured Network & IP configurations during the failover process.
You can failover the replica VMs to any of its available recovery points, and it is also possible to failover to a group of replica VMs which are actually dependant on one another that are available in the configuration.
The data created after failover will be maintained in a snapshot delta file which will be committed/reverted later based on the requirement.
Failover is a temporary state that may be further finalized using any of the below processes
- Undo Failover
- Permanent Failover
Undo Failover
Undo Failover is a process of reverting back the replica to its original state before a failover. The data added after failing over to the replica VM will be terminated after the Undo Failover process.
Undo Failover might be useful if the replica failover was initiated for testing purposes or if you get the original production server back after troubleshooting and if you don’t want the data that has been added after the failover process.
Permanent Failover
In case the source machine is not recoverable after a disaster or you want to continue business operations with the replica VM itself, then you can use the permanent failover option. Permanent Failover allows you to use the replica VM for production purposes permanently instead of source VM.
All changes made during the failover process will be committed to the disk when a permanent failover is done. So, all the snapshots of the replica VMs will be consolidated. Further incrementals will be blocked for the replica VM after the permanent failover process and the VM will be excluded from the VM replication job.
Featured Links