| PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.1 (Solaris(TM) Operating System) |
|
Contents
|
| Chapter 6 Backing Up and Restoring | > 6.6 Backing Up and Restoring through an External Server | > 6.6.3 Backing Up and Restoring Using Snapshots from a Proxy Volume |
3) Parting the proxy volume
Part the proxy volume from the master volume. The following procedure must be performed on Node1 or Node2 in the primary domain.
The following example secures data consistency by stopping the services when the proxy volume is parted. Steps 3-2) and 3-4) are not required if software, such as a file system and a database system, that manages volume data provides functionality ensuring data consistency or repairing consistency for a parted volume is present. Alternatively, data consistency must be secured with the method specific to that software. For details, see "Ensuring Consistency of Snapshot Data."
3-1) Viewing the status of the proxy volume
Confirm that master volume Volume1 and proxy volume Volume2 are in sync with each other.
Confirm that proxy volume Volume2 is in the joined state. If Join is displayed in the PROXY field, the proxy volume is in the joined state.
|
# sdxinfo -V -c Class1 -o Volume2 -e long OBJ NAME TYPE CLASS GROUP DISK MASTER PROXY ... ------ ------- ------ ------- ------- ------ ------ ----- ... volume * mirror Class1 Group2 * * * ... volume Volume2 mirror Class1 Group2 * Volume1 Join ... volume * mirror Class1 Group2 * * * ... |
Confirm that data in all the slices of proxy volume Volume2 is valid (STOP).
|
# sdxinfo -S -c Class1 -o Volume2 OBJ CLASS GROUP DISK VOLUME STATUS ------ ------- ------- ------- ------- -------- slice Class1 Group2 Disk3 Volume2 STOP |
If data is not valid (STOP), repair the slice status referring to "Slice Status Abnormality."
3-2) Stopping the services
To secure consistency of data in proxy volume Volume2 parted, exit all applications using master volume Volume1 on Node1 and Node2.
When Volume1 is used as a file system, it should be unmounted.
3-3) Parting the proxy volume
Part proxy volume Volume2 from master volume Volume1.
|
# sdxproxy Part -c Class1 -p Volume2 -a pjrm=off |
Just Resynchronization Mode for Proxy
On backup server Node3, data may be written from Node3 into Volume2 when data in Volume2 is backed up to tape. GDS in the primary domain cannot recognize the write occurrence from Node3. Consequently, if the JRM mode for proxies of the parted volume is on, the portions updated from Node3 may not be involved in resynchronization copying performed when the proxy volume is rejoined or restored. If this happens, synchronization of master volume Volume1 and proxy volume Volume2 is no longer ensured. For this reason, the JRM mode of a parted proxy volume must be set to off in advance.
When synchronization copying between a master and a proxy is conducted by the disk unit's copy function, the disk unit's copy function recognizes such a written occurrence from Node3. In this case, only the difference between the master and the proxy is copied through synchronization copying with the disk unit's copy function when the proxy is rejoined regardless of the value specified to the JRM mode for proxies. However, synchronization copying on restore is conducted by the soft copy function. Therefore, the JRM mode of a parted proxy volume should be set to off in advance.
3-4) Resuming the services
When the file system was unmounted in step 3-2), mount it again.
Resume the application stopped in step 3-2).
3-5) Stopping the proxy volume
To prevent improper access to proxy volume Volume2, stop Volume2.
|
# sdxvolume -F -c Class1 -v Volume2 -e allnodes |
4) Viewing the configuration of the proxy volume
On Node1 or Node2 in the primary domain, view the configuration of proxy volume Volume2 that is the backup target.
|
# sdxinfo -c Class1 -o Volume2 |
5) Creating a shadow volume for backup
On backup server Node3, create a volume for backup (shadow volume).
|
# sdxshadowdisk -M -c Class2 -d c1t1d3=Disk3 |
Master volume data may be damaged if data is written into a shadow volume in incorrect configuration. Be sure to confirm that the shadow volume configuration is correct using the sdxinfo command.
The shadow volume must be created in the same configuration as the proxy volume created in step 2).
The shadow disk name must correspond to the disk name assigned in the primary domain. The disk names assigned in the primary domain can be viewed in the NAME field for disk information displayed with the sdxinfo command in step 4).
The class, the group, and the volume can be assigned any name.
The order of connecting shadow disks to a shadow group must correspond to the order of connecting disks to a group in the primary domain. The order of connecting disks in the primary domain can be viewed in the DISKS field for group information displayed with the sdxinfo command in step 4).
The stripe width of a shadow group must correspond to the stripe width in the primary domain. The stripe width specified in the primary domain can be viewed in the WIDTH field for group information displayed with the sdxinfo -e long command in step 4).
The shadow volume must be created in the size corresponding to the proxy volume size. The proxy volume size can be viewed in the BLOCKS field for volume information displayed with the sdxinfo command in step 4).
If there are multiple volumes, the corresponding shadow volumes must be created in the order of ascending values (first block numbers) in the 1STBLK field for volume information displayed with the sdxinfo command in step 4).
6) Backing up to tape
On backup server Node3, back up data in the shadow volume to tape. In the following examples, back up data in shadow volume Volume2 to a tape medium of tape device /dev/rmt/0.
For details on the backup method, see the manuals of file systems to be backed up and used commands.
In a GFS Shared File System
Back up through the method as described in step 6a).
6a) When backing up data held in a raw device with the dd(1M) command
|
# dd if=/dev/sfdsk/Class2/rdsk/Volume2 of=/dev/rmt/0 bs=32768 |
6b) When backing up a ufs file system with the tar(1) command
6b-1) Activate shadow volume Volume2 in the read and write access mode (rw).
|
# sdxshadowvolume -F -c Class2 -v Volume2 |
6b-2) Check and repair consistency of the ufs file system on shadow volume Volume2. If the file system was unmounted when the proxy volume was parted in step 3), this step can be skipped.
|
# fsck -F ufs /dev/sfdsk/Class2/rdsk/Volume2 |
6b-3) Mount the ufs file system on shadow volume Volume2 on /mnt1, a temporary mount point, in the read only mode.
|
# mkdir /mnt1 |
6b-4) Back up data held in the file system to tape.
|
# cd /mnt1 |
6b-5) Unmount the file system mounted in step 6b-3).
|
# cd / |
6c) When backing up a ufs file system with the ufsdump(1M) command
6c-1) Activate shadow volume Volume2 in the read and write access mode (rw).
|
# sdxshadowvolume -F -c Class2 -v Volume2 |
6c-2) Check and repair consistency of the ufs file system on shadow volume Volume2. If the file system was unmounted when the proxy volume was parted in step 3), this step can be skipped.
|
# fsck -F ufs -y /dev/sfdsk/Class2/rdsk/Volume2 |
6c-3) Back up data held in the file system to tape.
|
# ufsdump 0ucf /dev/rmt/0 /dev/sfdsk/Class2/rdsk/Volume2 |
6d) When backing up the sfxfs file system(GFS Local File System or SynfinityFile file system) with the tar(1) command
6d-1) Activate shadow volume Volume2 in the read and write access mode (rw).
|
# sdxshadowvolume -F -c Class2 -v Volume2 |
6d-2) Reconfigure the partition information of the sfxfs file system on shadow volume Volume2.
|
# sfxadm /dev/sfdsk/Class2/rdsk/Volume2 |
6d-3) Check and repair consistency of the sfxfs file system on shadow volume Volume2. If the file system was unmounted when the proxy volume was parted in step 3), this step can be skipped.
|
# fsck -F sfxfs -y /dev/sfdsk/Class2/rdsk/Volume2 |
6d-4) Mount the sfxfs file system on shadow volume Volume2 on /mnt1, a temporary mount point, in the read only mode.
|
# mkdir /mnt1 |
6d-5) Back up data held in the file system to tape.
|
# cd /mnt1 |
6d-6) Unmount the file system mounted in step 6d-4).
|
# cd / |
6e) When backing up the sfxfs file system (GFS Local File System or SynfinityFile file system) with the sfxdump(1M) command
6e-1) Activate shadow volume Volume2 in the read and write access mode (rw).
|
# sdxshadowvolume -F -c Class2 -v Volume2 |
6e-2) Reconfigure the partition information of the sfxfs file system on shadow volume Volume2.
|
# sfxadm /dev/sfdsk/Class2/rdsk/Volume2 |
6e-3) Check and repair consistency of the sfxfs file system on shadow volume Volume2. If the file system was unmounted when the proxy volume was parted in step 3), this step can be skipped.
|
# fsck -F sfxfs -y /dev/sfdsk/Class2/rdsk/Volume2 |
6e-4) Back up data held in the file system to tape.
|
# sfxdump 0ucf /dev/rmt/0 /dev/sfdsk/Class2/rdsk/Volume2 |
7) Removing the shadow volume
After the backup process is complete, remove the shadow volume to prevent improper access to it. The following settings are necessary on backup server Node3.
|
# sdxshadowvolume -F -c Class2 -v Volume2 |
8) Rejoining the proxy volume
Rejoin the proxy volume to the master volume. The following procedure must be performed on Node1 or Node2 in the primary domain.
8-1) Rejoining the proxy volume
Rejoin proxy volume Volume2 to master volume Volume1.
|
# sdxproxy Rejoin -c Class1 -p Volume2 |
After returning from the command, synchronization copying from Volume1 to Volume2 is executed.
8-2) Viewing the copy status
The status of synchronization copying can be viewed using the sdxinfo -S command. The slice of proxy volume Volume2 as the copy destination is in COPY status if copying is in progress and it will be in STOP status after the copy process ends normally.
|
# sdxinfo -S -c Class1 -o Volume2 OBJ CLASS GROUP DISK VOLUME STATUS ------ ------- ------- ------- ------- -------- slice Class1 Group2 Disk3 Volume2 STOP |
|
Contents
|