| 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.4 Backing Up and Restoring by the Disk Unit's Copy Function |
3) Disconnecting a disk of the application volume
In the primary domain, among disks registered with class Class1 to which application volume Volume1 belongs, disconnect a disk (Disk2) other than the backup target disk Disk1 from Class1. Execute the following command on node Node1 or Node2 in the primary domain.
|
# sdxswap -O -c Class1 -d Disk2 |
4) Splitting the BCV
Split BCV device emcpower3 from standard device emcpower1. 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 a BCV is split. Steps 4-3) and 4-5) are not required if your software, such as a file system and a database system, that manages volume data provides functionality ensuring data consistency or repairing consistency for a split BCV. Alternatively, data consistency must be secured with the method specific to that software. For details, see "Ensuring Consistency of Snapshot Data."
4-1) Viewing the status of the application volume
Check the slice on standard device emcpower1 (Disk1) that is the copy source of BCV device emcpower3 among the slices of application volume Volume1 for the data validity (ACTIVE or STOP). Additionally, check that the slice of Disk2 disconnected in step 3) is in SWAP status.
|
# sdxinfo -S -c Class1 -o Volume1 OBJ CLASS GROUP DISK VOLUME STATUS ------ ------- ------- ------- ------- -------- slice Class1 Group1 Disk1 Volume1 ACTIVE slice Class1 Group1 Disk2 Volume1 NOUSE |
If the data is invalid (not ACTIVE or STOP), repair the slice status referring to "Slice Status Abnormality."
4-2) Viewing the condition of the BCV pair
Confirm that standard device STD001 (emcpower1) and BCV device BCV001 (emcpower3) are in sync with each other (synchronized).
|
# symmir -g DevGroup query Device Group (DG) Name: DevGroup DG's Type : REGULAR DG's Symmetrix ID : 000285502123 Standard Device BCV Device status
------------------------ ------------------------------------ --------------
Inv. Inv.
Logcal Sym Tracks Logical Sym Tracks STD <=> BCV ------------------------ ------------------------------------- ------------- STD001 005 0 BCV001 073 * 61754 Synchronized |
4-3) Stopping the services
To secure consistency of data in the split BCV device, exit all applications using application volume Volume1 on Node1 and Node2.
When Volume1 is used as a file system, it should be unmounted.
4-4) Splitting the BCV pair (disconnect)
Split the BCV pair (standard device STD001 and BCV device BCV001).
|
# symmir -g DevGroup split |
4-5) Resuming the services
When the file system was unmounted in step 4-3), mount it again.
Resume the application stopped in step 4-3).
5) Reconnecting the disk of the application volume
Reconnect disk Disk2 disconnected in step 3) from class Class1 to which application volume Volume1 belongs to Class1.
|
# sdxswap -I -c Class1 -d Disk2 -e nowaitsync |
After returning from the command, synchronization copying from the slice on Disk1 of volume Volume1 to the slice on Disk2 is executed.
6) Viewing the configuration of the application volume
On Node1 or Node2 in the primary domain, view the configuration of services volume Volume1 that is the backup target.
|
# sdxinfo -c Class1 OBJ NAME TYPE SCOPE SPARE ------ ------- -------- ----------- ----- class Class1 shared Node1:Node2 0 OBJ NAME TYPE CLASS GROUP DEVNAM DEVBLKS DEVCONNECT STATUS ------ ------- ------ ------- ------- ------- -------- ---------------- ------- disk Disk1 mirror Class1 Group1 emcpower1 8380800 Node1:Node2 ENABLE disk Disk2 mirror Class1 Group1 emcpower2 8380800 Node1:Node2 ENABLE OBJ NAME CLASS DISKS BLKS FREEBLKS SPARE ------ ------- ------- ------------------- -------- -------- ----- group Group1 Class1 Disk1:Disk2 8290304 7176192 0 OBJ NAME CLASS GROUP SKIP JRM 1STBLK LASTBLK BLOCKS STATUS ------ ------- ------- ------- ---- --- -------- -------- -------- -------- volume * Class1 Group1 * * 0 65535 65536 PRIVATE volume Volume1 Class1 Group1 off on 65536 1114111 1048576 ACTIVE volume * Class1 Group1 * * 1114112 8290303 7176192 FREE OBJ CLASS GROUP DISK VOLUME STATUS ------ ------- ------- ------- ------- -------- slice Class1 Group1 Disk1 Volume1 ACTIVE slice Class1 Group1 Disk2 Volume1 ACTIVE |
7) Creating a shadow volume for backup
On backup server Node3, create a volume for backup (shadow volume) on BCV device emcpower3. The following settings are necessary on backup server Node3.
Application 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 in step 7-4).
7-1) Registering a shadow disk
Register disk (BCV device) emcpower3 with shadow class Class2, and name it Disk1.
|
# sdxshadowdisk -M -c Class2 -d emcpower3=Disk1 |
The disk name must correspond to the disk name assigned in step 1-1) to standard device emcpower1 that is the copy source of BCV device emcpower3. The disk names assigned in 1-1) can be viewed in the NAME field for disk information displayed with the sdxinfo command in step 6).
The class can be assigned any name. However, if Node3 resides in the same domain as Node1 and Node2, it must be assigned a name different from the name of a class created in step 1-1).
7-2) Creating a shadow group
Connect shadow disk Disk1 to mirror type shadow group Group1.
|
# sdxshadowdisk -C -c Class2 -g Group1 -d Disk1 |
7-3) Creating a shadow volume
Create a shadow volume Volume1 to shadow group Group1.
|
# sdxshadowvolume -M -c Class2 -g Group1 -v Volume1 -s 1048576 |
The volume must be created in the size corresponding to the volume size in step 1-3). The size of a volume created in step 1-3) can be viewed in the BLOCKS field for volume information displayed with the sdxinfo command in step 6).
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 6).
The volume can be assigned any name.
7-4) 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 OBJ NAME TYPE SCOPE SPARE ------ ------- -------- ----------- ----- class Class2 local Node3 0 OBJ NAME TYPE CLASS GROUP DEVNAM DEVBLKS DEVCONNECT STATUS ------ ------- ------ ------- ------- ------- -------- ---------------- ------- disk Disk1 mirror Class2 Group1 emcpower3 8380800 Node3 ENABLE OBJ NAME CLASS DISKS BLKS FREEBLKS SPARE ------ ------- ------- ------------------- -------- -------- ----- group Group1 Class2 Disk1 8290304 7176192 0 OBJ NAME CLASS GROUP SKIP JRM 1STBLK LASTBLK BLOCKS STATUS ------ ------- ------- ------- ---- --- -------- -------- -------- -------- volume * Class2 Group1 * * 0 65535 65536 PRIVATE volume Volume1 Class2 Group1 off off 65536 1114111 1048576 ACTIVE volume * Class2 Group1 * * 1114112 8290303 7176192 FREE OBJ CLASS GROUP DISK VOLUME STATUS ------ ------- ------- ------- ------- -------- slice Class2 Group1 Disk1 Volume1 ACTIVE |
8) 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 Volume1 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 8a).
8a) 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 |
8b) When backing up a ufs file system with the tar(1) command
8b-1) Activate shadow volume Volume1 in the read and write access mode (rw).
|
# sdxshadowvolume -F -c Class2 -v Volume1 |
8b-2) Check and repair consistency of the ufs file system on shadow volume Volume1. If the file system was unmounted when the BCV was split in step 4), this step can be skipped.
|
# fsck -F ufs -y /dev/sfdsk/Class2/rdsk/Volume1 |
8b-3) Mount the ufs file system on shadow volume Volume1 on /mnt1, a temporary mount point, in the read only mode.
|
# mkdir /mnt1 |
8b-4) Back up data held in the file system to tape.
|
# cd /mnt1 |
8b-5) Unmount the file system mounted in step 8b-3).
|
# cd / |
8c) When backing up a ufs file system with the ufsdump(1M) command
8c-1) Activate shadow volume Volume1 in the read and write access mode (rw).
|
# sdxshadowvolume -F -c Class2 -v Volume1 |
8c-2) Check and repair consistency of the ufs file system on shadow volume Volume1. If the file system was unmounted when the BCV was split in step 3), this step can be skipped.
|
# fsck -F ufs -y /dev/sfdsk/Class2/rdsk/Volume1 |
8c-3) Back up data held in the file system to tape.
|
# ufsdump 0ucf /dev/rmt/0 /dev/sfdsk/Class2/rdsk/Volume1 |
8d) When backing up the sfxfs file system(GFS Local File System) with the tar(1) command
8d-1) Activate shadow volume Volume1 in the read and write access mode (rw).
|
# sdxshadowvolume -F -c Class2 -v Volume1 |
8d-2) Reconfigure the partition information of the sfxfs file system on shadow volume Volume1.
|
# sfxadm /dev/sfdsk/Class2/rdsk/Volume1 |
8d-3) Check and repair consistency of the sfxfs file system on shadow volume Volume1. If the file system was unmounted when the BCV was split in step 3), this step can be skipped.
|
# fsck -F sfxfs -y /dev/sfdsk/Class2/rdsk/Volume1 |
8d-4) Mount the sfxfs file system on shadow volume Volume1 on /mnt1, a temporary mount point, in the read only mode.
|
# mkdir /mnt1 |
8d-5) Back up data held in the file system to tape.
|
# cd /mnt1 |
8d-6) Unmount the file system mounted in step 6d-4).
|
# cd / |
8e) When backing up the sfxfs file system(GFS Local File System) with the sfxdump(1M) command
8e-1) Activate shadow volume Volume1 in the read and write access mode (rw).
|
# sdxshadowvolume -F -c Class2 -v Volume1 |
8e-2) Reconfigure the partition information of the sfxfs file system on shadow volume Volume1.
|
# sfxadm /dev/sfdsk/Class2/rdsk/Volume1 |
8e-3) Check and repair consistency of the sfxfs file system on shadow volume Volume1. If the file system was unmounted when the BCV was split in step 3), this step can be skipped.
|
# fsck -F sfxfs -y /dev/sfdsk/Class2/rdsk/Volume1 |
8e-4) Back up data held in the file system to tape.
|
# sfxdump 0ucf /dev/rmt/0 /dev/sfdsk/Class2/rdsk/Volume1 |
9) Removing the shadow volume
After the backup process is complete, remove the shadow volume to prevent improper access to it. The following procedure must be performed on backup server Node3.
9-1) Stopping the shadow volume
Stop shadow volume Volume1.
|
# sdxshadowvolume -F -c Class2 -v Volume1 |
9-2) Removing the shadow volume
Remove shadow volume Volume1.
|
# sdxshadowvolume -R -c Class2 -v Volume1 |
9-3) Removing the shadow group
Remove shadow group Group1.
|
# sdxshadowgroup -R -c Class2 -g Group1 |
9-4) Removing the shadow disk
Remove shadow disk Disk1.
|
# sdxshadowdisk -R -c Class2 -d Disk1 |
10) Resynchronizing the BCV
Resynchronize standard device STD001 and BCV device BCV001 for the following backup. Execute the following command on Node1 or Node2 in the primary domain.
|
# symmir -g DevGroup establish STD001 bcv ld BCV001 |
To back up again, follow the procedure from step 4).
|
Contents
|