Backup operation in units of logical volumes is possible in collaboration with GDS Snapshot.
The physical structure of the logical volumes is not important.
Figure 3.11 Backup operation in units of logical volumes
To specify a GDS logical volume in the AdvancedCopy Manager command, specify the GDS logical volume name.
/dev/sfdsk/<class-name>/dsk/<volume-name>
Note
AdvancedCopy Manager does not support the following SDX objects (volumes):
Volume of a shadow class
Stripe volume
Switch volume
Volume in a concatenation group
Stripe groups and concatenation groups, however, can be used as subordinate groups of a mirror group.
Copying cannot be processed in the following circumstances:
If the total number of the slices that make up the transaction volume plus all slices that make up all backup volumes associated with the transaction volume at the start of synchronous processing or snapshot-type backup processing is 33 or greater.
If either the source volume (the transaction volume for backup processing or the backup volume for restore processing) are in an invalid state.
Point
To confirm the type of volume being used, (that is: single, mirror, stripe, concatenation, or switch), execute "sdxinfo -e long" at the command line and check the volume type attribute values returned.
The value in the TYPE column on the line indicated for the volume in the OBJ column will match one of the following:
single : Single volume (supported)
mirror : Mirror volume (supported)
stripe : Stripe volume (not supported)
concat : Volume in a concatenation group (not supported)
switch : Switch volume (not supported)
The following information about performing the backup operation should be noted.
For a backup performed in collaboration with GDS Snapshot, AdvancedCopy Manager processes binding, separation, and release of volumes by using the GDS Snapshot function.
Therefore, an SDX object used by AdvancedCopy Manager must be set to a state in which the object can operate as either a master object or proxy object.
A transaction volume operates as a master object, and a backup volume as a proxy object.
Configure the GDS volume structure accordingly before registering a volume with AdvancedCopy Manager.
When configuring SDX objects of GDS for use by AdvancedCopy Manager, pay careful attention to the relevant structure attributes of "3.8.2.2 Transaction volume" and "3.8.2.3 Backup volumes" described in the next sections.
For details on GDS Snapshot and premises of the proxy structure, refer to the "PRIMECLUSTER(TM) Global Disk Services User's Guide (Solaris(TM) Operating Environment)".
To use an SDX object (logical volume) for transactions, register it as a transaction volume.
The transaction volume operates as a master object of GDS Snapshot.
Therefore, note the following about configuring the backup operation:
An SDX object that belongs to a shadow class cannot be registered as the transaction volume.
The only types of logical volumes that can be registered as the transaction volume are single volumes and mirror volumes.
A stripe volume, a volume in a concatenation group, or a switch volume cannot be registered as the transaction volume.
Stripe groups and concatenation groups, however, can be used as subordinate groups of a mirror group.
A volume in a disk group to which a backup volume also belongs cannot be registered as the transaction volume.
A logical volume that belongs to the single disk group with a backup volume cannot be registered as the transaction volume.
If any of the slices that make up the transaction volume are separated temporarily or are being copied, backup cannot be performed.
If the transaction volume (logical volume) is in the invalid state, backup cannot be performed.
A proxy object of GDS Snapshot cannot be used as the transaction volume.
Register an SDX object (logical volume) as a backup volume.
The backup volume operates as a proxy object of GDS Snapshot.
Therefore, note the following about configuring the backup operation:
An SDX object that belongs to a shadow class cannot be registered as a backup volume.
The types of logical volumes that can be registered as backup volumes are single volumes and mirror volumes. A stripe volume, a volume in a concatenation group, or a switch volume cannot be registered as a backup volume.
Stripe groups and concatenation groups, however, can be used as subordinate groups of a mirror group.
A volume in a disk group to which a transaction volume also belongs cannot be registered as a backup volume.
A logical volume that belongs to the single disk with the transaction volume cannot be registered as a backup volume.
An object whose class is different from that of the transaction volume cannot be used as a backup volume.
A master object of GDS Snapshot cannot be used as a backup volume.
A backup volume for backup by using EC or OPC must be a non-mirroring volume. If the backup volume is in a mirroring structure, only software-copy can be used.
If a backup volume is in use or is accessible by any application, backup cannot be performed.
If any slices of the slices that make up a backup volume is separated temporarily or being copied, backup cannot be performed.
As a backup volume, a logical volume must be the same size as the transaction volume.
For the backup operation, the total number of the slices that make up the transaction volume and slices that make up all backup volumes associated with the transaction volume must not exceed 32.
The following copy functions can be used in linkage with GDS Snapshot:
Advanced copy: Copying with the hardware function of ETERNUS Disk storage system
Software-copy: Copying with the disk driver of PRIMECLUSTER GDS
The following table shows the relationship between SDX object structures and their available copy functions.
Unit | Volume | SDX object structure(*1) | Available copy function | |
|---|---|---|---|---|
Logical volume | Transaction | Single | Advanced Copy / Software-copy | |
Mirror | No subordinate group exists. | Advanced Copy / Software-copy | ||
A subordinate group exists. | Software-copy | |||
Backup | Single | Advanced Copy / Software-copy | ||
Mirror | This consists of one disk. | Advanced Copy / Software-copy | ||
This consists of multiple disks. | Software-copy | |||
(*1) Stripe- and concatenation-type objects cannot be copied.
Unit | Volume | SDX object structure(*1) | Available copy function | |
|---|---|---|---|---|
Logical volume | Backup | Single | Advanced Copy / Software-copy | |
Mirror | No subordinate group exists. | Advanced Copy / Software-copy | ||
A subordinate group exists. | Software-copy | |||
Transaction | Single | Advanced Copy / Software-copy | ||
Mirror | This consists of one disk. | Advanced Copy / Software-copy | ||
This consists of multiple disks. | Advanced Copy / Software-copy | |||
(*1) Stripe-, concatenation-, and switch-type objects cannot be copied.
Specify options when performing backup to a backup volume in a box that does not contain the transaction volume.
Backup with GDS Snapshot does not require a setting to indicate inter-box copying.
To perform the backup operation with a Managed Server and obtain information of a subordinate device related to the Managed Server, you must register the server.
For details on how to fetch the device information, refer to the section titled "3.4.4 Fetching device information on a Managed Server".
Register a GDS logical volume as a transaction volume or backup volume.
# /opt/FJSVswsts/bin/swstdevinfoset -t /dev/sfdsk/CLS1/dsk/vol1 swstdevinfoset completed # /opt/FJSVswsts/bin/swstdevinfoset -b /dev/sfdsk/CLS1/dsk/bvol1 swstdevinfoset completed |
Note
The following SDX objects cannot be registered as transaction volumes or backup volumes:
Object of a shadow class
Stripe-type object
Concatenation-type object
Switch-type object
Checking the number of backup generations
Before configuring a backup policy, the required number of backup volumes for operation must be prepared according to the backup policy. (For details, refer to the section titled "3.4.7 Setting a backup policy".)
If the transaction volume is an SDX object, verify that there are enough backup volumes registered as proxy objects to match the required number of backup generations.
If the transaction volume is a GDS logical volume, each backup volume must be also a GDS logical volume.
#/opt/FJSVswsts/bin/swstbkpolset -s 3 /dev/sfdsk/CLS01/dsk/VOL01 /dev/sfdsk/CLS01/dsk/VOL01 swstbkpolset completed # |
Note
In the following cases, some SDX objects are not counted as available backup volumes:
Where the backup volume is an object whose class is different from that of the transaction volume
Where the size of the backup volume is different from that of the transaction volume
Limit on the number of slices
Where an SDX object is to be backed up, the transaction volume is described as the master and its associated backup volume is described as the proxy. Therefore, the total number of the slices that make up the transaction volume plus the number of slices that make up the associated backup volume must not exceed 32. Consequently, the number of backup generations that can be used is limited according to the GDS structure. This will be important when configuring a backup policy.
For example, if both the transaction volume and backup volume are single volumes, you can set the number of backup generations to 31, which is the maximum value. However, if both the transaction volume and backup volume have a two-slice structure, the number of backup generations is limited to 15. If 16 or a higher value is set, the 16th generation and subsequent generations are not backed up.
Backup in units of logical volumes
If the transaction volume is an SDX object, select a backup volume that can be a valid proxy object for backup.
AdvancedCopy Manager automatically selects it from the registered backup volumes.
# /opt/FJSVswsts/bin/swstbackup /dev/sfdsk/CLS1/dsk/vol1 /dev/sfdsk/CLS1/dsk/vol1 swstbackup completed |
Available copy processing methods
The available copy methods vary depending on the hardware environment or configuration supporting the GDS logical volumes.
EC/OPC cannot be used in the following cases:
The backup volume is an SDX object in a mirroring structure
A subordinate group is connected to the disk group to which the transaction volume and backup volume belong
Hardware | Available copy processing method |
|---|---|
EC/OPC can be used. | Synchronous high-speed backup: EC, software-copy Snapshot-type high-speed backup: OPC |
Only OPC can be used. | Synchronous high-speed backup: Software-copy Snapshot-type high-speed backup: OPC |
EC/OPC cannot be used. | Synchronous high-speed backup: Software-copy Snapshot-type high-speed backup: Unavailable |
Restoration to a transaction volume in units of logical volumes
This process can be carried out using either the Web Console or a command.
For restoration to a transaction volume in units of GDS logical volumes, copy the proxy to the master.
# /opt/FJSVswsts/bin/swstrestore /dev/sfdsk/CLS1/dsk/vol1 /dev/sfdsk/CLS1/dsk/vol1 swstrestore completed |
Restoration with the restore destination specified
If the transaction volume is a GDS logical volume, restoration cannot be performed with the restore destination specified.
Available copy processing methods
The available copy processing methods vary depending on the hardware environment or configuration supporting the GDS logical volumes.
OPC cannot be used in the following case:
A subordinate group is connected to the disk group to which the transaction volume and backup volume belong.
Hardware | Available copy processing method |
|---|---|
OPC can be used. | OPC, software-copy |
OPC cannot be used. | Software-copy |
Do not use the "sdxproxy" command directly to change the state of a volume registered for backup management.
Use of the "sdxproxy" command may create inconsistencies between the backup management information and the actual volume state. In such cases, perform recovery by executing swstsrsemtch (Resource match command).
