Failover is not supported for machines linked to a hypervisor or protected agentlessly. (4375922)

Failover is not supported for machines linked to a hypervisor or protected agentlessly.

Machines protected using the Agent software and that has been replicated to a disaster recovery (DR) site can be promoted to replace a system that is temporarily unavailable. Process can then be reverted when the original system is functional again. However, with Agents linked to a hypervisor for licensing purpose, this procedure is not applicable. When selected the Failover option for the system on the replication Core.

When using the failover procedure, the replication Core take over the protection of the system. When an Agent is linked (or protected agentless), the Core will also require to protect the hypervisor. However, there could be conditions that could be prevent the hypervisor to be protected on the DR site. Consequently, the failover/failback procedure is restricted for standalone systems protected with the Agent software.

Enhancement request RR-111518 has been issue to validate if the system is a linked Agent, so a specific error message would be displayed for this situation.

The following will be procedure to follow in a disaster recovery scenario where functionality will failover to the replicated system:

1. On the target Core, navigate to the replication screen.
2. On the Incoming Replication table, expand the job for the source Core.
3. Click the drop down to the right of the linked Agent and select Delete. Keep the existing recovery points.
4. If there isn't a virtual standby created for the fallen machine, run a one-time export to create a clone of the failed system.
5. Start the virtual machine and configure as needed.
6. Add the Agent to protection on the target Core; protection should resume (the next snapshot taken should be an incremental recovery point, not a base image).

When functionality has been restored on the main site, follow these steps on the source Core to take back protection of the linked Agent:

1. Create or add the linked agent to a replication job that will send the recovery points taken by the target core to the source one; for the meantime, the Core roles will be reversed.
2. It is preferable to delete and re-create the affected Agent on the virtual environment. Wait for the last recovery point to be replicated to run a continuous export job. After the virtual standby system has been created, check if new recovery points have been replicated and allow the changes to be applied on the standby machine.
3. Remove the system from the replication job.
4. Stop the system on the target site, and power on the virtual standby machine. Update the configuration as required.
5. Protect the system on the source Core, and link it to its hypervisor for licensing purpose.
6. Re-add the system to the original replication job.