Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster System Administration Guide Oracle Solaris Cluster 4.0 |
1. Introduction to Administering Oracle Solaris Cluster
2. Oracle Solaris Cluster and RBAC
3. Shutting Down and Booting a Cluster
4. Data Replication Approaches
5. Administering Global Devices, Disk-Path Monitoring, and Cluster File Systems
7. Administering Cluster Interconnects and Public Networks
10. Configuring Control of CPU Usage
12. Backing Up and Restoring a Cluster
How to Restore the ZFS Root (/) File System (Solaris Volume Manager)
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
|
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.
# metaset -s setname
Specifies the disk set name.
For more information, see the metaset(1M) man page.
# lockfs -w mountpoint
See the lockfs(1M) man page for more information.
# metastat -s setname -p
Displays the status in a format similar to the md.tab file.
See the metastat(1M) man page for more information.
# 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.
# lockfs -u mountpoint
# fsck /dev/md/diskset/rdsk/submirror
Note - Use the raw device (/rdsk) name for the submirror, rather than the block device (/dsk) name.
# 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.
# metastat -s setname mirror
See Oracle Solaris Administration: ZFS File Systems for more information.
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.
# /usr/cluster/bin/cluster export -o 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.
# vi configfile