To set up a Storage Management Server transaction and a Storage Server transaction, use the procedure below.
Restart the system.
Restart the primary node and all secondary nodes. If the system is restarted in an extension of the installation process of AdvancedCopy Manager, proceed to step 2.
Note
If VERITAS Cluster Server 5.0 is used, modify the following files:
/opt/FJSVswstf/cluster/smgr_vstart_OK
/opt/FJSVswstf/cluster/smgr_vstop_OK
"Contents to be changed"
/opt/FJSVswstf/cluster/smgr_vstart_OK
exit 1 -> exit 110
/opt/FJSVswstf/cluster/smgr_vstop_OK
exit 0 -> exit 100
* Make these changes on all primary nodes and secondary nodes where the cluster is being set up.
Check the preparations.
Check each item of "3.3 Confirmation of items," for the Service Group to be set up.
Mount the shared disk on the primary node.
For a Storage Management Server transaction, mount the shared disk for shared data (one partition). Also mount the shared disk for the repository (mount all shared disks where repository directories will be created) on the primary node.
For a Storage Server transaction, mount the shared disk for shared data on the primary node.
Stop the Service Groups.
To add a Storage Management Server transaction and a Storage Server transaction to an existing Service Group by using the VERITAS Cluster Server function, stop the applicable Service Group.
For information on how to stop the user Service Group, see the "VERITAS Cluster Server User's Guide."
# hagrp -offline User-Service-Group -sys system-name |
system-name: The node name by which the user service group is started
Register port numbers
Register the port number for the transaction communication in /etc/services. Use an OS command such as vi to register it in /etc/services.
Transaction communication daemon: stgxfws_Logical-Node-Name
Note
Register the same port number on the primary node and all secondary nodes.
Execute the cluster setup command on the primary node.
For a Storage Management Server transaction, on the primary node, execute the cluster setup command shown below after blocking other users from accessing the shared disk for shared data and that for the repository. When this command is executed, a repository is created in addition to the cluster being set up. For more information, see the chapter on database creation.
Example
# /opt/swstorage/bin/stgclset_vcs -k Primary -m /STGMGRDISK -n nodeMGR -s manager_service -i 10.10.10.10 -f mgr |
Note
For a Storage Management Server transaction to be performed, use the location that is specified when the Storage Management Server is installed.
For a Storage Server transaction, on the primary node, execute the following cluster setup command after blocking other users from accessing the shared disk for shared data:
Example
# /opt/swstorage/bin/stgclset_vcs -k Primary -m /STGAGTMNT -n nodeAGT -s agent_service |
Refer to "8.2.2 stgclset_vcs (Solaris edition VERITAS Cluster Server environment setup command)" for command details.
Check the setup object.
Information about the logical node specified by the command is displayed. After confirming the displayed information, press the Enter key.
For a Storage Management Server transaction:
# /opt/swstorage/bin/stgclset_vcs -k Primary -m /STGMGRDISK -n nodeMGR -s manager_service -i 10.10.10.10 -f mgr
AdvancedCopy Manager settings are as follows.
Cluster system : VERITAS Cluster Server
Node type : Primary
IP Address : 10.10.10.10
Mount point : /STGMGRDISK
Node name : nodemgr
Service : STGMGRSRV
Function : Management Server
Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] |
For a Storage Server transaction:
# /opt/swstorage/bin/stgclset_vcs -k Primary -m /STGAGTMNT -n nodeAGT -s agent_service
AdvancedCopy Manager settings are as follows.
Cluster system : VERITAS Cluster Server
Node type : Primary
Mount point : /STGAGTMNT
Node name : nodeAGT
Service : agent_service
Function : Server
Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] |
To interrupt cluster environmental setting processing, input "n". To continue processing, input "y", or press the Enter key.
Note
If the transaction is the Storage Management Server transaction, proceed to step 8.
If the transaction is the Storage Server transaction, proceed to step 13.
Start the creation of a common environment for Storage Management Server transactions.
The initial window for setting the common environment opens. Confirm the displayed information, enter "y", and press the Enter key.
+----------------------------------------------------------------+
| A common environment for the AdvancedCopy Manager |
| Storage Management Server will be created. |
| [Notes] |
| Prepare the following directories before starting processing.|
| ============================================================== |
| |
| 1) Directory for the DB file |
| 2) Directory for the RDB dictionary |
| 3) Directory for the RDB log file |
| 4) Directory for the DB space to store the repository data |
| |
+----------------------------------------------------------------+
Do you want to continue with processing? [y/n] ==> y |
For a Storage Management Server transaction, specify the DB device.
The window shown below opens. Enter the directory name for the DB file system according to the information in [Notes], and press the Enter key.
-----------------------< DB device setting >----------------------
Enter the directory name for the DB file.
[Notes]
Enter the absolute path name of the directory.
Enter ==> /ACMMnt/Vol202/DBFile |
A similar setting window opens for input of the directory names for the RDB dictionary, RDB log file, and DB space where repository data is stored. Enter a directory name for each item, and press the Enter key after each entry.
After setting up the directory name for DB space where repository data is stored, the setting window for inputting the size of repository data is opened. Enter the size of repository data, and press the Enter key.
For a Storage Management Server transaction, check the DB directory settings.
The four directory names and the size of repository data specified in step 9 are displayed. Confirm the displayed information, enter "y", and press the Enter key.
================================================================================
Directory name for the DB file ............................./ACMMntVol202/DBFile
Directory name for the RDB dictionary ....................../ACMMnt/Vol203/DBDic
Directory name for the RDB log file ......................../ACMMnt/Vol204/DBLog
Directory name for the DB space for saving repository data ..../ACMMnt/Vol205/DBSpa
Repository data Size .......................................65MB
================================================================================
Okay? [y/n] ==> y |
For a Storage Management Server transaction, confirm the continuation of processing.
After the window for confirming the continuation of processing opens, enter "y", and press the Enter key.
+--------------------------------------------------------------------+
| Creation of the AdvancedCopy Manager Storage management |
| server environment will start. |
| ================================================================== |
| |
| Once processing has started, system information is rewritten. |
| Make sure that the environment allows execution |
| before proceeding. |
| |
+--------------------------------------------------------------------+
Do you want to continue with processing? [y/n] ==> y |
For a Storage Management Server transaction, perform the repository access settings.
The window for setting repository access opens. Enter a user name and password, and press the Enter key.
Point
For security reasons it is recommended to use a general username and not the root user which has frequent password changes.
Enter the user name and password for accessing
the repository of AdvancedCopy Manager.
[Notes]
We recommend you to input a general user other than root.
Username : acmuser
Password :
Password(Re-enter) : |
Note
If user settings were entered as shown above, and the user is deleted or the password is changed from the operating system, perform the setup processing again. Refer to "User deletion or password change in repository access user settings" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide (Solaris)".
Finish the cluster setup command on the primary node.
The window indicating password registration and cluster setup command completion opens.
swstf8100 The cluster setup of the primary node has been completed. Next, create the cluster environment of the secondary node. # |
Dismount the shared disks on the primary node.
For a Storage Management Server transaction, dismount the shared disk for shared data and the one for the repository on the primary node.
For a Storage Server transaction, dismount the shared disk for shared data on the secondary node.
Mount the shared disks on the secondary node A.
For a Storage Management Server transaction, mount the shared disk for shared data and the one for the repository on the secondary node A.
For a Storage Server transaction, mount the shared disk for shared data on the secondary node A.
Execute the cluster setup command on the secondary node A.
For a Storage Management Server transaction, on the secondary node A, execute the cluster setup command shown below after blocking other users from accessing the shared disk for shared data and the one for the repository. When this command is executed, a repository is created in addition to the cluster being set up. For more information, see the chapter on database creation.
For a Storage Server transaction, on the secondary node A, execute the following cluster setup command after blocking other users from accessing the shared disk for shared data:
Example
# /opt/swstorage/bin/stgclset_vcs -k Secondary -m /STGMGRDISK |
Refer to "8.2.2 stgclset_vcs (Solaris edition VERITAS Cluster Server environment setup command)" for command details.
Note
For a Storage Management Server transaction to be performed, use the location that is specified when the Storage Management Server is installed.
Check the setup object.
Information about the logical node specified by the command is displayed. After confirming the displayed information, press the Enter key.
For a Storage Management Server transaction:
# /opt/swstorage/bin/stgclset_vcs -k Secondary -m /STGMGRDISK
AdvancedCopy Manager settings are as follows.
Cluster system : VERITAS Cluster Server
Node type : Secondary
IP Address : 10.10.10.10
Mount point : /STGMGRDISK
Node name : nodemgr
Service : STGMGRSRV
Function : Management Server
Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] |
For a Storage Server transaction:
# /opt/swstorage/bin/stgclset_vcs -k Secondary -m /STGAGTMNT
AdvancedCopy Manager settings are as follows.
Cluster system : VERITAS Cluster Server
Node type : Secondary
Mount point : /STGAGTMNT
Node name : nodeAGT
Service : agent_service
Function : Server
Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] |
To interrupt cluster environmental setting processing, input "n". To continue processing, input "y", or press the Enter key.
Note
If the transaction is a Storage Management Server transaction, proceed to step 18.
If the transaction is a Storage Server transaction, proceed to step 19.
Start the creation of a common environment for AdvancedCopy Manager management server transactions.
The initial window for setting the common environment opens. Confirm the displayed information, enter "y", and press the Enter key.
+--------------------------------------------------------------------+
| Creation of the AdvancedCopy Manager Storage management |
| server environment will start. |
| ================================================================== |
| |
| Once processing has started, system information is rewritten. |
| Make sure that the environment allows execution |
| before proceeding. |
| |
+--------------------------------------------------------------------+
Do you want to continue with processing? [y/n] ==> y |
Finish the cluster setup command on the secondary node A.
The window indicating cluster setup command completion opens.
swstf8101 The cluster setup of the secondary node has been completed. # |
Dismount the shared disks on the secondary node A.
For a Storage Management Server transaction, dismount the shared disk for shared data and the one for the repository on the secondary node A.
For a Storage Server transaction, dismount the shared disk for share data on the secondary node A.
Note
If the system is the 1:1 standby system, the Mutual standby system and the n:1 standby system, proceed to step 28.
If the system is Cascade topology and the Priority transfer, proceed to step 21.
Mount the shared disks on the secondary node B.
For a Storage Management Server transaction, mount the shared disk for shared data and that for the repository on the secondary node B.
For a Storage Server transaction, mount the shared disk for shared data on the secondary node B.
Note
When there are two or more secondary nodes B, Step 21 to Step 27 is processed for all the secondary nodes B.
Execute the cluster setup command on the secondary node B.
Execute the cluster setup command on the secondary node B on which the shared disk for shared data and the shared disk for the repository were mounted in step 21.
For a Storage Management Server transaction, on the secondary node B, execute the cluster setup command shown below after blocking other users from accessing the shared disk for shared data and the one for the repository. When this command is executed, a repository is created in addition to the cluster being set up. For more information, see the chapter on database creation.
For a Storage Server transaction, on the secondary node B, execute the following cluster setup command after blocking other users from accessing the shared disk for shared data:
Example
# /opt/swstorage/bin/stgclset_vcs -k Secondary -m /STGMGRDISK |
Refer to "8.2.2 stgclset_vcs (Solaris edition VERITAS Cluster Server environment setup command)" for command details.
Note
For a Storage Management Server transaction to be performed, use the location that is specified when the Storage Management Server is installed.
Check the setup object.
Information about the logical node specified by the command is displayed. After confirming the displayed information, press the Enter key.
For a Storage Management Server transaction:
# /opt/swstorage/bin/stgclset_vcs -k Secondary -m /STGMGRDISK
AdvancedCopy Manager settings are as follows.
Cluster system : VERITAS Cluster Server
Node type : Secondary
IP Address : 10.10.10.10
Mount point : /STGMGRDISK
Node name : nodemgr
Service : STGMGRSRV
Function : Management Server
Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] |
For a Storage Server transaction:
# /opt/swstorage/bin/stgclset_vcs -k Secondary -m /STGAGTMNT
AdvancedCopy Manager settings are as follows.
Cluster system : VERITAS Cluster Server
Node type : Secondary
Mount point : /STGAGTMNT
Node name : nodeAGT
Service : agent_service
Function : Server
Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] |
To interrupt cluster environmental setting processing, input "n". To continue processing, input "y", or press the Enter key.
Check the addition of a secondary node.
The window for confirming the addition of a secondary node is displayed. After confirmation of a cascade, "y" is inputted and the Enter key is pushed.
Secondary node is already setup in another node.
The number of secondary nodes : 1
Do you want to setup new secondary node? [default:n] y |
The number of secondary nodes already set up is outputted to "The number of secondary nodes."
Note
The default value is "n." "n" means cancellation of processing.
If the transaction is a Storage Management Server transaction, proceed to step 25.
If the transaction is a Storage Server transaction, proceed to step 26.
Start the creation of a common environment for AdvancedCopy Manager management server transactions.
After the window for confirming the continuation of processing opens, enter "y", and press the Enter key.
+--------------------------------------------------------------------+
| Creation of the AdvancedCopy Manager Storage management |
| server environment will start. |
| ================================================================== |
| |
| Once processing has started, system information is rewritten. |
| Make sure that the environment allows execution |
| before proceeding. |
| |
+--------------------------------------------------------------------+
Do you want to continue with processing? [y/n] ==> y |
Finish the cluster setup command on the secondary node B.
The window indicating cluster setup command completion opens.
swstf8101 The cluster setup of the secondary node has been completed. # |
Dismount the shared disks on the secondary node B.
For a Storage Management Server transaction, dismount the shared disk for shared data and that for the repository on the secondary node B.
For a Storage Server transaction, dismount the shared disk for share data on the secondary node B.
Note
When more secondary nodes B remain to be set up (ie Step 21 to Step 27 have not been performed in them as yet), perform from Step 21 in the node. When operation from Step 21 to Step 27 is completed by all secondary nodes B, go to Step 28.
Create and register a Service Group.
A service of AdvancedCopy Manager can be created and registered in a User Service Group.
Please add the following types as a resource of AdvancedCopy Manager.
Application
Specify a "/opt/FJSVswstf/cluster/clproc/vcsStart_Logical-Node-Name" to be StartProgram.
Specify a "/opt/FJSVswstf/cluster/clproc/vcsStop_Logical-Node-Name" to be StopProgram.
Specify a "/opt/FJSVswstf/cluster/clproc/vcsMoni_Logical-Node-Name" to be MonitorProgram.
MountPoint
For a Storage Management Server transaction, register the shared disk for share data, and the shared disk for the repository.
For a Storage Server transaction, register the shared disk for share data.
IP
Register the logic IP address for AdvancedCopy Manager. When using the logic IP address already used on business, it is not necessary to register newly.
The application should set up a dependency after MountPoint and IP to become on-line.
Refer to VERITAS Cluster Server User's Guide for information about a user service group and the creation/registration method of a resource.
The User Service Group by the command of VERITAS Cluster Server and the example of creation/registration of a resource are as follows.
In this example, User Service Group name is set to "STGMGRSRV", active system node name is set to "node1", standby system node name is set to "node2", and resource (ie, application) name is set to "AdvancedCopy_Manager_appl."
VCS config file is saved with another file-name. (Execute at all nodes.)
# mv /etc/VRTSvcs/conf/config/main.cf /etc/VRTSvcs/conf/config/main.cf.bk |
Place VCS into the read-write enabled state.
# haconf -makerw |
Define a list of systems used at occurrence of fail-over.
Note that when set up into the User Service Group, it is not necessary to set them up.
The following commands perform a check.
# hagrp -display STGMGRSRV -attribute SystemList # hagrp -display STGMGRSRV -attribute AutoStartList |
A User Service Group is newly created (it is unnecessary when already set up into the User Service Group). As the system priority sequence, the active node has priority over the standby node.
# hagrp -add STGMGRSRV # hagrp -modify STGMGRSRV SystemList node1 0 node2 1 # hagrp -modify STGMGRSRV AutoStartList node1 node2 |
Register applications.
A resource (an application) is registered into a User Service Group.
# hares -add AdvancedCopy_Manager_appl Application STGMGRSRV |
Place resources into the enabled state.
# hares -modify AdvancedCopy_Manager_appl Enabled 1 |
Specify a super-user (ie, root) who starts StartProgram, StopProgram, MonitorProgram.
# hares -modify AdvancedCopy_Manager_appl User root |
Specify a start application.
When a logical node name is nodemgr, the path of the application for starting becomes "/opt/FJSVswstf/cluster/clproc/vcsStart_nodemgr."
# hares -modify AdvancedCopy_Manager_appl StartProgram /opt/FJSVswstf/cluster/clproc/vcsStart_nodemgr |
Specify a stop application.
When a logical node name is nodemgr, the path of the application for a stop becomes "/opt/FJSVswstf/cluster/clproc/vcsStop_nodemgr."
# hares -modify AdvancedCopy_Manager_appl StopProgram /opt/FJSVswstf/cluster/clproc/vcsStop_nodemgr |
Specify a monitor application.
When a logical node name is nodemgr, the path of monitor application becomes "/opt/FJSVswstf/cluster/clproc/vcsMoni_nodemgr."
# hares -modify AdvancedCopy_Manager_appl MonitorProgram /opt/FJSVswstf/cluster/clproc/vcsMoni_nodemgr |
The mount information on the shared disk for share data is registered.
In this example, a resource (mount) name is set to "AdvancedCopy_Manager_mount", and the mount point of shared disk for share data is set to "/STGMGRDISK".
Register resource into User Service Group.
# hares -add AdvancedCopy_Manager_mount Mount STGMGRSRV |
Place the resource into the enabled state.
# hares -modify AdvancedCopy_Manager_mount Enabled 1 |
A mount pointer is set as a resource.
# hares -modify AdvancedCopy_Manager_mount MountPoint /STGMGRDISK |
Specify a block device to be mounted.
In this example, the block device of a shared disk is set to "/dev/dsk/c2t0d0s4".
# hares -modify AdvancedCopy_Manager_mount BlockDevice /dev/dsk/c2t0d0s4 |
Specify a file system type for the shared disk.
In this example, a file system type is set to vxfs.
# hares -modify AdvancedCopy_Manager_mount FSType vxfs |
For a Storage Management Server transaction, the mount information on the repository is registered. This operation is not required when the shared disk for share data is substituted for the shared disk for the repository.
In this example, all repository directories will be created on a single shared disk, and the resource (ie, mount) name for this shared disk will be "AdvancedCopy_Manager_DB". If multiple shared disks have been prepared for repository directories, perform the same operation on all shared disks.
Register resource in User Service Group.
# hares -add AdvancedCopy_Manager_DB Mount STGMGRSRV |
Place the resource into the enabled state.
# hares -modify AdvancedCopy_Manager_DB Enabled 1 |
The mount pointer of a resource is set up.
# hares -modify AdvancedCopy_Manager_DB MountPoint /ACMDB |
Specify a block device to be mounted.
In this example, the block device of a shared disk is set to "/dev/dsk/c2t0d1s4".
# hares -modify AdvancedCopy_Manager_DB BlockDevice /dev/dsk/ c2t0d1s4 |
Specify a file system type for the shared disk.
In this example, a file system type is set to "vxfs".
# hares -modify AdvancedCopy_Manager_DB FSType vxfs |
Register a logical address.
However, when it is already set up in the User Service Group, it is not necessary to set up this resource.
In this example, a resource (ie, an IP address) name is set to "sybase_ip".
A resource is registered into a User Service Group.
# hares -add sybase_ip IP STGMGRSRV |
Place the resource into the enabled state.
# hares -modify Sybase_ip Enabled 1 |
Specify a device.
In this example, a device is set to "hme0".
# hares -modify Sybase_ip Device hme0 |
Specify an address.
In this example, an IP address is set to "10.10.10.10".
# hares -modify sybase_ip Address "10.10.10.10" |
Specify the dependency of a resource.
# hares -link AdvancedCopy_Manager_appl AdvancedCopy_Manager_DB # hares -link AdvancedCopy_Manager_appl AdvancedCopy_Manager_mount # hares -link AdvancedCopy_Manager_appl sybase_ip |
Reflect the VCS setting and set VCS into the read-only mode.
# haconf -dump -makero |
Start the AdvancedCopy Manager and Transaction.
Start the new User Service Group or the User Service Group stopped in step 4.
Please refer to VERITAS Cluster Server User's Guide for the method of starting a User Service Group.
The example of starting the User Service Group by the command of VERITAS Cluster Server is as follows.
In this example, a User Service Group name is set to "STGMGRSRV", and an active system node name is set to "node1".
# hagrp -online STGMGRSRV -sys node1 |
Back up the environment.
To guard against the possibility of accidental deletion or corruption of data, back up the following environments.
Database
For a Storage Management Server transaction, refer to "Saving a database," in the "ETERNUS SF AdvancedCopy Manager Operations Guide (Solaris)" and back up the created database area.
Data on the shared disk for shared data
Use the OS command such as cp to back up the following directories on the shared disk for shared data:
Mountpoint-of-shared-disk-for-AdvancedCopy-Manager-shared-data/etc
Mountpoint-of-shared-disk-for-AdvancedCopy-Manager-shared-data/var
Create an environment for a Storage Management Server transaction and a Storage Server transaction.
Use the Web GUI of AdvancedCopy Manager to create an environment for a Storage Management Server transaction and a Storage Server transaction.
If using a Storage Server transaction function in a Storage Management Server transaction, create an environment for the Storage Server transaction.
Note
Create an environment for a Storage Management Server transaction and an environment for a Storage Server transaction by referring to the "ETERNUS SF AdvancedCopy Manager Operator's Guide (Solaris)."
