When using MSCS or WSFC for cluster operation
For backups 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 the resource adjustment command as a recovery measure.
You must perform backups on the active system of the cluster group because AdvancedCopy Manager is placed in the cluster group and operates as part of the cluster group.
You cannot make a backup from a standby node or another cluster group.
Note
From a volume used as a backup volume, delete the drive letter by performing the following steps:
You must take these steps before fetching device information on a Managed Server:
On the primary node, use the Disk Management to delete the drive letter of the backup volume.
Change to the secondary node.
On the secondary node, use the Disk Management to delete the drive letter of the backup volume.
Change to the primary node.
The steps above prevent a drive letter from being assigned to the backup volume in case of MSCS or WSFC failover.
Perform snapshot high-speed backup operations using OPC.
Use the procedure below to execute backups and restorations in the maintenance mode for physical disk resources.
Point
Enter a command using the following syntax to check the maintenance mode status of a physical disk resource.
cluster [ClusterName] res DiskResourceName /maint |
If "Online" is displayed as the "Status", the maintenance mode is "OFF".
If "Online (maintenance)" is displayed as the "Status", the maintenance mode is "ON".
Turn on the maintenance mode for physical disk resources (i.e., the transaction volumes and backup volumes).
> cluster [ClusterName] res <TransactionVolumePhysicalDiskResourceName> /maint:on > cluster [ClusterName] res <BackupVolumePhysicalDiskResourceName> /maint:on |
Execute the backup or restoration.
> C:\Win32app\AdvancedCopyManager\bin\swstbackup Device-Name Device-Name swstbackup completed > |
Turn off the maintenance mode for physical disk resources (i.e., the transaction volumes and backup volumes).
> cluster [ClusterName] res <TransactionVolumePhysicalDiskResourceName> /maint:off > cluster [ClusterName] res <BackupVolumePhysicalDiskResourceName> /maint:off |
If EC is used, perform inter-server replication operations where the copy destination is connected to a non-cluster Managed Server.
For backup and restoration of an SQL Server database in cluster operation, note the following points:
Perform the following steps to operate the SQL Server backup function in MSCS or WSFC:
Create SQL Server transactions and AdvancedCopy Manager transactions in one cluster group. Do not share a logical IP address with SQL Server and AdvancedCopy Manager.
To execute swsrpbackup_sql (SQL Server backup execution command), specify the name of the logical node for AdvancedCopy Manager in the environment variable SWSTGNODE beforehand.
To execute swstbackup_sqlsvr (SQL Server backup execution command) or swstrestore_sqlsvr (SQL Server restore execution command), use the -Xserver option and specify the virtual server name of the SQL Server as an argument.
Place the device map file so that both the primary node and secondary node can reference it by placing it on a shared disk or local disks in both nodes.
When using MSCS or WSFC for cluster operation
When a cluster group 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 the necessary resources, thus disabling backup operation. Likewise, if the cluster group has been stopped, the environment is not ready and it disables the backup.
However, the backup operation is re-enabled only when the cluster group has been stopped, by temporarily arranging the minimum resources.
Note
If any of the following resources cannot start (i.e., if they cannot be set online), the backup operation is disabled:
AdvancedCopy GUI Service (only for a Management Server transaction)
SymfoWARE RDA RDBSWSTF (only for a Management Server transaction)
There is no "SymfoWARE RDA RDBSWSTF" resource if it is running under Windows Server 2008 or later.
SymfoWARE RDB RDBSWSTF (only for a Management Server transaction)
AdvancedCopy COM Service_logical-node-name
IP address resource (When created by the cluster setup command of AdvancedCopy Manager, the resource is named in "AdvancedCopy IP Address_logical-node-name" format.)
Disk resource for a shared disk for AdvancedCopy Manager shared data
Disk resource for the shared disk for the AdvancedCopy Manager repository (only for Management Server transaction)
Backup operation disk (transaction volume/backup volume to operate)
Perform backup operation during the stoppage of a cluster group by taking the following steps:
Confirm that the cluster group has been stopped (i.e., that it has been set offline) on both nodes.
For details on how to stop a cluster group, refer to the MSCS or WSFC manual.
Start (i.e., set online) the resources required for operation.
Start the following resources:
AdvancedCopy GUI Service (only for a Management Server transaction)
SymfoWARE RDA RDBSWSTF (only for a Management Server transaction)
There is no "SymfoWARE RDA RDBSWSTF" resource if it is running under Windows Server 2008 or later.
SymfoWARE RDB RDBSWSTF (only for a Management Server transaction)
AdvancedCopy COM Service_logical-node-name
IP address resource (when created by the cluster setup command of AdvancedCopy Manager, the resource is named in "AdvancedCopy IP Address_logical-node-name" format).
Disk resource for a shared disk for AdvancedCopy Manager shared data
Disk resource for the shared disk for the AdvancedCopy Manager repository (only for a Management Server transaction)
Backup operation disk (the transaction volume/backup volume to operate)
Note
Be sure to start the resources from one of the nodes only.
Since the dependency between AdvancedCopy COM Service_logical-node-name and the transaction disk has been set, starting AdvancedCopy COM Service_logical-node-name starts all dependent disk resources.
For details on how to start a resource, refer to the MSCS or WSFC manual.
In the environment variable SWSTGNODE, set the logical node name for the relevant task.
Set the environment variable as shown below.
<Execution example>
set SWSTGNODE=logical-node-name |
Perform the backup.
You can perform the backup in the same way as for regular cluster operations.
Stop (i.e., set offline) the resources you started in step 2.
For details on how to stop a resource, refer to the MSCS or WSFC manual.
Start (i.e., set online) the cluster group.
Start the cluster group, if necessary.
For details on how to start a cluster group, refer to the MSCS or WSFC manual.
