| 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 |
This sub-section shows an example that access can be gained from backup server Node3 to all of the disks constituting master volume Volume1.
When Using a Disk Unit's Copy Function
When access can be gained from backup server Node3 to all of the disks constituting master volume Volume1 and the disk unit's copy function is used to synchronize a master and a proxy, parting the proxy volume in step 15) is not required.
When access cannot be gained from the backup server to the disks constituting the master volume
While proxy volume Volume2 is parted, copy data from tape to the proxy volume, and then restore master volume data using the proxy volume.
13) Stopping the services
Exit all applications using master volume Volume1 on Node1 and Node2 in the primary domain.
When Volume1 is used as a file system, it should be unmounted.
14) Stopping the master volume
On Node1 and Node2 in the primary domain, stop master volume Volume1 to prevent improper access to it. Execute the following command on Node1 or Node2.
|
# sdxvolume -F -c Class1 -v Volume1 -e allnodes |
15) Parting the proxy volume
In the primary domain, part proxy volume Volume2 from master volume Volume1. Execute the following command on Node1 or Node2.
|
# sdxproxy Part -c Class1 -p Volume2 -a pjrm=off |
Just Resynchronization Mode for Proxy
After data held in master volume Volume1 is restored from tape on backup server Node3, proxy volume Volume2 is supposed to be rejoined to master volume Volume1. At this point the entire Volume1 data must be copied to Volume2. For this reason, the JRM mode of a parted proxy volume must to be set to off in advance.
When Using a Disk Unit's Copy Function
When the disk unit's copy function is used to synchronize a master and a proxy, this procedure (parting a proxy) is not required.
When access cannot be gained from the backup server to the disks constituting the master volume
After proxy volume Volume2 is parted, inactivate Volume2 on Node1 and Node2 to prevent Volume2 from being written in improperly.
16) Viewing the status and configuration of the master volume
On Node1 and Node2 in the primary domain, view the configuration and status of master volume Volume1 that is the restore target. Confirm that all of the slices constituting Volume1 are in STOP status. If the status of a slice is invalid, repair it referring to "Slice Status Abnormality."
|
# sdxinfo -S -c Class1 -o Volume1 OBJ CLASS GROUP DISK VOLUME STATUS ------ ------- ------- ------- ------- -------- slice Class1 Group1 Disk1 Volume1 STOP slice Class1 Group1 Disk2 Volume1 STOP |
When Using a Disk Unit's Copy Function
When the proxy volume was not parted in step 15) because the disk unit's copy function is used for synchronizing a master and a proxy, you must also confirm that all of the slices constituting proxy volume Volume2 are in STOP status.
When access cannot be gained from the backup server to the disks constituting the master volume
View the configuration and the status of proxy volume Volume2 that is the restore target.
17) Creating a shadow volume for restore
On backup server Node3, create a volume for restore (shadow volume).
17-1) Creating a shadow volume
|
# sdxshadowdisk -M -c Class2 -d c1t1d1=Disk1,c1t1d2=Disk2 |
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 master volume created in step 1).
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 16).
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 16).
The stripe width of a stripe type shadow group must correspond to the stripe width of a stripe group in the primary domain. The stripe width in the primary domain can be viewed in the WIDTH field for group information displayed with the sdxinfo -e long command in step 16).
A shadow volume must be created in the size corresponding to the master volume size. The master volume size can be viewed in the BLOCKS field for volume information displayed with the sdxinfo command in step 16).
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 16).
When access cannot be gained from the backup server to the disks constituting the master volume
Create a shadow volume for restore in a similar procedure that created a proxy volume in step 2).
17-2) Setting the access mode of the shadow volume
Activate shadow volume Volume1 in the read and write access mode (rw).
|
# sdxshadowvolume -F -c Class2 -v Volume1 |
17-3) Viewing the configuration of the shadow volume
Using the sdxinfo command, confirm that the group configuration and the volume configuration are correct based on group information in the DISKS field, volume information in the 1STBLK field and in the BLOCKS field and so on.
|
# sdxinfo -c Class2 |
18) Restoring from tape
On backup server Node3, restore shadow volume data from tape to which it was backed up in step 6). In the following examples, restore data held in shadow volume Volume1 from a tape medium of tape device /dev/rmt/0.
For details on the restore method, see the manuals of file systems to be restored and used commands.
In a GFS Shared File System
Restore through the method as described in step 18a).
18a) When restoring data held in a raw device with the dd(1M) command
|
# dd if=/dev/rmt/0 of=/dev/sfdsk/Class2/rdsk/Volume1 bs=32768 |
18b) When restoring a ufs file system with the tar(1) command
18b-1) Create a ufs file system to shadow volume Volume1.
|
# newfs /dev/sfdsk/Class2/rdsk/Volume1 |
18b-2) Mount the ufs file system on shadow volume Volume1 on /mnt1, a temporary mount point.
|
# mkdir /mnt1 |
18b-3) Restore data held in the file system from tape.
|
# cd /mnt1 |
18b-4) Unmount the file system mounted in step 18b-3).
|
# cd / |
18c) When restoring a ufs file system with the ufsrestore(1M) command
18c-1) Create a ufs file system to shadow volume Volume1.
|
# newfs /dev/sfdsk/Class2/rdsk/Volume1 |
18c-2) Mount the ufs file system on shadow volume Volume1 on /mnt1, a temporary mount point.
|
# mkdir /mnt1 |
18c-3) Restore data held in the file system from tape.
|
# cd /mnt1 |
18c-4) Delete the temporary file created by the ufsrestore(1M) command.
|
# rm /mnt1/restoresymtable |
18c-5) Unmount the file system mounted in step 18c-2).
|
# cd / |
18d) When restoring the sfxfs file system(GFS Local File System or SynfinityFile file system) with the tar(1) command
18d-1) Create the sfxfs file system to shadow volume Volume1.
|
# sfxnewfs /dev/sfdsk/Class2/rdsk/Volume1 |
18d-2) Mount the sfxfs file system on shadow volume Volume1 on /mnt1, a temporary mount point.
|
# mkdir /mnt1 |
18d-3) Restore data held in the file system from tape.
|
# cd /mnt1 |
18d-4) Unmount the file system mounted in step 18d-2).
|
# cd / |
18e) When restoring the sfxfs file system(GFS Local File System or SynfinityFile file system) the sfxrestore(1M) command
18e-1) Create the sfxfs file system to shadow volume Volume1.
|
# sfxnewfs /dev/sfdsk/Class2/rdsk/Volume1 |
18e-2) Mount the sfxfs file system on shadow volume Volume1 on /mnt1, a temporary mount point.
|
# mkdir /mnt1 |
18e-3) Restore data held in the file system from tape.
|
# cd /mnt1 |
18e-4) Delete the temporary file created by the sfxrestore(1M) command.
|
# rm /mnt1/restoresymtable |
18e-5) Unmount the file system mounted in step 18e-2).
|
# cd / |
19) Removing the shadow volume
After the restore 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 Volume1 |
20) Resuming the services
Resume services in the primary domain. The following procedure must be performed on the node that runs the services.
When access cannot be gained from the backup server to the disks constituting the master volume
Before the services are resumed, restore data from proxy volume Volume2 to master volume Volume1. For the procedure see "Restoring from a Proxy Volume."
20-1) Activating the master volume
Activate master volume Volume1.
|
# sdxvolume -N -c Class1 -v Volume1 |
20-2) Reconfiguring the partition information of the sfxfs file system
When master volume Volume1 is used as the sfxfs file system, reconfigure the partition information.
|
# sfxadm /dev/sfdsk/Class1/rdsk/Volume1 |
20-3) Resuming the services
When the file system on Volume1 was unmounted in step 13), mount it again.
Start the applications using Volume1.
|
Contents
|