A device must be in failover mode to stop it.
You can only stop failover for the devices displaying either Test failover successful or Test failover failed as Failover state.
Stopping failover deactivates the DRaaS machines and switches the backup manager to restore-only mode. You must manually re-enable continuous restore for this device in the DRaaS dashboard so you can power on your new production devices.
Test failover
Click Stop failover to power off the machines and roll back to the snapshot taken when failover started.
This re-enables continuous restore.
Production failover
Click Stop failover to power off the machines without a snapshot rollback (since no snapshots are created).
This is tied to the failback procedure, wherein the production servers are down, and you temporarily run your workload in our cloud.
To get the environment back to its original configuration (to complete the restoration procedure of your On-Prem environment) prior to initiating stop failover:
- Verify that the backups of the DRaaS production failover machines are enabled and check the latest session
- Stop the DRaaS production failover VM
- Once ready, perform a one-time restore (virtual environment) or bare-metal restore
- You can now initiate stop failover
External Access During Failover For Production failover (full or partial), when your DR site becomes your primary site (up to 30 days), customers outside of your DR network would need to access services running on your DR servers. In this case, you can set up public IPs and configure inbound/outbound rules with the help of the service team.