/
Failback Operation Issues

Failback Operation Issues

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

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.

Related content

Cluster IO Filter Upgrade Error
Cluster IO Filter Upgrade Error
More like this
Planned Failover Issue
Planned Failover Issue
More like this
Check Progress of JetStream DR Upgrade
Check Progress of JetStream DR Upgrade
Read with this
Failover Task Cannot be Processed
Failover Task Cannot be Processed
More like this
Invalid Replication Log
Invalid Replication Log
Read with this
Background Data Backlog
Background Data Backlog
Read with this