Follow the procedure below to change the logical node name for a Management Server transaction.
Check the operational status of the Management Server transaction for which you wish to change the logical node name. If the transaction is stopped, start up the Management Server transaction.
Refer to the manual for the cluster software for information on how to start up the transaction.
Check to see if the Management Server transaction for which you wish to change the logical node name also serves as a Managed Server transaction for AdvancedCopy Manager. If it also serves as Managed Server transactions, proceed to step 3. If it does not, proceed to step 4.
Delete the environment for the Managed Server transaction.
If the backup management function is being used, delete the transaction volumes and backup volumes.
Refer to "Deleting a device" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for Solaris) or ETERNUS SF AdvancedCopy Manager Operation Guide (for Linux) for information on how to delete the environment.
If it is defined as a copy source or copy destination volume with the replication management function, delete the copy source/destination volume settings.
Refer to "Deleting a source volume or replica volume" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for Solaris) or ETERNUS SF AdvancedCopy Manager Operation Guide (for Linux) for information on how to delete the settings.
Back up the AdvancedCopy Manager data.
Back up the following data.
Repository Data
Refer to "Database backup" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for Solaris) or ETERNUS SF AdvancedCopy Manager Operation Guide (for Linux) for information on how to back up the data.
If the Management Server transaction also serves as Managed Server transaction, back up the following data as well.
Backup/Restore Pre- and Post-Processing Scripts
Replication Pre- and Post-Processing Scripts
If the server is a management information package backup server for AdvancedCopy Manager, back up the following data as well.
Policy File for Package Backup of Management Information
Refer to "Preliminaries" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for Solaris) or ETERNUS SF AdvancedCopy Manager Operation Guide (for Linux) for the file path of the policy file.
Back up the environment settings data for the AdvancedCopy Manager CCM.
Refer to "Backing up environment settings files" in the ETERNUS SF Operation Guide for Copy Control Module.
Delete the cluster environment for the Management Server transaction for which you wish to change the logical node name.
Refer to "Chapter 13 Deletion of Cluster Environment for Management Server Transactions" for information on how to delete the environment.
Specify the new logical node name and create the cluster environment for the Management Server transaction.
Refer to "Chapter 5 Customization for Management Server Transaction" for information on how to create the cluster environment.
Note
Input the new logical volume name for the input item for the logical node name in the AdvancedCopy Manager's cluster setup command.
Start up the created Management Server transaction.
Refer to the manual for the cluster software for information on how to start up the transaction.
Restore the AdvancedCopy Manager data.
Restore the following data.
Restore the repository data.
Refer to "Database restoration" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for Solaris) or ETERNUS SF AdvancedCopy Manager Operation Guide (for Linux) for information on how to restore the data.
If, in the Management Server transaction, it also serves as a Managed Server transaction for AdvancedCopy Manager, restore the following data as well.
Pre- and Post-Processing Scripts for Backup Management and Replication Management
If the server is a management information package backup server for AdvancedCopy Manager, restore the following data as well.
Policy File for Package Backup of Management Information
Refer to "Preliminaries" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for Solaris) or ETERNUS SF AdvancedCopy Manager Operation Guide (for Linux) for the file path of the policy file.
Restore the environment settings data for the AdvancedCopy Manager CCM.
Refer to "Restoring environment settings files" in the ETERNUS SF Operation Guide for Copy Control Module for information on how to restore the data.
Change the server name.
Refer to "Changing the server name of Management Server transaction or Managed Server transaction" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for Solaris) or ETERNUS SF AdvancedCopy Manager Operation Guide (for Linux) for information on how to change the server name.
If using the backup management function or replication management function, rebuild the environments for the various management functions.
If using the backup management function, perform the procedures starting from the section "Configuring the environment for a backup operation server" and onwards in the ETERNUS SF AdvancedCopy Manager Operation Guide (for Solaris) or ETERNUS SF AdvancedCopy Manager Operation Guide (for Linux).
If using the replication management function, perform the procedures starting from the section "Configuring the source volume and replica volume" and onwards in the ETERNUS SF AdvancedCopy Manager Operation Guide (for Solaris) or ETERNUS SF AdvancedCopy Manager Operation Guide (for Linux).
To execute the package backup of management information for AdvancedCopy Manager, register it as a management information package backup server.
Refer to "stgmgrinfoset (Management information package backup server registration/deletion command)" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for Solaris) or ETERNUS SF AdvancedCopy Manager Operation Guide (for Linux) for information on how to perform registration.
