The requested article is not available. Either it doesn't apply to this version of the product or the relevant information is organized differently in this version of the docs. You can search, browse, or go back to the other version.
Synchronize a node with the cluster
-
PDF of this doc site
-
Cluster administration
-
Volume administration
-
Logical storage management with the CLI
-
-
NAS storage management
-
Configure NFS with the CLI
-
Manage NFS with the CLI
-
Manage SMB with the CLI
-
Manage file access using SMB
-
-
-
Security and data encryption
-
Data protection and disaster recovery
-

Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
If cluster-wide quorum exists, but one or more nodes are out of sync with the cluster, then you must synchronize the node to restore the replicated database (RDB) on the node and bring it into quorum.
Step
-
From a healthy node, use the
system configuration recovery cluster sync
command at the advanced privilege level to synchronize the node that is out of sync with the cluster configuration.This example synchronizes a node (node2) with the rest of the cluster:
cluster1::*> system configuration recovery cluster sync -node node2 Warning: This command will synchronize node "node2" with the cluster configuration, potentially overwriting critical cluster configuration files on the node. This feature should only be used to recover from a disaster. Do not perform any other recovery operations while this operation is in progress. This command will cause all the cluster applications on node "node2" to restart, interrupting administrative CLI and Web interface on that node. Do you want to continue? {y|n}: y All cluster applications on node "node2" will be restarted. Verify that the cluster applications go online.
Result
The RDB is replicated to the node, and the node becomes eligible to participate in the cluster.