This section describes how to make a change to the operational configuration in cluster operation.
Change the IP address of a Managed Server transaction by performing the following steps:
If replication management function was used at the target Managed Server transaction to define it as a copy source or copy destination volume, delete the copy source or copy destination volume settings by referring to "6.6.2 Deleting a source volume or replica volume".
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.
On the Management Server that manages the Managed Server transactions, create a server information change instruction file, and then execute stgxfwcmmodsrv (Server information change command) with the -f option specified to change the IP address.
If the replication management function is used, reconstruct the replication management environment (perform the "6.4.5 Configuring the source volume and replica volume" task and subsequent tasks).
Change the port number of a Managed Server transaction by performing the following steps:
If replication management function was used at the target Managed Server transaction to define it as a copy source or copy destination volume, delete the copy source or copy destination volume settings by referring to "6.6.2 Deleting a source volume or replica volume".
Stop the target Managed 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 Managed Server transaction.
For details on how to start it, refer to the relevant cluster software manual.
On the Management Server that manages the target Managed Server transactions, create a server information change instruction file, and then execute stgxfwcmmodsrv (Server information change command) with the -f option specified to change the port number.
If the replication management function is used, reconstruct the replication management environment (perform the "6.4.5 Configuring the source volume and replica volume" task and subsequent tasks).
Change the server name of a Managed Server transaction by performing the steps below.
If replication management function was used by the target Managed Server transaction to define it as a copy source or copy destination volume, delete the copy source or copy destination volume settings by referring to "6.6.2 Deleting a source volume or replica volume".
On the Management Server that manages the Managed Server transactions, create a server information change instruction file, and then execute stgxfwcmmodsrv (Server information change command) with the -f option specified to change the server name.
If the replication management function is used, reconstruct the replication management environment (perform the "6.4.5 Configuring the source volume and replica volume" task and subsequent tasks).
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 a 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 a 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 "7.1.2.1 Preliminaries".
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 delete, refer to "Deletion of Cluster Environment for Managed Server Transactions" in the "ETERNUS SF Cluster Environment Setup Guide".
Note
Do not perform the following step in the "ETERNUS SF Cluster Environment Setup Guide".
Step 1 described in "Deletion Procedure" of "Deleting for AIX version High Availability Cluster Multi-Processing"
Step 1 described in "Deletion Procedure" of "Deleting for AIX version VERITAS Cluster Server"
Create the cluster environment of the target transaction.
For details on how to create, refer to "Customization of Managed Server transactions" in the "ETERNUS SF Cluster Environment Setup Guide".
Note
For the -n option of the cluster setup command, specify the name of the new logical node.
Do not perform the following step in the "ETERNUS SF Cluster Environment Setup Guide".
Step 24 in "Customization Procedure" on "Customization for AIX version High Availability Cluster Multi-Processing"
Step 18 in "Customization Procedure" on "Customization for AIX version VERITAS Cluster Server"
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 "7.1.2.1 Preliminaries".
Change the server name.
Perform the procedure described in "7.5.7.3 Changing the server name of 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 the environment for a backup operation server" task and subsequent tasks. For replication management, perform the "6.4.5 Configuring the source volume and replica volume" task and subsequent tasks.)
For a "package-backup-of-the-management-information execution server" of AdvancedCopy Manager, execute stgmgrinfoset (Management information package backup server registration/deletion 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 /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 "7.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 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 "7.1.2.1 Preliminaries".
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 "Deletion of Cluster Environment for Managed Server Transactions" in the "ETERNUS SF Cluster Environment Setup Guide".
Note
Do not perform the following step of "Deletion of Cluster Environment for Managed Server Transactions" in the "ETERNUS SF Cluster Environment Setup Guide".
Step 1 described in "Deletion Procedure" of "Deleting for AIX version High Availability Cluster Multi-Processing"
Step 1 described in "Deletion Procedure" of "Deleting for AIX version VERITAS Cluster Server"
On the clustered 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 "Customization of Managed Server transaction" in the "ETERNUS SF Cluster Environment Setup Guide".
Note
Do not perform the following step in the "ETERNUS SF Cluster Environment Setup Guide".
Step 24 in "Customization Procedure" on "Customization for AIX version High Availability Cluster Multi-Processing"
Step 18 in "Customization Procedure" on "Customization for AIX version VERITAS Cluster Server"
Do not change any information other than the transaction name 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 following AdvancedCopy Manager 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 "7.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 management.
When using the replication management function, restore the environment by using swsrprecoverres (Resource adjustment 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 "7.1.2.1 Preliminaries".
For a "package-backup-of-the-management-information execution server" of AdvancedCopy Manager, execute stgmgrinfoset (Management information package backup server registration/deletion 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 /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 "7.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 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 "7.1.2.1 Preliminaries".
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 "Deletion of Cluster Environment for Managed Server Transactions" in the "ETERNUS SF Cluster Environment Setup Guide".
Note
Do not perform the following step of "Deletion of Cluster Environment for Managed Server Transactions" in the "ETERNUS SF Cluster Environment Setup Guide".
Step 1 described in "Deletion Procedure" of "Deleting for AIX version High Availability Cluster Multi-Processing"
Step 1 described in "Deletion Procedure" of "Deleting for AIX version VERITAS Cluster Server"
Create the cluster environment of the target transaction.
For details about how to do this, refer to "Customization of Managed Server transactions" in the "ETERNUS SF Cluster Environment Setup Guide".
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 clustered system.
Do not perform the following step in the "ETERNUS SF Cluster Environment Setup Guide".
Step 24 in "Customization Procedure" on "Customization for AIX version High Availability Cluster Multi-Processing"
Step 18 in "Customization Procedure" on "Customization for AIX version VERITAS Cluster Server"
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 /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 "7.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 management.
When using the replication management function, restore the environment by using swsrprecoverres (Resource adjustment 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 "7.1.2.1 Preliminaries".
For a "package-backup-of-the-management-information execution server" of AdvancedCopy Manager, execute stgmgrinfoset (Management information package backup server registration/deletion command) to register as its server.
