This section describes how to make a change to the operational configuration in cluster operation.
Change the IP address of a Storage Server transaction by performing the following steps:
Check if the target Storage Management Server transaction is also used for Storage Server transactions.
If it is also used for Storage Server transactions and replication management functions were used to define it as a copy source or copy destination volume, delete the copy source or copy destination volume settings.
Refer to "7.6.2 Deleting a source volume or replica volume for the method for deleting the copy source or copy destination volume settings.
Stop the Storage Server transaction.
For details on how to stop it, refer to the relevant cluster software manual.
Change the IP address resource.
For details on how to change an IP address resource, refer to the relevant cluster software manual.
Start the Storage Server transaction.
For details on how to start it up, refer to the relevant cluster software manual.
On the Storage Management Server that manages the Storage Server transactions, create a server information change instruction file, then execute the server information change command with the -f option specified to change the IP address. Refer to "stgxfwcmmodsrv (Server information change command)" relevant to the OS running the Storage Management Server for details of the server information change command.
If the replication management functions are used, reconstruct the replication management environment (perform the "7.4.5 Configuring the source volume and replica volume" task and subsequent tasks).
Note
The IP address information displayed by the cluster unsetup command that is executed to delete the cluster environment of the Storage Server transaction is not the IP address that has been newly specified, but is the IP address specified by the cluster setup command.
Change the port number of a Storage Server transaction by performing the following steps:
If replication management functions were used to define it as a copy source or copy destination volume, delete the copy source or copy destination volume settings.
Refer to "7.6.2 Deleting a source volume or replica volume for the method for deleting the copy source or copy destination volume settings.
Stop the target Storage Server transaction.
For details on how to stop it, refer to the relevant cluster software manual.
On the primary node and secondary node, change the port number of the transaction-intended communication daemon (stgxfws_<logical node name>) specified in /etc/services.
Start the target Storage Server transaction.
For details on how to start it, refer to the relevant cluster software manual.
Create a server information change instruction file on the Storage Management Server that manages the Storage Server transactions, then execute the server information change command with the "-f" option specified to change the port number. Refer to "stgxfwcmmodsrv (Server information change command)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" relevant to the OS running the Storage Management Server for details of the server information change command.
If the replication management functions are used, reconstruct the replication management environment (perform the "7.4.5 Configuring the source volume and replica volume task and subsequent tasks).
Change the server name of a Storage Server transaction by performing the steps below.
If replication management functions were used by the target Storage Management Server or Storage Server to define it as a copy source or copy destination volume, delete the copy source or copy destination volume settings.
Refer to "7.6.2 Deleting a source volume or replica volume for the method for deleting the copy source or copy destination volume settings.
Create a server information change instruction file on the Storage Management Server that manages the Storage Server transactions.
Execute the server information change command with the "-f" option specified (specify the created file) to change the server name. Refer to "stgxfwcmmodsrv (Server information change command)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" relevant to the OS running the Storage Management Server for details of the server information change command.
If the replication management functions are used, reconstruct the replication management environment (perform the "7.4.5 Configuring the source volume and replica volume" task and subsequent tasks).
Change the logical node name of a Storage Server transaction by performing the following steps:
If the transaction is not operating, start the Storage Server transaction.
For details on how to start it up, refer to the relevant cluster software manual.
Delete the configuration of the Storage Server transaction.
When using the backup management function, delete the transaction volume and backup volume. For details on how to do this, refer to "4.6.2 Deleting a device".
When it is defined as a source or replica volume by using the replication control function, delete the source/replica volume configuration. For details on how to perform this, refer to "7.6.2 Deleting a source volume or replica volume".
Save the data.
The Storage Server transaction, save the following data:
Pre-processing/post-processing scripts
Save the pre-processing and post-processing scripts for backup management and replication control.
For the execution server of the package backup of the management information of AdvancedCopy Manager, save the following data:
Policy file for package backup of the management information
For details about the policy file path, refer to "8.1.2.1 Preliminaries".
For a Storage Server transaction, delete /etc/opt/swstorage/logical-node-name/swnode.ini on the node operating the transaction.
Delete the cluster environment of the target transaction.
For details about how to do this, refer to "Deleting a Storage Management Server transaction or Storage Server transaction" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Note
Do not perform Step 1 (deleting the node) described in "Detailed steps for deletion" in "Deletion on MC/ServiceGuard for HP-UX" or "Deletion on VERITAS Cluster Server for HP-UX" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Create the cluster environment of the target transaction.
For details on how to do this, refer to "Customizing a Storage Management Server transaction or Storage Server transaction" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Note
For the -n option of the cluster setup command, specify the name of the new logical node.
Do not perform the steps described in "Creating a Storage Management Server transaction or Storage Server transaction environment" in "Detailed steps for customization" on creating a cluster environment
(particularly Step 25 in "Details of the steps for customization" on "MC/ServiceGuard for HP-UX" or Step 18 in "Details of the steps for customization" on VERITAS Cluster Server for HP-UX).
Start the target transaction.
For details on how to start it up, refer to the relevant cluster software manual.
Restore the AdvancedCopy Manager data.
In the Storage Server transaction, restore the following data:
Pre-processing/post-processing scripts
Restore the pre-processing and post-processing scripts for backup management and replication control.
For a package-backup-of-the-management-information execution server of AdvancedCopy Manager, restore the following data:
Policy file for package backup of the management information
For details about the policy file path, refer to "8.1.2.1 Preliminaries".
Change the server name.
Perform the procedure described in "8.5.8.3 Changing the server name of a Storage Server transaction".
To use the backup management or replication control function, rebuild the backup management or replication control environment. (For backup management, perform the "Display backup management screen" task and subsequent tasks. For replication control, perform the "Setting copy source volume and copy destination volume" task and subsequent tasks.)
For the "package backup of the management information" execution server of AdvancedCopy Manager, execute the "package backup of the management information" server registration/deletion command to register the server.
Change the name of an AdvancedCopy Manager transaction by performing the following steps:
If the transaction is not operating, start the Storage Server transaction.
For details about how to start it up, refer to the relevant cluster software manual.
Save the AdvancedCopy Manager data.
In the Storage Server transaction, save the following data:
AdvancedCopy Manager management file
On the node operating the transaction, save /etc/opt/swstorage/logical-node-name/swnode.ini.
Backup management list
Make a backup of the backup management list.
For details about how to do this, refer to "8.1.1.1.1 Backing up a backup management list".
Pre-processing/post-processing scripts
Save the pre-processing and post-processing scripts for backup management and replication control.
For the execution server of the package backup of the management information of AdvancedCopy Manager, save the following data:
Policy file for package backup of the management information
For details about the policy file path, refer to "8.1.2.1 Preliminaries".
For a Storage Server transaction, delete /etc/opt/swstorage/logical-node-name/swnode.ini on the node operating the transaction.
Delete the cluster environment of the target transaction.
For details on how to do this, refer to "Deleting a Storage Management Server transaction or Storage Server transaction" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Note
Do not perform Step 1 (deleting the node) described in "Detailed steps for deletion" in "Deletion on MC/ServiceGuard for HP-UX" or "Deletion on VERITAS Cluster Server for HP-UX" in the ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment.
On the cluster system, change the cluster package name.
For details on how to do this, refer to the relevant cluster software manual.
Create the cluster environment of the target transaction.
For details on how to do this, refer to "Customizing a Storage Management Server transaction or Storage Server transaction" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Note
Do not perform the steps described in "Creating a Storage Management Server transaction or Storage Server transaction environment" in "Detailed steps for customization" on creating a cluster environment
(particularly Step 25 in "Details of the steps for customization" on MC/ServiceGuard for HP-UX or Step 18 in "Details of the steps for customization" on VERITAS Cluster Server for HP-UX)
Do not change any information other than the name of a transaction by using the cluster setup command.
Start the target transaction.
For details on how to start it up, refer to the relevant cluster software manual.
Restore the AdvancedCopy Manager data.
In the Storage Server transaction, restore the following data:
AdvancedCopy Manager management file
On the node operating the transaction, restore /etc/opt/swstorage/logical-node-name/swnode.ini.
Backup management list
Restore the backup management list.
For details about how to do this, refer to "8.1.1.1.2 Restoring a backup management list".
Pre-processing/post-processing scripts
Restore the pre-processing and post-processing scripts for backup management and replication control.
When using the replication control function, restore the environment by using swsrprecoverres (Resource adjustment command).
Specify the "-r" option for the resource adjustment command. For details about this, refer to "swsrprecoverres (Resource adjustment command)".
For a package-backup-of-the-management-information execution server of AdvancedCopy Manager, restore the following data:
Policy file for package backup of the management information
For details about the policy file path, refer to "8.1.2.1 Preliminaries".
For the "package backup of the management information" execution server of AdvancedCopy Manager, execute the "package backup of the management information" server registration/deletion command to register the server.
Change a shared disk that is used for AdvancedCopy Manager shared data (e.g., name of a mount point of a physical disk or shared disk) by performing the following steps:
Check whether the target Storage Server transaction is operating.
If the transaction is not operating, start the Storage Server transaction.
For details about how to start it up, refer to the relevant cluster software manual.
Save the AdvancedCopy Manager data.
In the Storage Server transaction, save the following data:
AdvancedCopy Manager management file
On the node operating the transaction, save /etc/opt/swstorage/logical-node-name/swnode.ini.
Backup management list
Make a backup of the backup management list.
For details about how to do this, refer to "8.1.1.1.1 Backing up a backup management list".
Pre-processing/post-processing scripts
Save the pre-processing and post-processing scripts for backup management and replication control.
For the execution server of the package backup of the management information of AdvancedCopy Manager, save the following data:
Policy file for package backup of the management information
For details about the policy file path, refer to "8.1.2.1 Preliminaries".
For a Storage Server transaction, delete /etc/opt/swstorage/logical-node-name/swnode.ini on the node operating the transaction.
Delete the cluster environment of the target transaction.
For details about how to do this, refer to "Deleting a Storage Management Server transaction or Storage Server transaction" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Note
Do not perform Step 1 (deleting the node) described in "Detailed steps for deletion" in "Deletion on MC/ServiceGuard for HP-UX" or "Deletion on VERITAS Cluster Server for HP-UX" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Create the cluster environment of the target transaction.
For details about how to do this, refer to "Customizing a Storage Management Server transaction or Storage Server transaction" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Note
To change the name of a mount point, specify the new mount point name in the -m option of the cluster setup command.
To change a physical disk, specify the new physical disk when you mount it.
Change the configuration of a shared disk in the cluster system.
Do not perform the steps described in "Creating a Storage Management Server transaction or Storage Server transaction environment" in "Detailed steps for customization" on creating a cluster environment
(particularly Step 25 in "Details of the steps for customization" on "MC/ServiceGuard for HP-UX" or Step 18 in "Details of the steps for customization" on "VERITAS Cluster Server for HP-UX").
Start the target transaction.
For details about how to start it up, refer to the relevant cluster software manual.
Restore the AdvancedCopy Manager data.
In the Storage Server transaction, restore the following data:
AdvancedCopy Manager management file
On the node operating the transaction, restore /etc/opt/swstorage/logical-node-name/swnode.ini.
Backup management list
Restore the backup management list.
For details about how to restore do this, refer to "8.1.1.1.2 Restoring a backup management list".
Pre-processing/post-processing scripts
Restore the pre-processing and post-processing scripts for backup management and replication control.
When using the replication control function, restore the environment by using swsrprecoverres (Resource adjustment command). Specify the "-r" option for the resource adjustment command.
For a package-backup-of-the-management-information execution server of AdvancedCopy Manager, restore the following data:
Policy file for package backup of the management information
For details about the policy file path, refer to "8.1.2.1 Preliminaries".
For the "package backup of the management information" execution server of AdvancedCopy Manager, execute the "package backup of the management information" server registration/deletion command to register the server.
