| PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.1 (Solaris(TM) Operating System) |
|
Contents
|
| Chapter 6 Backing Up and Restoring | > 6.5 Backing Up and Restoring through Disk Unit's Copy Functions |
3) Backing up the object configuration of the class
On Node1 or Node2 in the primary domain, back up the object configuration of Class1 to be backed up.
3-1) Saving configuration information
Save outputs of the sdxinfo command to a file. In this example, the path to a file is "/var/tmp/Class1.info."
|
# sdxinfo -c Class1 -e long > /var/tmp/Class1.info |
3-2) Creating a configuration file
Output the object configuration within Class1 to a file in configuration table format. In this example, the path to a file is "/var/tmp/Class1.conf."
|
# sdxconfig Backup -c Class1 -o /var/tmp/Class1.conf |
3-3) Backing up the configuration information and configuration file
Save the files created in steps 3-1) and 3-2) to tape and so on.
4) Detaching the backup disks (suspending synchronization)
In this example, stop services when detaching the backup disks in order to secure consistency of data. If installed software, such as file systems and database systems that manage volume data, provides functions for securing or repairing consistency of data on detached copy destination disks is present, skip steps 4-3) and 4-5). Alternatively, perform operations for securing consistency with software-specific methods. For details, see "Ensuring Consistency of Snapshot Data."
4-1) Viewing the application volume status
Confirm that data of slices comprising application volume Volume1 is in valid status (ACTIVE or STOP).
|
# sdxinfo -S -c Class1 -o Volume1 OBJ CLASS GROUP DISK VOLUME STATUS ------ ------- ------- ------- ------- -------- slice Class1 Group1 Disk1 Volume1 ACTIVE slice Class1 Group1 Disk2 Volume1 ACTIVE |
If it is not in valid status (ACTIVE or STOP), recover the slice status, referring to "Slice Status Abnormality."
4-2) Checking the statuses of the disk unit's copy functions
Confirm that the application disks and the backup disks are synchronized.
For the confirming methods, see the manuals of disk units for information regarding copy functions.
4-3) Stopping services
To secure consistency of data in the backup disks after they are detached from the application disks, stop applications using application volume Volume1 on Node1 and Node2.
When using Volume1 as a file system, unmount the file system.
4-4) Detaching the backup disks (suspending synchronization)
Detach backup disks c3t1d1 and c4t1d1 from application disks c1t1d1 and c2t1d1.
For the synchronization methods, see the manuals of disk units for information regarding copy functions.
4-5) Resuming the services
When the file system was unmounted in step 4-3), mount it again.
Resume the applications stopped in step 4-3).
5) Creating a backup volume
On backup server Node3, create a backup volume into backup disks c3t1d1 and c4t1d1. The following settings are necessary on backup server Node3.
5-1) Placing the configuration file
Place the configuration file "/var/tmp/Class1.conf" backed up in step 3) onto backup server Node3. In this example, the path to a destination file is "/var/tmp/Class1.conf."
5-2) Changing physical disks in the configuration file
Change the physical disk names of the application disks described in the configuration file "/var/tmp/Class1.conf" from c1t1d1 and c2t1d1 to c3t1d1 and c4t1t1, which are the physical disk names of the backup disks, respectively.
# sdxconfig Convert -e replace -c Class1 -p c1t1d1=c3t1d1,c2t1d1=c4t1d1 \ -i /var/tmp/Class1.conf -o /var/tmp/Class1.conf -e update |
Physical Disk Sizes
The former physical disks and the latter physical disks must be equivalent in size.
5-3) Editing a class name in the configuration file
Change the class name of the configuration table described in the configuration file "/var/tmp/Class1.conf" from Class1 to Class2 and save the changes to the configuration file "/var/tmp/Class2.conf." If Class1 already exists in a domain to which the backup server belongs, the class must be renamed.
|
# sdxconfig Convert -e rename -c Class1=Class2 -i /var/tmp/Class1.conf -o /var/tmp/Class2.conf |
5-4) Creating a backup volume
According to the configuration table in the configuration file "/var/tmp/Class2.conf" created in step 5-3), create the object configuration of class Class2.
|
# sdxconfig Restore -c Class2 -i /var/tmp/Class2.conf -e chkps,skipsync |
On backup server Node3, backup disks c3t1d1 and c4t1d1 are registered with local class Class2. Those disks are assigned Disk1 and Disk2 respectively and backup volume Volume1 is created on disks Disk1 and Disk2.
The backup disks to which write access was prevented were detached in step 4-4) and consistency between c3t1d1 and c4t1d1 has been ensured.
Therefore, synchronization copying can be skipped when creating mirror volume Volume1 by specifying the -e skipsync option for the sdxconfig Restore command.
6) Backing up to tape
On backup server Node3, back up data in backup volume Volume1 to a tape medium of tape unit /dev/rmt/0.
For details on the backup methods, see the manuals of backed up file systems and used commands.
GFS Shared File System
Back up data with the method shown in step 6a).
6a) When backing up data held in a raw device with the dd(1M) command
|
# dd if=/dev/sfdsk/Class2/rdsk/Volume1 of=/dev/rmt/0 bs=32768 |
6b) When backing up the ufs file system with the tar(1) command
6b-1) Check and repair consistency of the ufs file system on backup volume Volume1. If the file system was unmounted when the backup disks were detached in step 3), skip this step.
|
# fsck -F ufs -y /dev/sfdsk/Class2/rdsk/Volume1 |
6b-2) Mount the ufs file system on backup volume Volume1 on /mnt1, a temporary mount point, in the read only mode.
|
# mkdir /mnt1 |
6b-3) Back up data held in the file system to tape.
|
# cd /mnt1 |
6b-4) Unmount the file system mounted in step 6b-2).
|
# cd / |
6c) When backing up the ufs file system with the ufsdump(1M) command
6c-1) Check and repair consistency of the ufs file system on backup volume Volume1. If the file system was unmounted when the backup disks were detached in step 3), skip this step.
|
# fsck -F ufs -y /dev/sfdsk/Class2/rdsk/Volume1 |
6c-2) Back up data held in the file system to tape.
|
# ufsdump 0ucf /dev/rmt/0 /dev/sfdsk/Class2/rdsk/Volume1 |
6d) When backing up the sfxfs file system (GFS Local File System) with the tar(1) command
6d-1) Reconfigure the partition information of the sfxfs file system on backup volume Volume1.
|
# sfxadm /dev/sfdsk/Class2/rdsk/Volume1 |
6d-2) Check and repair consistency of the sfxfs file system on backup volume Volume1. If the file system was unmounted when the backup disks were detached in step 3), skip this step.
|
# fsck -F sfxfs -y /dev/sfdsk/Class2/rdsk/Volume1 |
6d-3) Mount the sfxfs file system on backup volume Volume1 on /mnt1, a temporary mount point, in the read only mode.
|
# mkdir /mnt1 |
6d-4) Back up data held in the file system to tape.
|
# cd /mnt1 |
6d-5) Unmount the file system mounted in step 6d-3).
|
# cd / |
6e) When backing up the sfxfs file system (GFS Local File System) with the sfxdump(1M) command
6e-1) Reconfigure the partition information of the sfxfs file system on backup volume Volume1.
|
# sfxadm /dev/sfdsk/Class2/rdsk/Volume1 |
6e-2) Check and repair consistency of the sfxfs file system on backup volume Volume1. If the file system was unmounted when the backup disks were detached in step 3), skip this step.
|
# fsck -F sfxfs -y /dev/sfdsk/Class2/rdsk/Volume1 |
6e-3) Back up data held in the file system to tape.
|
# sfxdump 0ucf /dev/rmt/0 /dev/sfdsk/Class2/rdsk/Volume1 |
7) Removing the backup volumes
After the backup process is complete, delete the object configuration of Class2 created for backup. On backup server Node3, perform the following procedures.
7-1) Stopping the backup volume
Stop all the volumes in Class2.
|
# sdxvolume -F -c Class2 |
7-2) Deleting the object configuration of Class2
Delete the object configuration of Class2.
|
# sdxconfig Remove -c Class2 |
8) Resynchronizing the backup disks
Preparatory to the next backup, resynchronize application disks c1t1d1 and c2t1d1, as copy sources, respectively with backup disks c3t1d1 and c4t1d1, as copy destinations, with copy functions of the disk units.
For the resynchronization methods, see the manuals of disk units for information regarding copy functions.
|
Contents
|