Troubleshooting VCS configuration backup and restore
Prev	Troubleshooting and recovery for VCS	Next

---

Troubleshooting VCS configuration backup and restore

This section cites the problem you may encounter when using the hasnap command to backup and restore VCS configuration files.

Error connecting to remote nodes in the cluster.

The hasnap command is a distributed command in the sense that it tries to backup and restore files from all cluster nodes in a single session. It needs to establish connection with all cluster nodes from the node where the command is executed. The connection may fail for one of the following reasons:

• The hasnap command retrieves the list of cluster nodes from the llthosts configuration file. However, the node names in this file may not always be DNS resolvable, in which case the command cannot establish connection with the remote nodes.

  Recommended Action:. For each node in the cluster, map the VCS node names to the actual DNS-resolvable names using the hasnap configuration file /opt/VRTSvcs/cutil/conf/vcsmappings.properties.

• The hasnap command uses the VCS Command Server Daemon running on the remote nodes to establish connection. The connection fails if the Daemon is not running on the remote node.

  Recommended Action: Verify the VCS Command Server Daemon is running on all cluster nodes. Start it by running the following command:

# /opt/VRTSvcs/bin/CmdServer

• The remote node might be currently down or unreachable.

  Recommended Action: Run the hasnap command again after the bringing the remote node online.