Recovering After a Failover Event

Overview#

After an evacuation event completes, the next steps depend on whether you can recover the source compute resource:

• If you cannot recover the source compute resource, delete it from Compute Resources to avoid IP and network conflicts.
• If the source compute resource comes back online, you can manually migrate the evacuated virtual servers back to it.

To review the outcome of an evacuation event before you act on it, see Monitoring High Availability Activities.

Move Virtual Servers Back to the Source Compute Resource#

Once the source compute resource is back online, you can migrate the evacuated virtual servers back to it.

To move the virtual servers back to the source compute resource, perform the following steps:

1. Go to High Availability > Activities.
2. Locate the evacuation event.
3. Select the compute resource or specific virtual servers that you want to move back.
4. Click Move back .

If the move back fails, see Troubleshooting: A move back action fails.

Retry a Failed Evacuation#

If a compute resource (or a virtual server) failed to migrate during an evacuation event, you can retry the migration.

Before retrying, verify that at least one destination compute resource in the failover domain is online and has sufficient CPU and memory.

To retry a failed evacuation, perform the following steps:

1. Go to High Availability > Activities.
2. Locate the event with virtual servers that failed to migrate.
3. Select the checkboxes for the virtual servers you want to retry, or select the event row to retry all failed migrations.
4. Click Retry .