This section describes how to make a change to the operational configuration in cluster operation.
Refer to "Changing IP Address for Management Server Transaction" in "Changing Operation Environment (for Solaris/Linux)" in the Cluster Environment Setup Guide.
Change the IP address of a Managed Server transaction by performing the following steps:
Stop the Managed 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 Managed Server transaction.
For details on how to start it up, refer to the relevant cluster software manual.
When AdvancedCopy Manager is being operated using Web Console, refer to "Change Server Information" in the Web Console Guide and change the IP address information. When AdvancedCopy Manager is being operated using only Command Line Interface, after creating a server information change instruction file with the Management Server, execute the stgxfwcmmodsrv command with the -f option and change the IP address. When using the replication management function, execute the swsrprecoverres command with the -r option and the -h option on the Management Server. Specify the server name of the Managed Server running the replication operation with the -h option.
For changing the port number of Management Server transaction, refer to "Changing Port Number of Management Server Transactions" in "Changing Operation Environment (for Solaris/Linux)" in the Cluster Environment Setup Guide.
Change the port number of a Managed Server transaction by performing the following steps:
Stop the Management Server transaction or Managed Server transaction.
For details on how to stop it, refer to the relevant cluster software manual.
On the primary node and secondary node of the target Managed Server transaction, change the port number of the AdvancedCopy Manager communication daemon (stgxfws_logicalNodeName) specified in /etc/services.
Start the targeted Managed Server transaction.
For details on how to start it up, refer to the relevant cluster software manual.
Create a server information change instruction file at the Management Server that manages the Managed Server. Then, execute the stgxfwcmmodsrv command with the -f option specified to change the port number. When using the replication management function, execute the swsrprecoverres command with the -r option and the -h option on the Management Server. Specify the server name of the Managed Server running the replication operation with the -h option.
Refer to "Reload Server Configuration Information" in the Web Console Guide and reload the configuration information of the Management Server or Managed Server.
For changing the server name of Management Server transaction, refer to "Changing Server Name of Management Server Transaction" in "Changing Operation Environment (for Solaris/Linux)" in the Cluster Environment Setup Guide.
Change the server name of a Managed Server transaction by performing the steps below.
Create a server information change instruction file at the Management Server that manages the Managed Server. Then, execute the stgxfwcmmodsrv command with the -f option specified to change the port number. When using the replication management function, execute the swsrprecoverres command with the -r option and the -h option on the Management Server. Specify the server name of the Managed Server running the replication operation with the -h option.
Refer to "Reload Server Configuration Information" in the Web Console Guide and reload the configuration information of the Management Server or Managed Server.
For changing the logical node name of Management Server transaction, refer to "Changing Logical Node Name" in "Changing Operation Environment (for Solaris/Linux)" in the Cluster Environment Setup Guide.
Change the logical node name of a Managed Server transaction by performing the following steps:
Check whether the target Managed Server transaction is operating.
If the transaction is not operating, start the Managed Server transaction.
For details on how to start it up, refer to the relevant cluster software manual.
Delete the configuration of the Managed Server transaction.
When using the backup management function, delete the transaction volume and backup volume by referring to "3.6.2 Deleting Device".
When it is defined as a copy source or copy destination volume by using the replication management function, delete the copy source or copy destination volume settings by referring to "6.6.2 Deleting Source Volume or Replica Volume".
Save the following AdvancedCopy Manager data.
Pre-processing/post-processing scripts
Save the pre-processing and post-processing scripts for backup management and replication management.
For a "package-backup-of-the-management-information execution server" 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".
Delete the "/etc/opt/swstorage/logicalNodeName/swnode.ini" file on the node operating the transaction.
Delete the cluster environment of the target transaction.
For details about how to delete, refer to "Deletion for Solaris/Linux/HP-UX version Clustered Systems" in the Cluster Environment Setup Guide.
Note
Do not perform the following step in "Deletion for Solaris/Linux/HP-UX version Clustered Systems" in the Cluster Environment Setup Guide.
Step 1 described in "Deletion Procedure"
Create the cluster environment of the target transaction.
For details on how to create, refer to "Customization for Solaris/Linux/HP-UX version Clustered Systems" in the Cluster Environment Setup Guide.
Note
When you perform the cluster set up, specify the name of the new logical node.
Start the target transaction.
For details on how to start it up, refer to the relevant cluster software manual.
Restore the following AdvancedCopy Manager data.
Pre-processing/post-processing scripts
Restore the pre-processing and post-processing scripts for backup management and replication management.
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.6.4 Changing Server Name of Management Server Transaction or Managed Server Transaction".
To use the backup management or replication management function, rebuild the backup management or replication management environment. (For backup management, perform the "3.4.5 Configuring Environment for Backup Operation Server" task and subsequent tasks. For replication management, perform the "6.4.5 Configuring Source Volume and Replica Volume" task and subsequent tasks.)
For a "package-backup-of-the-management-information execution server" of AdvancedCopy Manager, execute the stgmgrinfoset command to register as its server.
Change the name of a Managed Server transaction by performing the following steps:
Check whether the target Managed Server transaction is operating.
If the transaction is not operating, start the Managed Server transaction.
For details about how to start it up, refer to the relevant cluster software manual.
Save the following AdvancedCopy Manager data.
AdvancedCopy Manager management file
On the node operating the transaction, save the "/etc/opt/swstorage/logicalNodeName/swnode.ini" file.
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 Backup Management List".
Pre-processing/post-processing scripts
Save the pre-processing and post-processing scripts for backup management and replication management.
For a "package-backup-of-the-management-information execution server" 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".
Delete the "/etc/opt/swstorage/logicalNodeName/swnode.ini" file on the node operating the transaction.
Delete the cluster environment of the target transaction.
For details on how to do this, refer to "Deletion for Solaris/Linux/HP-UX version Clustered Systems" in the Cluster Environment Setup Guide.
Note
Do not perform the following step of "Deletion for Solaris/Linux/HP-UX version Clustered Systems" in the Cluster Environment Setup Guide.
Step 1 described in "Deletion Procedure"
On the clustered system, change the name of cluster transaction.
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 "Customization for Solaris/Linux/HP-UX version Clustered Systems" in the Cluster Environment Setup Guide.
Note
When you perform the cluster set up, do not change any information other than the transaction name.
Start the target transaction.
For details on how to start it up, refer to the relevant cluster software manual.
Restore the following AdvancedCopy Manager data.
AdvancedCopy Manager management file
On the node operating the transaction, restore the "/etc/opt/swstorage/logicalNodeName/swnode.ini" file.
Backup management list
Restore the backup management list.
For details about how to do this, refer to "8.1.1.1.2 Restoring Backup Management List".
Pre-processing/post-processing scripts
Restore the pre-processing and post-processing scripts for backup management and replication management.
When using the replication management function, restore the environment by using the swsrprecoverres command with the -r option.
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 a "package-backup-of-the-management-information execution server" of AdvancedCopy Manager, execute the stgmgrinfoset command to register as its server.
Change a shared disk that is used for Managed Server transaction by performing the following steps:
Check whether the target Managed Server transaction is operating.
If the transaction is not operating, start the Managed Server transaction.
For details about how to start it up, refer to the relevant cluster software manual.
Save the following AdvancedCopy Manager data.
AdvancedCopy Manager management file
On the node operating the transaction, save the "/etc/opt/swstorage/logicalNodeName/swnode.ini" file.
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 Backup Management List".
Pre-processing/post-processing scripts
Save the pre-processing and post-processing scripts for backup management and replication management.
For a "package-backup-of-the-management-information execution server" 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".
Delete the "/etc/opt/swstorage/logicalNodeName/swnode.ini" file on the node operating the transaction.
Delete the cluster environment of the target transaction.
For details about how to do this, refer to "Deletion for Solaris/Linux/HP-UX version Clustered Systems" in the Cluster Environment Setup Guide.
Note
Do not perform the following step of "Deletion for Solaris/Linux/HP-UX version Clustered Systems" in the Cluster Environment Setup Guide.
Step 1 described in "Deletion Procedure"
Create the cluster environment of the target transaction.
For details about how to do this, refer to "Customization for Solaris/Linux/HP-UX version Clustered Systems" in the Cluster Environment Setup Guide.
Note
To change the name of a mount point, specify the new mount point name when you perform the cluster set up.
To change a physical disk, specify the new physical disk when you mount it.
Change the configuration of a shared disk in the clustered system.
Start the target transaction.
For details about how to start it up, refer to the relevant cluster software manual.
Restore the following AdvancedCopy Manager data.
AdvancedCopy Manager management file
On the node operating the transaction, restore the "/etc/opt/swstorage/logicalNodeName/swnode.ini" file.
Backup management list
Restore the backup management list.
For details about how to restore do this, refer to "8.1.1.1.2 Restoring Backup Management List".
Pre-processing/post-processing scripts
Restore the pre-processing and post-processing scripts for backup management and replication management.
When using the replication management function, restore the environment by using the swsrprecoverres command with the -r option.
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 a "package-backup-of-the-management-information execution server" of AdvancedCopy Manager, execute the stgmgrinfoset command to register as its server.
