A single-node cluster is a special implementation of a cluster running on a stand-alone node. You can deploy a single-node cluster if your workload only requires a single node, but does not need nondisruptive operations.
For example, you could deploy a single-node cluster to provide data protection for a remote office. In this scenario, the single-node cluster would use SnapMirror and SnapVault to replicate the site's data to the primary data center.
In a single-node cluster, the HA mode is set to non_HA, which enables the node to use all of the nonvolatile memory (NVRAM) on the NVRAM card. In addition, single-node clusters do not use a cluster network, and you can use the cluster ports as data ports that can host data LIFs.
Single-node clusters are typically configured when the cluster is set up. However, you can also remove nodes from an existing cluster to create a single-node cluster.
The following features and operations are not supported for single-node clusters:
Single-node clusters operate in a stand-alone HA mode. If the node goes offline, clients cannot access data stored in the cluster.
For example, you cannot move volumes or perform most copy operations.
Infinite Volumes must contain aggregates from at least two nodes.
By default, the configuration backup schedule creates backups of the cluster configuration and stores them on different nodes throughout the cluster. However, if the cluster consists of a single node and you experience a disaster in which the node becomes inaccessible, you cannot recover the cluster unless the cluster configuration backup file is stored at a remote URL.