You can backup your cluster configuration data using the
command-line interface (CLI).
Before you backup your cluster configuration data, the
following prerequisites must be met:
- No independent operations that change the cluster configuration
can be running while the backup command is running.
- No object name can begin with an underscore.
- All objects should have non-default names, that is, names that
are not assigned by the SAN Volume Controller.
Note: - The default object names for controllers, I/O groups and managed
disks (MDisks) do not restore correctly if the ID of the object is
different than what is recorded in the current cluster configuration
data file.
- All other objects with default names are renamed during the restore
process. The new names appear in the format name_r. Where name is
the name of the object in your cluster.
The backup feature of the svcconfig CLI command
is designed to back up information about your cluster configuration,
such as virtual disks (VDisks), local Metro Mirror information, local
Global Mirror information, managed disk (MDisk) groups, and nodes.
All other data that you have written to the VDisks is not backed
up. Any application that uses the VDisks on the cluster as storage,
must back up its application data using the appropriate backup methods.
You
must regularly back up your cluster configuration data and your application
data to avoid data loss. If a cluster is lost after a severe failure
occurs, both cluster configuration and application data is lost. You
must reinstate the cluster to the exact state it was in prior to the
failure and then recover the application data.
Perform the following
steps to backup your cluster configuration data:
- Back up all of the application data that you have stored
on your VDisks using your preferred backup method.
- Open a command prompt.
- Issue the following command to log onto the cluster:
ssh -l admin your_cluster_name -p 22
Where your_cluster_name is
the name of the cluster for which you want to backup cluster configuration
data.
- Issue the following CLI command to remove all of the existing
cluster configuration backup and restore files that are located on
your configuration node in the /tmp directory.
svcconfig clear -all
- Issue the following CLI command to backup your cluster
configuration:
svcconfig backup
The following output is an example of the messages that are
displayed during the backup process:CMMVC6112W io_grp io_grp1 has a default name
CMMVC6112W io_grp io_grp2 has a default name
CMMVC6112W mdisk mdisk14 ...
CMMVC6112W node node1 ...
CMMVC6112W node node2 ...
....................................................
The svcconfig backup CLI
command creates three files that provide information about the backup
process and cluster configuration. These files are created in the
/tmp directory of the configuration node.
The following table
describes the three files that are created by the backup process:
| File name |
Description |
|---|
| svc.config.backup.xml |
This file contains your cluster configuration
data. |
| svc.config.backup.sh |
This file contains the names of the commands
that were issued to create the backup of the cluster. |
| svc.config.backup.log |
This file contains details about the backup,
including any error information that might have been reported. |
- Issue the following command to exit the cluster:
exit
- Issue the following command
to copy the backup files to a location that is not in your cluster:
scp -P 22 admin@your_cluster:/tmp/svc.config.backup.*
/offclusterstorage/
Where your_cluster is
the name of your cluster and offclusterstorage is the location
where you want to store the backup files.
You must copy these
files to a location outside of your cluster because the /tmp directory
on this node becomes inaccessible if the configuration node changes.
The configuration node might change in response to an error recovery
action or to a user maintenance activity.
Tip: To maintain
controlled access to your cluster configuration data, copy the backup
files to a location that is password protected.
- Ensure that the copies of the backup files are stored in
the location that you specified in step 7.
You can rename the backup files to include the configuration
node name either at the start or end of the file names so you can
easily identify these files when you are ready to restore your configuration.
Issue
the following command to rename the backup files that are stored on
a Linux® or AIX® host:
mv /offclusterstorage/svc.config.backup.xml
/offclusterstorage/svc.config.backup.xml_myconfignode
Where offclusterstorage is
the name of the directory where the backup files are stored and myconfignode is
the name of your configuration node.
To rename the backup files
that are stored on a Windows® host,
right-click on the name of the file and select Rename.