DOC-12112 no vbucket replica warning

modules/manage/pages/manage-nodes/failover-hard.adoc

@@ -36,35 +36,45 @@ The display is as follows:
 [#servers-screen-with-node-added-after-rebalance]
 image::manage-nodes/twoNodeClusterAfterRebalanceCompressedView.png[,800,align=middle]
 +
-. To see further details of the node to be failed over, which in this example will be `101.142.181.102`, left-click on the row for the node.
+. To see further details of the node to be failed over, which in this example will be `10.142.181.102`, left-click on the row for the node.
 The row expands vertically, as follows:
 +
 [#two-node-cluster-after-rebalance-expanded]
 image::manage-nodes/twoNodeClusterAfterRebalance.png[,800,align=middle]
 
-. To initiate failover, left-click on the *Failover* button, at the lower right of the row for `101.142.181.102`:
+. To initiate failover, left-click on the *Failover* button, at the lower right of the row for `10.142.181.102`:
 +
 [#failover-button]
 image::manage-nodes/failoverButton.png[,140,align=middle]
 +
 The *Confirm Failover Dialog* now appears:
 +
 [#confirm-failover-dialog]
-image::manage-nodes/confirmFailoverDialog.png[,400,align=middle]
+image::manage-nodes/confirmFailoverDialog.png[,500,align=middle]
 +
 Two radio buttons are provided, to allow selection of either *Graceful* or *Hard* failover. *Graceful* is selected by default.
 
-. Select _hard_ failover by selecting the *Hard* radio button:
+. Select  *Hard Failover*:
 +
 [#select-hard-failover]
-image::manage-nodes/confirmHardFailoverDialog.png[,400,align=middle]
+image::manage-nodes/confirmHardFailoverDialog.png[,500,align=middle]
 +
-Note the warning message that appears when hard failover is selected: in particular, this points out that hard failover may interrupt ongoing writes and replications, and that therefore it may be better to xref:manage:manage-nodes/remove-node-and-rebalance.adoc[Remove a Node and Rebalance], than use hard failover on a still-available Data Service node.
+Read the warning message that appears. 
+It explains that a hard failover may interrupt ongoing writes and replications.
+Therefore, you may want to xref:manage:manage-nodes/remove-node-and-rebalance.adoc[remove the node and rebalance] instead of performing a hard failover on a still-available Data Service node.
 +
-To continue with hard failover, confirm your choice by left-clicking on the *Failover Node* button.
+If the node contains vBuckets that do not have replicas on other nodes, Couchbase Server shows you an additional warning about data loss:
 +
-Hard failover now occurs.
-On conclusion, the *Servers* screen appears as follows:
+image::manage-nodes/hardFailoverWithDataLoss.png[,500,align=middle]
++
+In this case, you must select  *Confirm failover* to continue the hard failover.
++
+WARNING: Performing a hard failover on a node containing vBuckets that have no replicas on other nodes results in data loss. 
+
+. Confirm the hard failover by clicking btn:[Failover Node].
++
+Couchbase Server performs the hard failover on the node.
+When it finishes, the *Servers* screen appears as follows:
 +
 [#cluster-after-hard-failover]
 image::manage-nodes/twoNodeClusterAfterHardFailover.png[,800,align=middle]