When using MSCS or WSFC for cluster operation
For replication in a clustered system, note the following points that do not apply to regular operation:
If failover occurs while running a replication command, you must ensure consistency by using swsrprecoverres (Resource adjustment command) as a recovery measure.
You must perform replication on the active system of the cluster group because AdvancedCopy Manager is placed in the cluster group and operates as part of it.
You cannot perform replication from a standby node or another cluster group.
If the copy destination volume is registered as a disk resource for the cluster, run a snapshot replication with OPC.
Note
If the replication destination volume has been registered as cluster disk resources, it is recommended that you copy the partition unit.
When cluster disk resources are copied in Logical Unit units and the disk management information signature (MBR disk format) or GUID (GPT disk format) is modified, it may make it impossible to recognize the replication destination disk resources from the cluster.
Before copying in Logical Unit units, refer to "13.1.1.18 Notes on executing Logical Unit (disk) unit copy".
Use the procedure below to execute replication 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".
If the copy destination volume has been registered as a physical disk resource for the cluster, turn on the maintenance mode for physical disk resources.
> cluster [ClusterName] res <CopyDestinationVolumePhysicalDiskResourceName> /maint:on |
If the copy source volume has been registered as a physical disk resource for the cluster, turn on the maintenance mode for physical disk resources.
> cluster [ClusterName] res <CopySourceVolumePhysicalDiskResourceName> /maint:on |
Execute the replication.
> C:\Win32app\AdvancedCopyManager\bin\swsrpmake <From-Volume-Name> <To-Volume-Name> FROM=<From-Volume-Name> TO=<To-Volume-Name> swsrpmake completed > |
If the copy source volume has been registered as a physical disk resource for the cluster, turn off the maintenance mode for physical disk resources.
> cluster [ClusterName] res <CopySourceVolumePhysicalDiskResourceName> /maint:off |
If the copy destination volume has been registered as a physical disk resource for the cluster, turn off the maintenance mode for physical disk resources.
> cluster [ClusterName] res <CopyDestinationVolumePhysicalDiskResourceName> /maint:off |
If EC is used, perform inter-server replication by connecting the copy destination to a non-cluster Managed Server. For reverse replication, use snapshot replication using OPC.
For replication using EC, perform the following procedure using the maintenance mode for physical disk resources:
Start synchronous processing.
> C:\Win32app\AdvancedCopyManager\bin\swsrpstartsync <From-Volume-Name> <To-Volume-Name> FROM=<From-Volume-Name> TO=<To-Volume-Name> swsrpstartsync completed > |
Check the equivalency maintenance state.
Turn on the maintenance mode for physical disk resources (the copy source volume).
> cluster [ClusterName] res <CopySourceVolumePhysicalDiskResourceName> /maint:on |
Execute the replication.
> C:\Win32app\AdvancedCopyManager\bin\swsrpmake <From-Volume-Name> <To-Volume-Name> FROM=<From-Volume-Name> TO=<To-Volume-Name> swsrpmake completed > |
Turn off the maintenance mode for physical disk resources (the copy source volume).
> cluster [ClusterName] res <CopySourceVolumePhysicalDiskResourceName> /maint:off > cluster [ClusterName] res DiskResourceName /maint |
If REC is used, perform inter-server replication by connecting the copy destination to a non-cluster Managed Server. For reverse replication, use synchronized replication using REC.
For reverse replication using REC, perform the following procedure using the maintenance mode for physical disk resources:
Turn on the maintenance mode for physical disk resources (i.e., the copy destination volume).
> cluster [ClusterName] res <CopyDestinationVolumePhysicalDiskResourceName> /maint:on |
Start synchronous processing.
> C:\Win32app\AdvancedCopyManager\bin\swsrpstartsync <From-Volume-Name> <To-Volume-Name> FROM=<From-Volume-Name> TO=<To-Volume-Name> swsrpstartsync completed > |
Check the equivalency maintenance state.
Execute the replication.
> C:\Win32app\AdvancedCopyManager\bin\swsrpmake <From-Volume-Name> <To-Volume-Name> FROM=<From-Volume-Name> TO=<To-Volume-Name> swsrpmake completed > |
Turn off the maintenance mode for physical disk resources (i.e., the copy destination volume).
> cluster [ClusterName] res <CopyDestinationVolumePhysicalDiskResourceName> /maint:off |
Note that once physical disk resources have been set offline during synchronous processing (between step 2 and step 4) they cannot be set online again.
If physical disk resources have been set offline during synchronous processing, use the following procedure to resolve the problem:
Stop the synchronous processing from the non-cluster Managed Server.
> C:\Win32app\AdvancedCopyManager\bin\swsrpcancel -m <From-Volume-Name> <To-Volume-Name> FROM=<From-Volume-Name> TO=<To-Volume-Name> swsrpcancel completed > |
Set the physical disk resources online, and then execute the reverse replication again.
For backup and restoration of an Exchange 2003/2007 database in cluster operation, perform the following steps to operate the Exchange linkage function in MSCS:
Create Exchange transactions and AdvancedCopy Manager transactions in one cluster group.
For Exchange Server 2003
Do not use the same logical IP address for Exchange Server and AdvancedCopy Manager.
For Exchange Server 2007
Use the same logical IP address for Exchange Server and AdvancedCopy Manager. (Create the Exchange transaction, and then create the AdvancedCopy Manager transaction.)
To execute an AdvancedCopy Manager's command, specify the name of the logical node for AdvancedCopy Manager in the environment variable SWSTGNODE beforehand.
To execute the Exchange linkage command (swsrpXXX_exchange, swsrpXXX_exchange2k3) of AdvancedCopy Manager, use the -evs option and specify the virtual server name of the Exchange Server as an argument.
Place the device map file so that both the primary node and secondary node can reference it (place it on a shared disk or local disks in both nodes).
For backup and restoration of an SQL Server database in cluster operation, perform the following steps to operate the SQL Server backup function in MSCS or WSFC cluster operations:
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. (i.e., place it on a shared disk or local disks in both nodes)
For backups and restorations performed with a Hyper-V guest OS operating under the clustered system, there are the following items of caution.
If performing cluster operation of the Hyper-V backup function with WSFC, please do the following.
Use the AdvancedCopy Manager's agent installed to each physical server. As such, please do not set the environment variable SWSTGNODE when executing commands.
Place the guest OS list files such that it is possible to refer to them from both the primary node and the secondary node.
Please place the files either on a shared disk or on the local disks of both nodes.
When using MSCS or WSFC for cluster operation
When a cluster group to which AdvancedCopy Manager belongs is operating, replication operation is enabled only on the active node. The standby node environment is not ready (to provide necessary resources) for replication operation, thus disabling replication operation. Likewise, if the cluster group has been stopped, the environment is not ready and disables replication operation.
However, only when the cluster group has been stopped is the replication operation enabled by temporarily arranging the minimum essential resources.
Note
If any of the following resources cannot start (i.e., cannot be brought online), replication 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 a Management Server transaction)
Replication operation disks (source volume/destination volume to operate)
Perform replication the operation during the stoppage of a cluster group by performing 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 "Chapter 2 Starting and Stopping Services".
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)
Replication operation disks (source volume/destination volume to operate)
Note
Be sure to start the resources from only one of these nodes.
Since the dependency between AdvancedCopy COM Service_logical-node-name and 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 replication operation.
You can perform replication operation in the same way as for regular cluster operations.
Stop (i.e., set to 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 to 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.
