Note
Automatic Resource Registration
If the backup server resides in a cluster domain (called a backup domain) that is different from the primary domain, those disks which are registered as resources in the primary domain or are to be registered with classes restored in the backup domain may not be involved in the resource registration in the backup domain. In the backup domain, those relevant disks must be described in the Excluded Device List prior to executing the automatic resource registration. For details on the automatic resource registration, see "PRIMECLUSTER Installation and Administration Guide."
1) Creating an application volume
Create an application mirror volume onto application disks c1t1d1 and c2t1d1. The following settings are necessary on Node1 or Node2 in the primary domain.
1-1) Registering disks
Register disks c1t1d1 and c2t1d1 with shared class Class1 that is shared on Node1 and Node2, and name them Disk1 and Disk2 respectively.
# sdxdisk -M -c Class1 -a type=shared,scope=Node1:Node2 -d c1t1d1=Disk1,c2t1d1=Disk2 |
1-2) Creating a mirror group
Connect disks Disk1 and Disk2 to mirror group Group1.
# sdxdisk -C -c Class1 -g Group1 -d Disk1,Disk2 |
1-3) Creating a mirror volume
Create mirror volume Volume1 into mirror group Group1.
# sdxvolume -M -c Class1 -g Group1 -v Volume1 -s 1048576 |
2) Synchronizing backup disks
Synchronize application disks c1t1d1 and c2t1d1, as copy sources, respectively with disks c3t1d1 and c4t1d1, as copy destinations, with copy functions of the disk units.
See
For the synchronization methods, see the manuals of disk units for information regarding copy functions.
Note
Backup disks must be equivalent in size application disks to be backed up.
