PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment)

24.7.7 Setup of the backup relationship

It is necessary to perform the following steps to establish the backup relationship for both section EC employment and OPC employment. In the case of EC employment of each group, please perform "1) Setting a volume start lock" after "3) Setup of the backup relationship."

1. Setting a volume start lock

   Set a volume start lock in nodes that do not auto start the backup destination GDS volume.

   With the settings that were set during GDS volume creation, when the separation operation is performed during EC employment or the backup operation is performed during OPC implementation, the GDS volumes of the backup destination are started in all nodes that share those volumes.

   However, when a subsequent join is performed in EC employment or when the next backup is performed in OPC implementation, the backup destination volumes must be stopped in all nodes except the node in which that operation is being performed.

   Set up a volume start lock in the backup destination volumes to suppress volume startup in nodes that do not use the backup destination volumes.

2. Stopping the GDS volumes

   In the nodes that share the file system, stop the GDS volumes that the backup destination file system uses.

3. Setup of the backup relationship

   Set up the relationship between all of the partitions of the GFS Shared File System backup source and backup destination.

24.7.7.1 Lock the GDS volumes

The GDS sdxattr(1M) command sets the volume lock attribute which is used to deter a node from starting a GDS volume.

For details on the sdxattr command, see "Command Reference" in the " PRIMECLUSTER Global Disk Services Configuration and Administration Guide."

(Example) Locking the backup destination volumes

The backup destination consists of the following GDS volumes:

/dev/sfdsk/class0001/rdsk/volume0001- (class class0001, volume volume0001-)

If the GDS volumes are accessible by nodeA, nodeB, and nodeC, and the node that uses the backup destination volumes is only nodeC, the following commands are executed in nodeA and nodeB.

nodeA:
# sdxattr -V -c class0001 -v volume0001- -a lock=on
nodeB:
# sdxattr -V -c class0001 -v volume0001- -a lock=on

24.7.7.2 Stopping the GDS volumes

Before setting up the relationship, all the GDS volumes of the backup destination must be stopped. Use the GDS sdxvolume command to stop the GDS volumes. The stop operation must be executed in all nodes that share that file system.

For details on the sdxvolume command, see "Command Reference" in the "PRIMECLUSTER Global Disk Services Configuration and Administration Guide."

(Example) Stopping the backup destination volumes

The backup destination consists of the following GDS volumes:

/dev/sfdsk/class0001/rdsk/volume0001- (class class0001 and volume volume0001-)

If the volumes are accessible by nodeA, nodeB, and nodeC. The sdxvolume command is executed in nodes nodeA, nodeB, as shown below.

nodeA:
# sdxvolume -F -c class0001 -v volume0001-
nodeB:
# sdxvolume -F -c class0001 -v volume0001-
nodeC:
# sdxvolume -F -c class0001 -v volume0001-

The relationship cannot be set up when any volume of the backup source has an error status. If a volume of the backup source is stopped on any node, it will display an error status. For details on recover from an error state, refer to "Appendix F.1 Resolving Problems" in the "PRIMECLUSTER Global Disk Services Configuration and Administration Guide."

24.7.7.3 Setting up the backup relationship

The relationship between the backup source and backup destination is set up (simply called a relationship hereinafter).

A relationship is set up between all partitions that configure the GFS Shared File System that is the backup source to the partitions of the backup destination.

The corresponding partitions of the backup source and destination must relate as GDS master and proxy. Therefore, the conditions for setting up a GDS volume relationship must be satisfied between the corresponding partitions. For details, see Section 24.7.3, "Precondition." At this time, equivalent copy is executed so that the backup source and destination become equivalent.

As part of the setup of the backup source and backup destination relationship, a name is associated to identify this backup relationship. It will be referred to as the relationship name and is used by all operations to identify the specific backup relationship.

For details on sfcproxyjoin(1M), see Appendix F.2.18, "sfcproxyjoin(1M)."

(Example) Setup of relationship for EC

Use a GFS Shared File System whose representative partition is /dev/sfdsk/class0001/rdsk/volume0001 as a backup source. To relate the partition /dev/sfdsk/class0001/rdsk/volume1001 as a backup destination of this file system for the EC operation, execute the following command in the nodes that share the backup source file system for EC.

# sfcproxyjoin equivalent -r backup1_for_volume0001 \
/dev/sfdsk/class0001/rdsk/volume0001=/dev/sfdsk/class0001/rdsk/volume0001-

(Example) Setup of the relationship for OPC

Use a GFS Shared File System whose representative partition is /dev/sfdsk/class0002/rdsk/volume0002 as a backup source. To relate the partition /dev/sfdsk/class0002/rdsk/volume0002- as a backup destination of this file system for the OPC operation, execute the following command in the nodes that share the backup source file system for OPC.

# sfcproxyjoin separate -r backup1_for_volume0002 \
  /dev/sfdsk/class0002/rdsk/volume0002=/dev/sfdsk/class0002/rdsk/volume0002-

(Example) Setup of relationship for EC of group

Use a GFS Shared File System whose representative partition is /dev/sfdsk/class0003/rdsk/volume0003 on group0003 of GDS as a backup source. To relate the group0003- of GDS as a backup destination of this file system for the EC operation, execute the following command.

# sfcproxyjoin equivalent -r backup1_for_group0003 \
-g /dev/sfdsk/class0003/rdsk/volume0003 \
class0003.group0003=class0003.group0003-