Table of Contents
Advertisement
72
7.1.2. Example
In this example, the name of the cluster is
/dev/pool/alpha_cca
create a CCS archive on the CCA device
ccs_tool create /root/alpha/ /dev/pool/alpha_cca
7.1.3. Comments
The
(override) option can be specified after the command name (
•
-O
forcibly write over the current CCA device contents without a prompt.
Warning
Make sure that you specify the right device if you use the override option. Otherwise, data may be
lost.
Depending on the size of the device, it may take several seconds to create a CCA device for the first
•
time due to initialization of the device.
The
command uses the Linux raw-device interface to update and read a CCA device
•
ccs_tool
directly, bypassing operating system caches. Caching effects could otherwise create inconsistent
views of the CCA device between cluster nodes.
7.2. Starting CCS in the Cluster
Once a CCS archive has been created on a CCA device (refer to Section 7.1 Creating a CCS Archive
for details, if necessary), the CCS daemon (
nodes must be able to see the CCA device before the daemon is started.
The CCS daemon provides an interface to configuration data that is independent of the specific loca-
tion where the data is stored.
7.2.1. Usage
ccsd -d CCADevice
CCADevice
Specifies the name of the CCA device.
7.2.2. Example
In this example, the CCS daemon is started on a cluster node. This command should be run on all
cluster nodes:
ccsd -d /dev/pool/alpha_cca
. The CCS configuration files in directory
/dev/pool/alpha_cca
ccsd
Chapter 7. Using the Cluster Configuration System
, and the name of the pool is
alpha
.
) should be started on all cluster nodes. All cluster
are used to
/root/alpha/
ccs_tool -O create
) to
Advertisement
Table of Contents
