Follow below procedure for setting up CCM Server transactions.
Log in to the primary and secondary nodes. Perform the operation after logging in as a root user.
Note
If AdvancedCopy Manager CCM is currently operating on any node in the cluster, use the following commands to stop all AdvancedCopy functions that are being executed.
acopc cancel command
acsnap cancel command
acec cancel command
If a management service is being executed, run the acservice stop command with the -lan option to stop the management service.
Stop the CCM Server transactions.
If you are setting up CCM Server transactions within already existing cluster transactions, stop the relevant cluster transactions.
Refer to your cluster software documentation for the procedure for stopping cluster transactions.
Mount the shared disk for shared data.
Make settings to allow access from the primary node to the file system of the shared disk for shared data.
Customize the primary node.
For Solaris: Refer to "5.2.1.3.2 Customization procedure".
For Linux: Refer to "5.3.1.3.2 Customization procedure".
Customize the secondary node.
For Solaris: Refer to "5.2.2.3.2 Customization procedure".
For Linux: Refer to "5.3.2.3.2 Customization procedure".
On the primary node, register the resources in the CCM Server transactions.
The resources required for CCM Server transactions are as follows:
Shared disk for shared data
Refer to "10.2 Resources required for Solaris/Linux version clustered systems" for details.
Generic script for AdvancedCopy Manager CCM
Refer to "4.1.4 Resources required for AdvancedCopy Manager CCM" for details.
Refer to your cluster software documentation for the procedure for registering resources in CCM Server transactions.
Note
Set the dependencies of the shared disk for shared data in such a way that it is mounted before executing the generic script for AdvancedCopy Manager CCM.
Refer to "4.1.4 Resources required for AdvancedCopy Manager CCM" for information on the generic script for AdvancedCopy Manager CCM.
On the primary node, start the CCM Server transactions.
Set the environment variable PATH.
Add the bin directory of AdvancedCopy Manager CCM to the environment variable PATH.
Refer to "Setting PATH environment variable" in "Setup of AdvancedCopy Manager CCM" in the ETERNUS SF Installation and Setup Guide for details.
Set up the network environment.
Refer to "Configuring the network environment" in "Setup of AdvancedCopy Manager CCM" in the ETERNUS SF Installation and Setup Guide for details.
Create a user account.
Create a user account for using AdvancedCopy Manager CCM.
Refer to "Creating CCM User Accounts" in the ETERNUS SF Installation and Setup Guide for details.
Set up access volumes on all nodes that are operating the clustered system.
Refer to "4.1.4 Resources required for AdvancedCopy Manager CCM" and to "Access Volume Settings" in the ETERNUS SF Operation Guide for Copy Control Module for details.
Register the ETERNUS Disk storage system.
Refer to "Registering ETERNUS Disk storage system" in the ETERNUS SF Operation Guide for Copy Control Module for details.
Note
Use the same access volume for all nodes in the cluster.
If you use an access volume, when you register the ETERNUS Disk storage system, execute the acarray add command with the -path option specified.
Create a copy group.
Refer to "Creating copy groups" in the ETERNUS SF Operation Guide for Copy Control Module for details.
Add a copy pair.
Add a copy pair to the newly created copy group.
Refer to "Adding copy pairs" in the ETERNUS SF Operation Guide for Copy Control Module for details.
Set up copy volume protection.
In order to prevent destruction of the volume by any mistakes in operation, you can set the volume protection function on the transaction volume.
Refer to "Setting Copy Volume Protection" in the ETERNUS SF Operation Guide for Copy Control Module for details.
Back up the environment setup files for the Managed Server transactions.
To be prepared for unexpected situations, back up the environment setup files.
Refer to "Backing up environment settings files" in the ETERNUS SF Operation Guide for Copy Control Module for the files to be backed up.
See
Refer to "Commands" in the ETERNUS SF Operation Guide for Copy Control Module for information on the commands.
