# Confirm Node Fail Over for {{node.hostname}}

## Fail Over Options

Graceful Fail Over (default). Hard Fail Over - If you use hard failover option on a functioning node it may result in data loss. This is because failover will immediately remove the node from the cluster and any data that has not yet been replicated to other nodes may be permanently lost if it had not been persisted to disk.
Attention – Graceful fail over option is not available either because node is unreachable or replica vbucket cannot be activated gracefully.
Attention – A significant amount of data stored on this node does not yet have replica (backup) copies! Failing over the node now will irrecoverably lose that data when the incomplete replica is activated and this node is removed from the cluster. It is recommended to select "Remove Server" and rebalance to safely remove the node without any data loss. Please confirm Failover.
Warning – Failing over the node will remove it from the cluster and activate a replica. Operations currently in flight and not yet replicated, will be lost. Rebalancing will be required to add the node back into the cluster. Consider using "Remove from Cluster" and rebalancing instead of Failover, to avoid any loss of data. Please confirm Failover.
Attention – There are not replica (backup) copies of all data on this node! Failing over the node now will irrecoverably lose that data when the incomplete replica is activated and this node is removed from the cluster. If the node might come back online, it is recommended to wait. Check this box if you want to failover the node, despite the resulting data loss Please confirm Failover.
Warning – Failing over the node will remove it from the cluster and activate a replica. Operations not replicated before the node became unresponsive, will be lost. Rebalancing will be required to add the node back into the cluster. Please confirm Failover.
Cancel