Failback Operation Fails Due to Offline or Faulty Host in Cluster

This article applies to all JSDR software versions.

Problem

A failback operation may not be able to complete if a host in the cluster is offline or faulty.

Example of a problem completing failback.

Issue

Failure Scenarios

The following scenarios illustrate cases that result in the failure of the failback operation.

Faulty Node

• In a multi-node cluster, if one node is faulty then failback will not start.

IO Filter Unavailable

• In a multi-node cluster, all hosts are healthy but one node’s IO filter is unavailable. Failback will not start.

Success Scenarios

The following scenarios illustrate cases where the failback operation is rectified and operation can continue.

Maintenance Mode

• In a multi-node cluster, all hosts are healthy but one host is in maintenance mode. Failback will be able to continue.

Faulty Host Corrected

• In a multi-node cluster, one host is faulty and that faulty host is replaced with a healthy host. Failback will be able to continue.

Faulty Host Removed

• In a multi-node cluster, one host is faulty and that faulty host is removed from the cluster (removed from inventory). Failback will be able to continue.