Backing Up a Cluster

Before you back up your cluster, find the names of the file systems you want to back up, calculate how many tapes you need to contain a full backup, and back up the ZFS root file system.

Table 12-1 Task Map: Backing Up Cluster Files

How to Perform Online Backups for Mirrors (Solaris Volume Manager)

A mirrored Solaris Volume Manager volume can be backed up without unmounting it or taking the entire mirror offline. One of the submirrors must be taken offline temporarily, thus losing mirroring, but it can be placed online and resynchronized as soon as the backup is complete, without halting the system or denying user access to the data. Using mirrors to perform online backups creates a backup that is a “snapshot” of an active file system.

A problem might occur if a program writes data onto the volume immediately before the lockfs command is run. To prevent this problem, temporarily stop all the services running on this node. Also, ensure the cluster is running without errors before performing the backup procedure.

The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.

1. Assume an equivalent role on the cluster node that you are backing up.
2. Use the metaset command to determine which node has the ownership on the backed-up volume.

   # metaset -s setname

   -s setname

   Specifies the disk set name.

   For more information, see the metaset(1M) man page.

3. Use the lockfs command with the -w option to lock the file system from writes.

   # lockfs -w mountpoint

   See the lockfs(1M) man page for more information.

4. Use the metastat command to determine the names of the submirrors.

   # metastat -s setname -p

   -p

   Displays the status in a format similar to the md.tab file.

   See the metastat(1M) man page for more information.

5. Use the metadetach command to take one submirror offline from the mirror.

   # metadetach -s setname mirror submirror

   See the metadetach(1M) man page for more information.

   ---

   Note - Reads continue to be made from the other submirrors. However, the offline submirror is unsynchronized as soon as the first write is made to the mirror. This inconsistency is corrected when the offline submirror is brought back online. You do not need to run fsck.

   ---

6. Unlock the file systems and allow writes to continue, using the lockfs command with the -u option.

   # lockfs -u mountpoint 

7. Perform a file system check.

   # fsck /dev/md/diskset/rdsk/submirror

8. Back up the offline submirror to tape or another medium.

   ---

   Note - Use the raw device (/rdsk) name for the submirror, rather than the block device (/dsk) name.

   ---

9. Use the metattach command to place the metadevice or volume back online.

   # metattach -s setname mirror submirror

   When the metadevice or volume is placed online, it is automatically resynchronized with the mirror. See the metattach(1M) man page for more information.

10. Use the metastat command to verify that the submirror is resynchronizing.

    # metastat -s setname mirror

    See Oracle Solaris 11.1 Administration: ZFS File Systems for more information.

How to Back Up the Cluster Configuration

To ensure that your cluster configuration is archived and to facilitate easy recovery of the your cluster configuration, periodically back up your cluster configuration. Oracle Solaris Cluster provides the ability to export your cluster configuration to an eXtensible Markup Language (XML) file.

1. Log on to any node in the cluster, and assume a role that provides solaris.cluster.read RBAC authorization.
2. Export the cluster configuration information to a file.

   # /usr/cluster/bin/cluster export -o configfile

   configfile

   The name of the XML configuration file that the cluster command is exporting the cluster configuration information to. For information about the XML configuration file, see the clconfiguration(5CL) man page.

3. Verify that the cluster configuration information was successfully exported to the XML file.

   # vi configfile