Top
ETERNUS SF Storage Cruiser V16.9.1 / AdvancedCopy Manager V16.9.1 Cluster Environment Setup Guide
FUJITSU Storage

12.2.4 Changing Logical Node Name

Follow the procedure below to change the logical node name for a Management Server transaction.

  1. 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 your cluster software manuals for information on how to start up the transaction.

  2. 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, go to step 3. If it does not, go to step 4.

  3. Delete the environment for the Managed Server transaction.

    If the AdvancedCopy Manager backup management function is being used, delete the transaction volumes and backup volumes.
    Refer to "Deleting Device" in the AdvancedCopy Manager Operation Guide (for Solaris or Linux) for information on how to delete the environment.

    If you have defined a copy source or copy destination volume with the AdvancedCopy Manager replication management function, delete the copy source/destination volume settings.
    Refer to "Deleting Source Volume or Replica Volume" in the AdvancedCopy Manager Operation Guide (for Solaris or Linux) for information on how to delete the settings.

  4. Back up the AdvancedCopy Manager data.

    Back up the following data.

    • Repository Data
      Refer to "Backup of Common Control and AdvancedCopy Manager Repository" in the AdvancedCopy Manager Operation Guide (for Solaris or 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 AdvancedCopy Manager Operation Guide (for Solaris or Linux) for the file path of the policy file.

  5. Back up the environment setting data for the AdvancedCopy Manager CCM.
    Refer to "Backing Up Environment Settings Files" in the AdvancedCopy Manager Operation Guide for Copy Control Module for details.

  6. 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.

  7. 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.

  8. Start up the created Management Server transaction.
    Refer to your cluster software manuals for information on how to start up the transaction.

  9. Restore the AdvancedCopy Manager data.

    Restore the following data.

    • Restore the repository data.
      Refer to "Restore of Common Control and AdvancedCopy Manager Repository" in the AdvancedCopy Manager Operation Guide (for Solaris or 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 AdvancedCopy Manager Operation Guide (for Solaris or Linux) for the file path of the policy file.

  10. Restore the environment setting data for the AdvancedCopy Manager CCM.
    Refer to "Restoring Environment Settings Files" in the AdvancedCopy Manager Operation Guide for Copy Control Module for information on how to restore the data.

  11. Change the server name.
    Refer to "Changing Server Name of Management Server Transaction or Managed Server Transaction" in the AdvancedCopy Manager Operation Guide (for Solaris or Linux) for information on how to change the server name.

  12. If using the backup management function or replication management function, rebuild the environments for the various management functions.

    If using the AdvancedCopy Manager backup management function, perform the procedures starting from the section "Configuring Environment for Backup Operation Server" and onwards in the AdvancedCopy Manager Operation Guide (for Solaris or Linux).
    If using the AdvancedCopy Manager replication management function, perform the procedures starting from the section "Configuring Source Volume and Replica Volume" and onwards in the AdvancedCopy Manager Operation Guide (for Solaris or Linux).

  13. 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 AdvancedCopy Manager Operation Guide (for Solaris or Linux) for information on how to perform registration.