MC/ServiceGuard
For backups in a cluster system, note the following points that do not apply to regular operation:
If failover occurs while running a backup command, you must ensure consistency by using swstsrsemtch (Resource match command) as a recovery measure.
You must define a volume group of backup volumes in "VOLUME GROUPS" on the transaction-oriented package control script.
Example:
VG[1]=vg02 |
In cluster operation, you must perform backups on the active system of the package because AdvancedCopy Manager is placed in the package and operates as part of the package.
You cannot make a backup from a standby node or another package.
If the backup volume belongs to a volume group and failover occurs while synchronization (EC/REC) is being handled, package startup is disabled because the backup volume cannot be activated on the standby node.
Therefore, you should perform OPC-based, snapshot type, high speed backups in a cluster environment.
If package startup is disabled during an EC-based, synchronous high speed backup, forcibly stop synchronization by using ETERNUS Web GUI or similar, and then start the package.
VERITAS Cluster Server
For backup operation in a cluster system, note the following points that do not apply to regular operation:
If failover occurs while running a backup command, you must ensure consistency by using swstsrsemtch (Resource adjustment command) as a recovery measure.
To use synchronous high-speed backup, do not register a backup to any cluster transaction.
You must perform backups on the active server of the service group because AdvancedCopy Manager is placed into the service group and operates as a part of it.
You cannot make a backup from a standby node or another service group.
To perform backup/restoration using AdvancedCopy Manager, you usually must unmount transaction volumes beforehand and mount the volumes later.
If the mount point of transaction volumes have been registered to a cluster transaction, set the mount point resource online or offline from the cluster transaction instead of mounting or unmounting the volumes. Alternatively, modify the backup/restoration pre-processing and post-processing scripts so that the transaction volumes are set offline or online instead of being unmounted or mounted.
Moreover, the Volume is immediately placed offline/online for a mount point resource whereas there will be a time delay when mount/unmount is used. Therefore, please add into the pre-processing script after the statement where the success or failure value of offline/online is returned, a "df" command with a sleep operand to function until mount/unmount is actually complete.
For details and examples on the pre-processing and post-processing scripts, see "Appendix A Pre-processing and Post-processing of Backup and Restoration". For details on the commands used to set resources offline and online, see the relevant cluster system manual.
MC/ServiceGuard
When the package to which AdvancedCopy Manager belongs is operating, backup is enabled only on the active node. The standby node environment is not ready to provide the necessary resources, thus disabling backup operation. Likewise, if the package has been stopped, the environment is not ready and backup is disabled.
However, the backup operation is re-enabled only when the package has been stopped, by temporarily arranging the minimum resources.
Note
If either of the following types of shared disks cannot be enabled (ie, be set online or mounted in a system), backup is disabled:
Shared disk for AdvancedCopy Manager shared data
Backup operation disk (transaction volume/backup volume to operate)
The following operations are not allowed in a backup:
Backup/restore using the GUI
Manipulation of a backup operation from a Storage Management Server (host specification with the "-h" option)
Addition or deletion of a transaction volume/backup volume, or a change in policy
If display-related commands are executed by Storage Management Server transactions or Storage Server transactions, options must be specified in the commands. Refer to "9.2 Backup Management Commands" for details of backup management display-related commands.
If the package has been stopped, perform a backup by taking the following steps:
Confirm that the package has been stopped on both nodes.
For details on how to stop the package, see the MC/ServiceGuard manual.
Log in to the node on which you want to make a backup, for example through telnet.
You cannot use the logical IP address. Directly use a node that is accessible via the physical IP address.
Enable the shared disk.
Start (set online) the shared disk.
Mount the shared disk for AdvancedCopy Manager shared data.
When the transaction volume is a file system, mount it.
Note
Be sure to enable the shared disk from only one of the nodes, not both.
In the SWSTGNODE environment variable, set the logical node name for the relevant task.
Set the environment variable as shown below.
<Execution example>
# SWSTGNODE=logical-node-name # export SWSTGNODE |
Perform the backup.
You can perform the backup in the same way as for regular cluster operations.
Release all the shared disks you enabled in Step 3.
Unmount the file systems you mounted.
Stop (set offline) the shared disk.
Start (set online) the package.
Start the package, if necessary.
For details on how to start the package, see the MC/ServiceGuard manual.
VERITAS Cluster Server
When a service group to which AdvancedCopy Manager belongs is operating, backup is enabled only on the active node. The standby node environment is not ready (to provide necessary resources) for backup operation, therefore backup is disabled. Likewise, if the service group has been stopped, the environment is not ready and disables backup operation.
However, backup is temporarily enabled when the service group is stopped.
Note
If any of the following types of shared disks cannot be enabled (i.e., set online or mounted in a system), backup is disabled:
Shared disk for AdvancedCopy Manager shared data
Backup operation disk (transaction volume/backup volume to operate)
The following operations are not allowed in backup:
Backup/restoration through GUI
Manipulation for backup operation from a Storage Management Server (host specification with the "-h" option)
Addition or deletion of a transaction volume/backup volume, or change in policy
To execute a display command for backup management to a Storage Management Server transaction that also functions as a Storage Server transaction, you must specify options for the command. For details on the display command for backup management, refer to "9.2 Backup Management Commands".
If the service group has been stopped, perform a backup by taking the following steps:
Confirm that the service group has been stopped on both nodes.
For details on how to stop a service group, see the VERITAS Cluster Server manual.
Log in (for example, using Telnet) to the node on which you want to make a backup.
You cannot use the logical IP address. Use a node that is operable via the physical IP address.
Enable the shared disk.
Start (set online) the shared disk.
Mount the shared disk for AdvancedCopy Manager shared data.
When the transaction volume is a file system, mount it.
Note
Be sure to enable the shared disk from either node. Do not enable the shared disk from both nodes.
In the SWSTGNODE environment variable, set the logical node name for the relevant task.
Set the environment variable as shown below.
<Execution example>
# SWSTGNODE=logical-node-name # export SWSTGNODE |
Perform the backup.
You can perform the backup in the same way as for regular operations in a cluster environment.
You can use swstrestore (Restore execution command) to perform restoration.
Release all the shared disks you enabled in Step 3.
unmount the file systems you mounted.
Stop (set offline) the shared disk.
Start (set online) the service group.
Start the service group, if necessary.
For details on how to start a service group, see the VERITAS Cluster Server manual.
