Top
ETERNUS SF Express V16.9 / Storage Cruiser V16.9 / AdvancedCopy Manager V16.9 Migration Guide
FUJITSU Storage

A.6 Restoring Management Information (for HP-UX, AIX)

Restore the management information which exists in the Managed Server.

Note

Caution about AdvancedCopy Manager's Agent in HP-UX Environments

AdvancedCopy Manager supports device names in both the legacy format and the new format. Refer to "Managing Device on AdvancedCopy Manager" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for HP-UX) for information on device names. Depending on the device format, perform the procedure below.

  • If using a different format device name before and after upgrade:

    Before upgrading, set the device format executing the stgxfwcmsetmode command, and then delete the definition for the backup management and replication management. After that, set the device format used after upgrading executing the stgxfwcmsetmode command, and then fetch the device information and redefine the backup management and replication management.
    Refer to "Configuration Management Commands" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for HP-UX) for information on setting the information collection mode.

    Refer to "Changing Device Configuration" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for HP-UX) for information on backup management and replication management.

  • If using the same format device name before and after upgrade:

    Even if using the same format device name as before upgrade, always set up the device format being used by executing the stgxfwcmsetmode command.
    Refer to "Configuration Management Commands" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for HP-UX) for information on setting the information collection mode.

If Backup Operation Has Been Done
  1. Restore the backup management list.

    Specify the directory saved in "A.3 Backing Up Management Information (for HP-UX, AIX)" and execute the following command.

    # /opt/FJSVswsts/bin/swstresrst saveDir

    See

    Refer to "Command References" in the ETERNUS SF AdvancedCopy Manager Operation Guide for this version for information on the command.

  2. Restore pre-processing and post-processing scripts.

    Note

    Do not restore pre-processing and post-processing scripts for backup management function by using copy command.

    The sample of pre-processing and post-processing scripts may be changed when upgrading a version. If you have customized pre-processing and post-processing scripts before the upgrade, re-customize it in reference to pre-processing and post-processing scripts which has been saved before the upgrade.

If Replication Operation Has Been Done
  1. Restore the replication management list.

    The replication management list is stored in the repository on the Management Server. Execute the following command.

    # /opt/FJSVswsrp/bin/swsrprecoverres -r

    See

    Refer to "Command References" in the ETERNUS SF AdvancedCopy Manager Operation Guide for this version for information on the command.

    Point

    If a server-to-server replication is performed, restore the replication management list in the associated server as well.

  2. Restore specification files.

    Restore the following files saved in "A.3 Backing Up Management Information (for HP-UX, AIX)" by executing the cp command:

    • Timeout value setting file for the concurrent suspend function

    For Non-clustered Systems

    File for Restoration

    Full Path Name for Restoration Destination

    Timeout value setting file for the concurrent suspend function

    /etc/opt/FJSVswsrp/data/DEFAULT/check.ini

    For Clustered Systems

    File for Restoration

    Full Path Name for Restoration Destination

    Timeout value setting file for the concurrent suspend function

    /etc/opt/FJSVswsrp/logicalNodeName/data/DEFAULT/check.ini

    Note

    Do not restore pre-processing and post-processing scripts for replication management function by using copy command.

    The sample of pre-processing and post-processing scripts may be changed when upgrading a version. If you have customized pre-processing and post-processing scripts before the upgrade, re-customize it in reference to pre-processing and post-processing scripts which has been saved before the upgrade.