SynfinityCLUSTER or PRIMECLUSTER
For backup operation in a clustered system, note the following points that do not apply to regular operation:
If failover occurs while running a backup command, you must secure consistency by using swstsrsemtch (Resource match command) as a recovery measure.
You must perform backup operation on the active server of the cluster service (userApplication) because AdvancedCopy Manager is placed in the cluster service (userApplication) and operates as part of said cluster service (userApplication).
You cannot make a backup from a standby node or another cluster service (userApplication).
SynfinityCLUSTER
Note the following points if a file system has been created on a transaction volume and the file system has been registered as a cluster resource:
Change the backup pre-processing so that the transaction volume is not unmounted. Refer to "A.2 Pre-processing and Post-processing of Backup" for information about changing backup pre-processing.
It is not possible to restore data using swstrestore (Restore execution command) during transaction operations. To restore data on the volume, either copy the data using the dd command, or mount the backup volume and copy the necessary data. Alternatively, perform the procedure described in "9.1.7.1 Backup and restoration during the stoppage of a cluster".
PRIMECLUSTER 4.1A30 or later
If a file system has been created on a transaction volume, and the file system has been registered as a cluster resource, use the following procedure to back up and restore data.
Follow the procedure below to perform backup/restore.
Switch userApplication to Maintenance mode.
# hvutil -m on userApplication |
Unmount the transaction volume (this is mandatory to backup or restore a transaction volume in the file system).
If the transaction volume was unmounted, then make sure that the cluster resources of the transaction volume are Offline (wait until the return value of the command is 0):
# hvassert -s <transaction_volume> <cluster_resource_name> Offline |
Perform backup or restore
# /opt/FJSVswsts/bin/swstbackup Device-Name Device-Name swstbackup completed or # /opt/FJSVswsts/bin/swstrestore Device-Name Device-Name swstrestore completed |
If the transaction volume was unmounted, then mount it back.
Make sure that the cluster resources of the transaction volume are Online (wait until the return value of the command is 0):
# hvassert -s <transaction_volume> <cluster_resource_name> Online |
Stop the Maintenance mode for the userApplication.
# hvutil -m off userApplication |
Start synchronization processing.
# /opt/FJSVswsts/bin/swststartsync Device-Name Device-Name swststartsync completed |
Check the equivalency maintenance status.
Swith userApplication to Maintenance mode.
# hvutil -m on userApplication |
Unmount the transaction volume (this is mandatory to backup/restore a transaction volume in the file system).
If the transaction volume was unmounted , then make sure that the cluster resources of the transaction volume are Offline (wait until the return value of the command is 0):
# hvassert -s <transaction_volume> <cluster_resource_name> Offline |
Perform backup.
# /opt/FJSVswsts/bin/swstbackup Device-Name Device-Name swstbackup completed |
If the transaction volume was unmounted, then mount it back.
Make sure that the cluster resources of the transaction volume are Online (wait until the return value of the command is 0):
# hvassert -s <transaction_volume_cluster_resource_name> Online |
Stop Maintenance mode for userApplication.
# hvutil -m off userApplication |
Note
In either procedure, if the transaction volume is unmounted, then the pre-processing and post-processing scripts will not be executed (they are only executed when the transaction or replication source volumes are mounted).
Take this into account if the applicable parts of the pre-processing and post-processing scripts are being customized.
The cluster detector detects the status of cluster resources either periodically or asynchronously. Therefore, it may take a few moments for the cluster resource status to be reflected, depending on the system load, and on the timing of mounting/unmounting the transaction volume. This means that the status may not be able to be checked using the hvassert command.
Due to this fact, note the following about the timing of using hvassert to check the cluster resource status:
Once the mounting/unmounting of the file system of a cluster FSystem resource has finished, only use hvassert after the time elapsed is equal to or greater than the cluster resource monitoring interval.
You can specify the maximum time to wait until the cluster reaches the desired status by using hvassert with the -w option:
# hvassert -w <replication_vol> Offline|Online <max_wait_time(secs)> |
When using hvassert with the -w option, the system load and cluster resource reflection processing time must also be taken into account.
Due to that, make sure to specify a value that suits the system operating environment, purpose, and requirements.
In PRIMECLUSTER 4.2, the default monitoring interval for the PRIMECLUSTER Fsystem resource is 10 seconds - check the default value for your version.
For details on the hvassert command, refer to the "PRIMECLUSTER Installation and Administration Guide", section "hvassertt(1M)".
VERITAS Cluster Server
For backup operation in a clustered 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.
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, the df or sleep command to function until mount/unmount is actually complete.
For details and examples on the pre-processing and post-processing scripts, refer to "Appendix A Pre-processing and Post-processing of Backup and Restoration". For details on the commands used to set resources offline and online, refer to the relevant cluster software manual.
SynfinityCLUSTER or PRIMECLUSTER
When a cluster service (userApplication) to which AdvancedCopy Manager belongs is operating, backup operation is enabled only on the active node. The standby node environment is not ready (to provide necessary resources) for backup operation, thus disabling backup operation. Likewise, if the cluster service (userApplication) has been stopped, the environment is not ready and disables backup operation.
However, only when the cluster service (userApplication) has been stopped is backup operation enabled by temporarily arranging the minimum essentials.
Note
When transactions in scalable operation are handled together, only stop cluster service (userApplication) in scalable operation; do not stop cluster service (userApplication) for Managed Server (or Management Server) transactions.
Enabling backup operation disks (transaction volume and backup volume to operate) allows you to perform backup operation in the same way as for regular operations.
If a backup operation disk cannot be enabled, you cannot perform backup operation while user applications in scalable operation are stopped.
If any of the following types of shared disks cannot be enabled (i.e., set online or mounted in a system), backup operation 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 operation:
Backup/restoration through Web Console
Manipulation for backup operation from a 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 Management Server transaction that also functions as a Managed Server transaction, you must specify options for the command. For details on the display command for backup management, refer to the "8.2 Backup Management Commands".
Perform backup operation while a cluster service (userApplication) is stopped by taking the following steps:
Confirm that the cluster service (userApplication) has been stopped on both nodes.
For details on how to stop a cluster service (userApplication), refer to the PRIMECLUSTER manual.
Log in to the node on which you want to make a backup through telnet, for example.
You cannot use the logical IP address. Directly use a node that is operable by using 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 backup operation.
You can perform backup operation in the same way as for regular operations for cluster operation.
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 cluster service (userApplication).
Start the cluster service (userApplication), if necessary.
For details on how to start a cluster service (userApplication), refer to the PRIMECLUSTER 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 Web Console
Manipulation for backup operation from a 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 Management Server transaction that also functions as a Managed Server transaction, you must specify options for the command. For details on the display command for backup management, refer to "8.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, refer to 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 environment variable SWSTGNODE, 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, refer to the VERITAS Cluster Server manual.
