You cannot start two failovers at the same time.
Prerequisites
Before starting failover of a Cove Data Protection (Cove) DRaaS device, ensure:
- No restore is in progress
If a restore is in progress, we recommend you wait until it finishes before starting failover. Alternatively, you can Cancel the restore in progress but then you must Rollback to the latest backup session.
- The last restore session was successful (green)
- The failover devices belong to the same customer
- Pause continuous restores
Instructions
- Sign in to the Management Console using a SuperUser or Manager account.
- Navigate to Continuity > DRaaS > Overview
- Select the device to failover and then click Start Failover from the top bar
- Select whether the failover is a Test failover or a Production failover
- Test failover: Use this when you simply need to start the machine for access to file system or when you want to simulate failover scenarios
- Production failover: Use this in a real disaster scenario for partial or full failover. Partial failover temporarily replaces some production servers with disaster recovery servers, full failover starts the entire infrastructure in our Disaster Recovery (DR) facility to maintain business continuity
For Production failover, the subnet and IP settings work the same as in Test failover. Test failover use less powerful VMs (2 CPUs and 8GB RAM for Test vs 4 CPUs and 16GB RAM for Production) and may eventually auto-manage uptime (e.g., power off machines with no traffic), whereas for Production failover, you would be contacted before taking such action. You can request to resize the VMs to more powerfull by creating a support ticket and providing justification. It will be provisioned based on capacity up to 16 CPUs 64 GB RAM.
- Click Next
- Enter Subnet
The on-premises subnet which you are going to connect to the DR site. This must be the same subnet used when deploying the VPN appliance
- Enter Cloud Gateway IP
Specify a spare or unused IP address from the subnet
- Failover compatibility will provide information on whether the device is compatible or incompatible for failover. If the devices fall into one of the following scenarios, they will be incompatible for failover:
- The devices are added to the DRaaS plan under the same Customer but at least one of them has its Failover state as Provisioning with Recovery Status as Scheduled/In Progress/Failed/Retrying.
The device must have had a successful restore to be compatible for failover.
- The devices are added to the DRaaS plan under the same Customer but at least one of them has its Failover state as Standby with Recovery Status as Failed. The device cannot start failover because it does not have a successful restore. Roll back the device to a previous restore point or ensure a restore completes successfully to proceed with failover.
If the last session failed, perform a rollback. To rollback, select the device, click Rollback, choose the last successful session, and proceed. Once rolled back, the device is paused and ready for failover.
- The devices are added to the DRaaS plan under the same Customer but at least one of them has its Failover state as Standby with Recovery Status as Retrying. Failover cannot be started while a recovery is in retrying mode. Wait for the recovery to complete, or cancel the recovery and then initiate a rollback before starting failover.
- The devices are added to the DRaaS plan under the same Customer and at least one of them has its Failover state as Standby with Recovery Status as In-Progress. Failover cannot be started while a recovery is in progress. Wait for the recovery to complete, or cancel the recovery and then initiate a rollback before starting failover.
- The devices are added to the DRaaS plan under the same Customer but at least one of them has its Failover state as Complete with Recovery Status as RUNNING. Failover can only be started for a device with continuous restores paused. Stop continuous restores to proceed with failover.
- The devices are added to the DRaaS plan under the same Customer but at least one of them has its Failover state as Standby with Recovery Status as Cancelling/Cancelled. Failover cannot be started due to an incompatible recovery status. Only devices with a recovery status of Completed or Completed with Errors are eligible for failover.
- The devices are added to the DRaaS plan under the same Customer but at least one of them is already in Failover.
- The devices are added to the DRaaS plan under the same Customer but at least one of them has its Failover state as Provisioning with Recovery Status as Scheduled/In Progress/Failed/Retrying.
- Confirm the device has an appropriate amount of Failover time remaining
If you stop the Virtual Machine, but do not stop the failover, this is still counted towards the failover time used, and so reflected in the failover time remaining.
- The Device IP address will pre-populate with the default IP of the device, confirm this is correct.
- Turn Allow VPN connection on or off if you need the device to connect to the VPN network when device is in failover
- Turn Allow outbound internet access on or off if you need the device to be accessed by the internet when device is in failover
- Click Next
- Confirm the Failover Summary and click Start failover
- Once Failover has been initiated, you can now click Done to close the wizard. The device failover will appear in the dashboard once the wizard is closed:
After clicking Start Failover, the system creates the subnet, assigns IPs, starts the machines, and updates the DRaaS dashboard with the Virtual Machine (VM) status (started/stopped). Once the VM is started and the agent is ready, additional button Stop VM appear.
You can Stop/Start VMs when device is in failover.
: If machine does not start, please contact N-able support for assistance.
If there is a requirement to add one more device to a failover which is in progress, when you click Start Failover for this device, the subnet is going to be pre-populated (because failover is in progress already. However you can change/specify the device’s IP
While Cove DRaaS is in public preview, it is only possible to connect to the machine in failover by deploying the VPN appliance and establishing a tunnel to the DR site.