Veritas Storage Foundation 5.1 SP1 Cluster File System Administrator"s Guide (5900-1738, April 2011)

■ generate_snapshot.sh : Retrieves the SCSI ID’s of the coordinator disks and/or
UUID ID's of the CP servers
For information about the UUID (Universally Unique Identifier), see the Veritas
Cluster Server Administrator's Guide.
■ join_local_node.sh: Registers the keys with the coordinator disks or CP servers
■ race_for_coordination_point.sh: Races to determine a winner after cluster
reconfiguration
■ unjoin_local_node.sh: Removes the keys that are registered in
join_local_node.sh
■ fence_data_disks.sh: Fences the data disks from access by the losing nodes.
■ local_info.sh: Lists local node’s configuration parameters and coordination
points, which are used by the vxfen driver.
About the CP server database
CP server requires a database for storing the registration keys of the SFCFS cluster
nodes. CP server uses a SQLite database for its operations. By default, the database
is located at /etc/VRTScps/db.
For a single node VCS cluster hosting a CP server, the database can be placed on
a local file system. For an SFHA cluster hosting a CP server, the database must be
placed on a shared file system. The file system must be shared among all nodes
that are part of the SFHA cluster.
In an SFHA cluster hosting the CP server, the shared database is protected by
setting up SCSI-3 PR based I/O fencing. SCSI-3 PR based I/O fencing protects
against split-brain scenarios.
Warning: The CP server database must not be edited directly and should only be
accessed using cpsadm(1M). Manipulating the database manually may lead to
undesirable results including system panics.
About the CP server user types and privileges
The CP server supports the following user types, each with a different access level
privilege:
■ CP server administrator (admin)
■ CP server operator
45Storage Foundation Cluster File System architecture
About I/O fencing