Top
ETERNUS SF Storage Cruiser V16.1 Operation Guide
FUJITSU Storage

11.1.1 Maintenance of Manager

11.1.1.1 Collecting Data for Troubleshooting

If any problem occurs in a system that uses this software, collect troubleshooting information according to "B.1 Collecting Troubleshooting Information".

11.1.1.2 Backup of Manager

Back up (save) the environment for the Storage Cruiser's manager if an error has occurred in the Management Server.

All of the tasks for backup of Manager are performed in the Management Server.

11.1.1.2.1 Backup of Solaris OS Manager

Follow the procedure below to save the environment for the Storage Cruiser's manager.

Information

Notation in Procedure:

  • "$BAK_DIR" signifies the backup destination directory.

  1. Stop the ETERNUS SF Manager Tomcat Service.

    Execute the following shell script to stop the service.

    /opt/FJSVesfcm/bin/stop-webservice.sh
  2. Create the backup data.

    Create the directory for the backup data.

    mkdir -p $BAK_DIR/Common

    Execute the following command to create the backup data. Specify the default value 15432 to <port-number>, however, if you have changed the port number, specify the changed port number to <port-number>. The backup data is then created using the file name designated in <filename>.

    /opt/FJSVesfcm/postgres/bin/pg_dump -U esfpostgres -C --attribute-inserts
     -p <port-number> -f $BAK_DIR/Common/<filename> esfdb

    A prompt is displayed with the server awaiting input. Input the following keyword.

    master01!
  3. Execute the following shell script to stop ETERNUS SF Manager services.

    /opt/FJSVesfcm/bin/stopesf.sh

    Note

    Upon executing the shell script, multiple messages stating that the ETERNUS SF Manager Tomcat has already been stopped will be displayed. These messages do not pose a problem and can be ignored.

  4. Back up the files related to the performance management function.

    This step can be skipped if you are not using the performance management function. Backup is not required if there are no subdirectories or files.

    Note

    If a pile of files related to the performance management function exists, calculate the backup time according to the amount of files.

    Create the directories for the backup data.

    mkdir -p $BAK_DIR/etc/opt/FJSVssmgr/current
    mkdir -p $BAK_DIR/var/opt/FJSVssmgr/current/perf

    Copy the subdirectories and files to the backup locations.

    cp -p /etc/opt/FJSVssmgr/current/perf.conf $BAK_DIR/etc/opt/FJSVssmgr/current/
    cp -Rp /var/opt/FJSVssmgr/current/perf/* $BAK_DIR/var/opt/FJSVssmgr/current/perf/
  5. Back up the other files which can be customized.

    It is unnecessary to back up the files or the directories which are not existed.

    Create the directories for the backup data.

    mkdir -p $BAK_DIR/etc/opt/FJSVssmgr/current
    mkdir -p $BAK_DIR/etc/opt/FJSVssmgr/current/eventmail

    Copy the subdirectories and files to the backup locations.

    # cp -p /etc/opt/FJSVssmgr/current/sanma.conf $BAK_DIR/etc/opt/FJSVssmgr/current/
    # cp -p /etc/opt/FJSVssmgr/current/ssmgr.conf $BAK_DIR/etc/opt/FJSVssmgr/current/
    # cp -p /etc/opt/FJSVssmgr/current/trapop.sh $BAK_DIR/etc/opt/FJSVssmgr/current/
    # cp -p /etc/opt/FJSVssmgr/current/traprm.sh $BAK_DIR/etc/opt/FJSVssmgr/current/
    # cp -Rp /etc/opt/FJSVssmgr/current/eventmail/* $BAK_DIR/etc/opt/FJSVssmgr/current/eventmail/
  6. Back up the SNMP Trap XML definition files.

    This step can be skipped if you are not customizing the SNMP Trap XML definition files.

    Below is an example for if the SNMP Trap XML definition file 1_3_6_1_1588_2_1_1_1.xml has been customized. As shown in this example, back up each customized file one at a time.

    Create the directory for the backup data.

    mkdir -p $BAK_DIR/etc/opt/FJSVssmgr/current/snmpth

    Copy the file to the backup location.

    # cp -p /etc/opt/FJSVssmgr/current/snmpth/1_3_6_1_1588_2_1_1_1.xml $BAK_DIR/etc/opt/FJSVssmgr/current/snmpth/
  7. Back up the device polling setting files.

    This step can be skipped if you are not customizing the device polling setting files.

    Below is an example for if the device polling setting file, DP_config.xml, has been customized. As shown in this example, back up each customized file one at a time.

    Create the directory for the backup data.

    # mkdir -p $BAK_DIR/etc/opt/FJSVssmgr/current/devicepolling

    Copy the file to the backup location.

    # cp -p /etc/opt/FJSVssmgr/current/devicepolling/DP_config.xml $BAK_DIR/etc/opt/FJSVssmgr/current/devicepolling/
  8. Back up the polling service setting file.

    This step can be skipped if you are not customizing the polling service setting file.

    If you have customized the polling service setting file pollingService.xml, back up this file using the step shown below.

    Create the directory for the backup data.

    # mkdir -p $BAK_DIR/etc/opt/FJSVssmgr/current/polling

    Copy the file to the backup location.

    # cp -p /etc/opt/FJSVssmgr/current/polling/pollingService.xml $BAK_DIR/etc/opt/FJSVssmgr/current/polling/
  9. Save the files related to copy group and copy pair definitions.

    Perform this step only if you are using the AdvancedCopy function.

    Create the directories for the backup data.

    mkdir -p $BAK_DIR/CCM/etc
    mkdir -p $BAK_DIR/CCM/etc/db
    mkdir -p $BAK_DIR/CCM/etc/db/cg
    mkdir -p $BAK_DIR/CCM/etc/prop
    mkdir -p $BAK_DIR/CCM/var/micc/database

    Copy the subdirectories and files to the backup locations.

    cp -p /etc/opt/FJSVccm/db/eternus.xml $BAK_DIR/CCM/etc/db
    cp -p /var/opt/FJSVccm/micc/database/DeviceRegList.xml $BAK_DIR/CCM/var/micc/database
    cp -p /etc/opt/FJSVccm/prop/user.properties $BAK_DIR/CCM/etc/prop
    cp -p /etc/opt/FJSVccm/accc/etc/stxc.alias $BAK_DIR/CCM/etc
    cp -p /etc/opt/FJSVccm/accc/etc/stxc_ext.alias $BAK_DIR/CCM/etc
    cp -p /etc/opt/FJSVccm/accc/etc/stxcvolinf $BAK_DIR/CCM/etc
    cp -Rp /etc/opt/FJSVccm/db/cg/* $BAK_DIR/CCM/etc/db/cg
  10. Back up the license management database.

    Create the directory for the backup data.

    mkdir -p $BAK_DIR/LM

    Execute the following command. The backup data is created using the file name specified in <filename>.

    /opt/FJSVesflm/bin/esflm backup $BAK_DIR/LM/<filename>
  11. Back up the files associated with the Reporting function. (For Reporting Function only)

    Create the directories for the backup data.

    mkdir -p $BAK_DIR/etc/opt/FJSVesfcm/conf/report
    mkdir -p $BAK_DIR/etc/opt/FJSVesfcm/conf/scheduler
    mkdir -p $BAK_DIR/var/opt/FJSVesfcm/report

    Copy the subdirectories and files to the backup locations.

    cp -p /etc/opt/FJSVesfcm/conf/report/* $BAK_DIR/etc/opt/FJSVesfcm/conf/report/
    cp -p /etc/opt/FJSVesfcm/conf/scheduler/* $BAK_DIR/etc/opt/FJSVesfcm/conf/scheduler/
    cp -Rp /var/opt/FJSVesfcm/report/* $BAK_DIR/var/opt/FJSVesfcm/report/
  12. Back up the Optimization Option environment. (For Optimization Option only)

    Create the directories for the backup data.

    mkdir -p $BAK_DIR/etc/opt/FJSVssast/data/policy
    mkdir -p $BAK_DIR/etc/opt/FJSVssast/data/pool
    mkdir -p $BAK_DIR/var/opt/FJSVssast/data/perf

    Copy the subdirectories and files to the backup locations.

    cp -p /etc/opt/FJSVssast/data/policy/TierPolicy.xml $BAK_DIR/etc/opt/FJSVssast/data/policy/
    cp -p /etc/opt/FJSVssast/data/pool/* $BAK_DIR/etc/opt/FJSVssast/data/pool/
    cp -Rp /var/opt/FJSVssast/data/perf/* $BAK_DIR/var/opt/FJSVssast/data/perf/
  13. Back up the Quality of Service Management Option environment. (For Quality of Service Management Option only)

    Create the directories for the backup data.

    mkdir -p $BAK_DIR/etc/opt/FJSVesfcm/conf/qos

    Copy the subdirectories and files to the backup locations.

    cp -p /etc/opt/FJSVesfcm/conf/qos/* $BAK_DIR/etc/opt/FJSVesfcm/conf/qos/
  14. Execute the following shell script to start the ETERNUS SF Manager services.

    /opt/FJSVesfcm/bin/startesf.sh
11.1.1.2.2 Backup of Solaris OS Manager (Cluster Environment)

For cluster environment, follow the procedure below to save the environment for the Storage Cruiser's manager.

  1. Stop all cluster services which the Manager belongs to.

    Refer to "Cluster Transaction and Local Transaction" in the ETERNUS SF Cluster Environment Setup Guide for details of cluster transaction.

  2. Mount the shared disk on the primary node.

  3. Start the ETERNUS SF Manager Postgres service.
    Execute the following command to start the ETERNUS SF Manager Postgres service:

    /etc/init.d/startSFmanager start-postgres
  4. Perform steps 2 and step 4 to 13 of "11.1.1.2.1 Backup of Solaris OS Manager" on the primary node.

  5. Stop the ETERNUS SF Manager Postgres service.
    Execute the following command to stop the ETERNUS SF Manager Postgres service:

    /etc/init.d/startSFmanager stop-postgres
  6. Unmount the shared disk mounted in step 2.

  7. Start all cluster transactions which the Manager belongs to.

11.1.1.2.3 Backup of Linux Manager

Since the procedure for backup of the Linux version of Manager is identical to that for backup of the Solaris OS version, refer to "11.1.1.2.1 Backup of Solaris OS Manager" for performing this operation.

11.1.1.2.4 Back up of Linux Manager (Cluster Environment)

Since the procedure for backup of the Linux version of Manager is identical to that for backup of the Solaris OS versions in cluster environment, refer to "11.1.1.2.2 Backup of Solaris OS Manager (Cluster Environment)" for performing this operation.

11.1.1.2.5 Backup of Windows Manager

Follow the procedure below to save the environment for the Storage Cruiser's manager.

Information

Notation in Procedure:

  • $BAK_DIR means the backup destination directory.

  • $INS_DIR means "Program Directory" specified at the ETERNUS SF Manager installation.

  • $ENV_DIR means "Environment Directory" specified at the ETERNUS SF Manager installation.

  • $TMP_DIR means "Work Directory" specified at the ETERNUS SF Manager installation.

  1. Stop the ETERNUS SF Manager Tomcat Service.

    Open Service Control Manager and stop the following service.

    • ETERNUS SF Manager Tomcat Service

  2. Create the backup data.

    Create the following directory for the backup data in Explorer or a similar program.

    • $BAK_DIR\Common

    Execute the following command to create the backup data. Specify the default value 15432 to <port-number>, however, if you have changed the port number, specify the changed port number to <port-number>. The backup data will be created with the name specified in <filename>.

    $INS_DIR\Common\sys\postgres\bin\pg_dump -U esfpostgres -C --attribute-inserts
     -p <port-number> -f $BAK_DIR\Common\<filename> esfdb

    A prompt is displayed, with the server awaiting input. Input the following keyword.

    master01!
  3. Execute the following batch to stop the ETERNUS SF Manager services.

    $INS_DIR\Common\bin\Stop_ESFservice.bat

    Note

    Upon executing the batch, multiple messages stating that the ETERNUS SF Manager Tomcat Service has already been stopped will be displayed. These messages do not pose a problem and can be ignored.

  4. Back up the files related to the performance management function.

    This step can be skipped if you are not using the performance management function.

    This backup is also not required if there are no subdirectories or files.

    Note

    If a pile of files related to the performance management function exists, calculate the backup time according to the amount of files.

    Create the following directories for the backup data in Explorer or a similar program.

    • $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current

    • $BAK_DIR\ESC\Manager\var\opt\FJSVssmgr\current\perf

    Using Explorer or a similar program, copy the following file to the backup location.

    Copy Source File

    Copy Destination Directory

    $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\perf.conf

    $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current

    Using Explorer or a similar program, copy the subdirectories and files belonging to the following directories to their backup locations.

    Copy Source Directory

    Copy Destination Directory

    $TMP_DIR\ESC\Manager\var\opt\FJSVssmgr\current\perf

    $BAK_DIR\ESC\Manager\var\opt\FJSVssmgr\current\perf

  5. Back up the other files which can be customized.

    It is unnecessary to back up the files or the directories which are not existed.

    Create the following backup directories in Explorer or a similar program.

    • $BAK_DIR\ESC\Manager\opt\FJSVssmgr\bin

    • $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current

    • $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\eventmail

    Using Explorer or a similar program, copy the following files to their backup locations.

    Copy Source File

    Copy Destination Directory

    $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\sanma.conf

    $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current

    $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\ssmgr.conf

    $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\trapop.bat

    $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\traprm.bat

    Using Explorer or a similar program, copy the subdirectories and files belonging to the following directory to their backup location.

    Copy Source Directory

    Copy Destination Directory

    $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\eventmail

    $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\eventmail

  6. Back up the SNMP Trap XML definition files.

    This step can be skipped if you are not customizing the SNMP Trap XML definition files.

    Below is an example for if the SNMP Trap XML definition file 1_3_6_1_1588_2_1_1_1.xml is being customized. As in this example, back up each file one at a time.

    Create the following backup directory in Explorer or a similar program.

    • $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\snmpth

    Using Explorer or a similar program, copy the following file to its backup location.

    Copy Source File

    Copy Destination Directory

    $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\snmpth\1_3_6_1_1588_2_1_1_1.xml

    $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\snmpth

  7. Back up the device polling setting files.

    This step can be skipped if you are not customizing the device polling setting files.

    Below is an example for if the device polling setting file DP_config.xml is being customized. As in this example, back up each file one at a time.

    Create the following backup directory in Explorer or a similar program.

    • $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\devicepolling

    Using Explorer or a similar program, copy the following file to its backup location.

    Copy Source File

    Copy Destination Directory

    $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\devicepolling\DP_config.xml

    $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\devicepolling

  8. Back up the polling service setting file.

    This step can be skipped if you are not customizing the polling service setting file.

    If customizing the polling service setting file pollingService.xml, follow the step below to back it up.

    Create the following backup directory in Explorer or a similar program.

    • $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\polling

    Using Explorer or a similar program, copy the following file to its backup location.

    Copy Source File

    Copy Destination Directory

    $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\polling\pollingService.xml

    $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\polling

  9. Back up the registry.

    Create the following backup directory in Explorer or a similar program.

    • $BAK_DIR\ACM\etc

    Using Explorer or a similar program, copy the following files to the backup location.

    Copy Source File

    Copy Destination Directory

    $ENV_DIR\ACM\etc\swnode.ini

    $BAK_DIR\ACM\etc

    $ENV_DIR\ACM\etc\device.ini

  10. Save the files related to copy group and copy pair definitions.

    Perform this step only if you are using the AdvancedCopy function.

    Create the following directories for the backup data in Explorer or a similar program.

    • $BAK_DIR\CCM\etc

    • $BAK_DIR\CCM\etc\db

    • $BAK_DIR\CCM\etc\db\cg

    • $BAK_DIR\CCM\etc\prop

    • $BAK_DIR\CCM\var\micc\database

    Using Explorer or a similar program, copy the following files to their backup locations.

    Copy Source File

    Copy Destination Directory

    $ENV_DIR\CCM\etc\db\eternus.xml

    $BAK_DIR\CCM\etc\db

    $TMP_DIR\CCM\var\micc\database\DeviceRegList.xml

    $BAK_DIR\CCM\var\micc\database

    If copy source files exist, copy the following files to their backup locations using Explorer or a similar program.

    Copy Source File

    Copy Destination Directory

    $ENV_DIR\CCM\etc\prop\user.properties

    $BAK_DIR\CCM\etc\prop

    $ENV_DIR\CCM\etc\stxc.alias

    $BAK_DIR\CCM\etc

    $ENV_DIR\CCM\etc\stxc_ext.alias

    $ENV_DIR\CCM\etc\stxcvolinf

    Using Explorer or a similar program, copy the files belonging to the following directory to their backup location.

    Copy Source Directory

    Copy Destination Directory

    $ENV_DIR\CCM\etc\db\cg

    $BAK_DIR\CCM\etc\db\cg

  11. Back up the license management database.

    Create the following backup directory in Explorer or a similar program.

    • $BAK_DIR\LM

    Execute the following command. The backup data will be created with the file name specified in <filename>.

    $INS_DIR\LM\bin\esflm backup $BAK_DIR\LM\<filename>
  12. Back up the files associated with the Reporting function. (For Reporting Function only)

    Create the following backup directories using Explorer or the like:

    • $BAK_DIR\Common\etc\report

    • $BAK_DIR\Common\etc\scheduler

    • $BAK_DIR\Common\var\report

    Copy the files under the following directories to the backup location using Explorer or the like:

    Copy Source Directory

    Copy Destination Directory

    $ENV_DIR\Common\etc\report

    $BAK_DIR\Common\etc\report

    $ENV_DIR\Common\etc\scheduler

    $BAK_DIR\Common\etc\scheduler

    Copy the files under the following directories to the backup location using Explorer or the like:

    Copy Source Directory

    Copy Destination Directory

    $TMP_DIR\Common\var\report

    $BAK_DIR\Common\var\report

  13. Back up the Optimization Option environment. (For Optimization Option only)

    Create the following directories for the backup data in Explorer or a similar program.

    • $BAK_DIR\AST\Manager\etc\opt\FJSVssast\data\policy

    • $BAK_DIR\AST\Manager\etc\opt\FJSVssast\data\pool

    • $BAK_DIR\AST\Manager\var\opt\FJSVssast\data\perf

    Using Explorer or a similar program, copy the following files to their backup locations.

    Copy Source File

    Copy Destination Directory

    $ENV_DIR\AST\Manager\etc\opt\FJSVssast\data\policy\TierPolicy.xml

    $BAK_DIR\AST\Manager\etc\opt\FJSVssast\data\policy

    Using Explorer or a similar program, copy the subdirectories and files belonging to the following directory to their backup location.

    Copy Source Directory

    Copy Destination Directory

    $ENV_DIR\AST\Manager\etc\opt\FJSVssast\data\pool

    $BAK_DIR\AST\Manager\etc\opt\FJSVssast\data\pool

    $TMP_DIR\AST\Manager\var\opt\FJSVssast\data\perf

    $BAK_DIR\AST\Manager\var\opt\FJSVssast\data\perf

  14. Back up the Quality of Service Management Option environment. (For Quality of Service Management Option only)

    Create the following backup directory using Explorer or the like:

    • $BAK_DIR\Common\etc\qos

    Copy the files under the following directory to the backup location using Explorer or the like:

    Copy Source Directory

    Copy Destination Directory

    $ENV_DIR\Common\etc\qos

    $BAK_DIR\Common\etc\qos

  15. Execute the following batch to start ETERNUS SF Manager services.

    $INS_DIR\Common\bin\Start_ESFservice.bat
11.1.1.2.6 Backup of Windows Manager (Cluster Environment)

For cluster environment, follow the procedure below to save the environment for the Storage Cruiser's manager.

  1. Stop all cluster services which the Manager belongs to.

    Refer to "Cluster Transaction and Local Transaction" in the ETERNUS SF Cluster Environment Setup Guide for details of cluster transaction.

  2. Mount the shared disk on the primary node.

  3. Start the ETERNUS SF Manager Postgres service.
    Open Service Control Manager to start the following service:

    • ETERNUS SF Manager Postgres Service

  4. Perform steps 2 and step 4 to 14 of "11.1.1.2.5 Backup of Windows Manager" on the primary node.

    Directory description in "11.1.1.2.5 Backup of Windows Manager" are replaced to the following directories.

    • $BAK_DIR means the backup destination directory.

    • $INS_DIR means "Program Directory" specified at the ETERNUS SF Manager installation.

    • $ENV_DIR means "Environment Directory" specified at the ETERNUS SF Manager installation.

    • $TMP_DIR means "Work Directory" as specified during installation.

  5. Stop the ETERNUS SF Manager Postgres service.
    Open Service Control Manager to stop the following service:

    • ETERNUS SF Manager Postgres Service

  6. Unmount the shared disk mounted in step 2.

  7. Start all cluster transactions which the Manager belongs to.

11.1.1.3 Restoring Manager

Restore the environment for the Storage Cruiser's manager if an error has occurred in the Management Server.

All of the tasks for restoring Manager are performed in the Management Server.

11.1.1.3.1 Restoring Solaris OS Manager

Follow the procedure below to restore the environment for the Storage Cruiser's manager.

For restoration after reinstalling Manager, be sure to complete installation and setup before restoration. Refer to "Installation of ETERNUS SF Manager" and "Setup of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for installation and setup.

Information

Notation in Procedure:

  • "$BAK_DIR" signifies the backup destination directory.

  1. Re-setup Storage Cruiser's manager.

    Install ETERNUS SF Manager and set it up as Storage Cruiser's manager.

    Refer to "Installation of ETERNUS SF Manager" and "Setup of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for installation and setup.

  2. Stop the ETERNUS SF Manager Tomcat Service.

    Execute the following shell script to stop the service.

    /opt/FJSVesfcm/bin/stop-webservice.sh
  3. Restore the backup data.

    Execute the following command. Specify the default value 15432 to <port-number>, however, if you have changed the port number, specify the changed port number to <port-number>.

    /opt/FJSVesfcm/postgres/bin/psql -U esfpostgres -p <port-number> postgres

    A prompt is displayed, with the server awaiting input. Input the following keywords in the sequence shown below.

    master01!
    drop database esfdb;
    \q

    Execute the following command to restore the backup data. Specify the default value 15432 to <port-number>, however, if you have changed the port number, specify the changed port number to <port-number>. For <filename>, input the file name specified when the backup data was created.

    /opt/FJSVesfcm/postgres/bin/psql -U esfpostgres -p <port-number>
     -f $BAK_DIR/Common/<filename> postgres

    A prompt is displayed, with the server awaiting input. Input the following keyword.

    master01!
  4. Execute the following shell script to stop the ETERNUS SF Manager services.

    /opt/FJSVesfcm/bin/stopesf.sh

    Note

    Upon executing the shell script, multiple messages stating that the ETERNUS SF Manager Tomcat Service has already been stopped will be displayed. These messages do not pose a problem and can be ignored.

  5. Restore the files related to the performance management function.

    This step can be skipped if you are not using the performance management function or the files related to the performance management function are not backed up.

    Delete the subdirectories and files belonging to the restore destination directory.

    However, be sure not to delete the restore destination directory itself. If the restore destination directory itself does not exist, create one.

    rm -f /etc/opt/FJSVssmgr/current/perf.conf
    rm -rf /var/opt/FJSVssmgr/current/perf/*

    Copy the subdirectories and files from the backup location.

    cp -p $BAK_DIR/etc/opt/FJSVssmgr/current/perf.conf /etc/opt/FJSVssmgr/current/
    cp -Rp $BAK_DIR/var/opt/FJSVssmgr/current/perf/* /var/opt/FJSVssmgr/current/perf/
  6. Restore the other files which can be customized.

    This restoration is unnecessary for the files or the directories which have not been backed up.

    Copy the subdirectories and files from the backup location.

    # cp -p $BAK_DIR/etc/opt/FJSVssmgr/current/sanma.conf /etc/opt/FJSVssmgr/current/
    # cp -p $BAK_DIR/etc/opt/FJSVssmgr/current/ssmgr.conf /etc/opt/FJSVssmgr/current/
    # cp -p $BAK_DIR/etc/opt/FJSVssmgr/current/trapop.sh /etc/opt/FJSVssmgr/current/
    # cp -p $BAK_DIR/etc/opt/FJSVssmgr/current/traprm.sh /etc/opt/FJSVssmgr/current/
    # cp -Rp $BAK_DIR/etc/opt/FJSVssmgr/current/eventmail/* /etc/opt/FJSVssmgr/current/eventmail/
  7. Restore the SNMP Trap XML definition files.

    This restoration is unnecessary for the files which have not been backed up.

    Copy the SNMP Trap XML definition files from the backup location.

    # cp -p $BAK_DIR/etc/opt/FJSVssmgr/current/snmpth/*.xml /etc/opt/FJSVssmgr/current/snmpth/
  8. Restore the device polling setting files.

    This restoration is unnecessary for the files which have not been backed up.

    Copy the files from the backup location.

    # cp -p $BAK_DIR/etc/opt/FJSVssmgr/current/devicepolling/*.xml /etc/opt/FJSVssmgr/current/devicepolling/
  9. Restore the polling service setting file.

    This restoration is unnecessary for the files which have not been backed up.

    Copy the file from the backup location.

    # cp -p $BAK_DIR/etc/opt/FJSVssmgr/current/polling/*.xml /etc/opt/FJSVssmgr/current/polling/
  10. Restore the files related to copy group and copy pair definitions.

    Perform this step only if you are using the AdvancedCopy function.

    Delete the subdirectories and files belonging to the restore destination directory.

    rm -rf /etc/opt/FJSVccm/db/cg/*
    rm -f /etc/opt/FJSVccm/prop/user.properties
    rm -f /etc/opt/FJSVccm/accc/etc/stxc.alias
    rm -f /etc/opt/FJSVccm/accc/etc/stxc_ext.alias
    rm -f /etc/opt/FJSVccm/accc/etc/stxcvolinf

    Copy the subdirectories and files from the backup location.

    cp -p $BAK_DIR/CCM/etc/db/eternus.xml /etc/opt/FJSVccm/db
    cp -p $BAK_DIR/CCM/var/micc/database/DeviceRegList.xml /var/opt/FJSVccm/micc/database
    cp -p $BAK_DIR/CCM/etc/prop/user.properties /etc/opt/FJSVccm/prop
    cp -p $BAK_DIR/CCM/etc/stxc.alias /etc/opt/FJSVccm/accc/etc
    cp -p $BAK_DIR/CCM/etc/stxc_ext.alias /etc/opt/FJSVccm/accc/etc
    cp -p $BAK_DIR/CCM/etc/stxcvolinf /etc/opt/FJSVccm/accc/etc
    cp -Rp $BAK_DIR/CCM/etc/db/cg/* /etc/opt/FJSVccm/db/cg
  11. Restore the license management database.

    Execute the following command. For <filename>, input the file name which was specified when the backup data was created.

    /opt/FJSVesflm/bin/esflm restore $BAK_DIR/LM/<filename>
  12. Restore the files associated with the Reporting function. (For Reporting Function only)

    If the files associated with the Reporting function are not backed up, this procedure is not needed.

    Delete the subdirectories and files belonging to the restore destination directory.
    However, be sure not to delete the restore destination directory itself. If the restore destination directory itself does not exist, create one.

    rm -f /etc/opt/FJSVesfcm/conf/report/*
    rm -f /etc/opt/FJSVesfcm/conf/scheduler/*
    rm -rf /var/opt/FJSVesfcm/report/*

    Copy the subdirectories and files from the backup location.

    cp -p $BAK_DIR/etc/opt/FJSVesfcm/conf/report/* /etc/opt/FJSVesfcm/conf/report/
    cp -p $BAK_DIR/etc/opt/FJSVesfcm/conf/scheduler/* /etc/opt/FJSVesfcm/conf/scheduler/
    cp -Rp $BAK_DIR/var/opt/FJSVesfcm/report/* /var/opt/FJSVesfcm/report/
  13. Restore the Optimization Option environment. (For Optimization Option only)

    Delete the subdirectories and files belonging to the restore destination directory.
    However, be sure not to delete the restore destination directory itself. If the restore destination directory itself does not exist, create one.

    rm -f /etc/opt/FJSVssast/data/policy/TierPolicy.xml
    rm -f /etc/opt/FJSVssast/data/pool/*
    rm -rf /var/opt/FJSVssast/data/perf/*

    Copy the subdirectories and files from the backup location.

    cp -p $BAK_DIR/etc/opt/FJSVssast/data/policy/TierPolicy.xml /etc/opt/FJSVssast/data/policy/
    cp -p $BAK_DIR/etc/opt/FJSVssast/data/pool/* /etc/opt/FJSVssast/data/pool/
    cp -Rp $BAK_DIR/var/opt/FJSVssast/data/perf/* /var/opt/FJSVssast/data/perf/
  14. Restore the Quality of Service Management Option environment. (For Quality of Service Management Option only)

    Delete the subdirectories and files belonging to the restore destination directory.
    However, be sure not to delete the restore destination directory itself. If the restore destination directory itself does not exist, create one.

    rm -f /etc/opt/FJSVesfcm/conf/qos/*

    Copy the subdirectories and files from the backup location.

    cp -p $BAK_DIR/etc/opt/FJSVesfcm/conf/qos/* /etc/opt/FJSVesfcm/conf/qos/
  15. Execute the following shell script to start ETERNUS SF Manager services.

    /opt/FJSVesfcm/bin/startesf.sh
11.1.1.3.2 Restoring Solaris OS Manager (Cluster Environment)

For cluster environment, follow the procedure below to restore the environment for the Storage Cruiser's manager.

For restoration after reinstalling Manager, be sure to complete installation and setup before restoration. Refer to "Customization for Management Server Transaction" in the ETERNUS SF Cluster Environment Setup Guide for installation and setup.

  1. Stop all cluster transaction which the Manager belongs to.

    Refer to "Cluster Transaction and Local Transaction" in the ETERNUS SF Cluster Environment Setup Guide for details of cluster transaction.

  2. Mount the shared disk on the primary node.

  3. Start the ETERNUS SF Manager Postgres service.
    Execute the following command to start the ETERNUS SF Manager Postgres service:

    /etc/init.d/startSFmanager start-postgres
  4. Perform steps 3 and step 5 to 14 of "11.1.1.3.1 Restoring Solaris OS Manager" on the primary node.

  5. Stop the ETERNUS SF Manager Postgres service.
    Execute the following command to stop the ETERNUS SF Manager Postgres service:

    /etc/init.d/startSFmanager stop-postgres
  6. Unmount the shared disk mounted in step 2.

  7. Start all cluster transactions which the Manager belongs to.

11.1.1.3.3 Restoring Linux Manager

Since the procedure for restoring the Linux version of Manager is identical to that for restoring the Solaris OS versions, refer to "11.1.1.3.1 Restoring Solaris OS Manager" for performing this operation.

11.1.1.3.4 Restoring Linux Manager (Cluster Environment)

Since the procedure for restoring the Linux version of Manager is identical to that for restoring the Solaris OS versions in cluster environment, refer to "11.1.1.3.2 Restoring Solaris OS Manager (Cluster Environment)" for performing this operation.

11.1.1.3.5 Restoring Windows Manager

Follow the procedure below to restore the environment for Storage Cruiser's manager.

For restoration after reinstalling Manager, be sure to complete installation and setup before restoration. Refer to "Installation of ETERNUS SF Manager" and "Setup of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for the installation and setup procedures.

Information

Notation in Procedure:

  • $BAK_DIR means the backup destination directory.

  • $INS_DIR means "Program Directory" specified at the ETERNUS SF Manager installation.

  • $ENV_DIR means "Environment Directory" specified at the ETERNUS SF Manager installation.

  • $TMP_DIR means "Work Directory" specified at the ETERNUS SF Manager installation.

  1. Re-setup Storage Cruiser's manager.

    Install ETERNUS SF Manager and set it up as Storage Cruiser's manager.

    Refer to "Installation of ETERNUS SF Manager" and "Setup of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for installation and setup procedures.

  2. Stop the ETERNUS SF Manager Tomcat Service.

    Open the Service Control Manager and stop the following service.

    • ETERNUS SF Manager Tomcat Service

  3. Restore the backup data.

    Execute the following command. Specify the default value 15432 to <port-number>, however, if you have changed the port number, specify the changed port number to <port-number>.

    $INS_DIR\Common\sys\postgres\bin\psql -U esfpostgres -p <port-number> postgres

    A prompt is displayed, with the server awaiting input. Input the following keywords in the sequence shown below.

    master01!
    drop database esfdb;
    \q

    Execute the following command to restore the backup data. Specify the default value 15432 to <port-number>, however, if you have changed the port number, specify the changed port number to <port-number>. For <filename>, input the file name which was specified when the backup data was created.

    $INS_DIR\Common\sys\postgres\bin\psql -U esfpostgres -p <port-number>
     -f $BAK_DIR\Common\<filename> postgres

    A prompt is displayed, with the server awaiting input. Input the following keyword.

    master01!
  4. Execute the following batch to stop the ETERNUS SF Manager services.

    $INS_DIR\Common\bin\Stop_ESFservice.bat

    Note

    Upon executing the batch, multiple messages stating that the ETERNUS SF Manager Tomcat Service has already been stopped will be displayed. These messages do not pose a problem and can be ignored.

  5. Restore the files related to the performance management function.

    This step can be skipped if you are not using the performance management function or the files related to the performance management function are not backed up.

    Using Explorer or a similar program, delete the subdirectories and files belonging to the following restore destination directory.

    However, be sure not to delete the restore destination directory itself. If the restore destination directory itself does not exist, create it.

    • $TMP_DIR\ESC\Manager\var\opt\FJSVssmgr\current\perf

    Using Explorer or a similar program, copy the following file from its backup location.

    Copy Source File

    Copy Destination Directory

    $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\perf.conf

    $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current

    Using Explorer or a similar program, copy the subdirectories and files belonging to the following directory from their backup location.

    Copy Source Directory

    Copy Destination Directory

    $BAK_DIR\ESC\Manager\var\opt\FJSVssmgr\current\perf

    $TMP_DIR\ESC\Manager\var\opt\FJSVssmgr\current\perf

  6. Restore the other files which can be customized.

    This restoration is unnecessary for the files or the directories which have not been backed up.

    Using Explorer or a similar program, copy the following files from the backup locations.

    Copy Source File

    Copy Destination Directory

    $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\sanma.conf

    $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current

    $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\ssmgr.conf

    $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\trapop.bat

    $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\traprm.bat

    Using Explorer or a similar program, copy the subdirectories and files belonging to the following directory from their backup location.

    Copy Source Directory

    Copy Destination Directory

    $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\eventmail

    $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\eventmail

  7. Restore the SNMP Trap XML definition files.

    This restoration is unnecessary for the files which have not been backed up.

    Using Explorer or a similar program, copy the SNMP Trap XML definition files from their backup location.

    Copy Source File

    Copy Destination Directory

    $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\snmpth\*.xml

    $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\snmpth

  8. Restore the device polling setting files.

    This restoration is unnecessary for the files which have not been backed up.

    Using Explorer or a similar program, copy the device polling setting file from its backup location.

    Copy Source File

    Copy Destination Directory

    $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\devicepolling\DP_config.xml

    $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\devicepolling

  9. Restore the polling service setting file.

    This restoration is unnecessary for the files which have not been backed up.

    Using Explorer or a similar program, copy the polling service setting file from its backup location.

    Copy Source File

    Copy Destination Directory

    $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\polling\pollingService.xml

    $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\polling

  10. Restore the registry.

    Using Explorer or a similar program, copy the following files from their backup location.

    Copy Source File

    Copy Destination Directory

    $BAK_DIR\ACM\etc\swnode.ini

    $ENV_DIR\ACM\etc

    $BAK_DIR\ACM\etc\device.ini

  11. Restore the files related to copy group and copy pair definitions.

    Perform this step only if you are using the AdvancedCopy function.

    Using Explorer or a similar program, delete the files belonging to the following restore destination directory.

    • $ENV_DIR\CCM\etc\db\cg

    Delete the following files if they exist.

    • $ENV_DIR\CCM\etc\prop\user.properties

    • $ENV_DIR\CCM\etc\stxc.alias

    • $ENV_DIR\CCM\etc\stxc_ext.alias

    • $ENV_DIR\CCM\etc\stxcvolinf

    Using Explorer or a similar program, copy the following files from their backup locations.

    Copy Source File

    Copy Destination Directory

    $BAK_DIR\CCM\etc\db\eternus.xml

    $ENV_DIR\CCM\etc\db

    $BAK_DIR\CCM\var\micc\database\DeviceRegList.xml

    $TMP_DIR\CCM\var\micc\database

    If copy source files exist, copy the following files from the backup location using Explorer or a similar program.

    Copy Source File

    Copy Destination Directory

    $BAK_DIR\CCM\etc\prop\user.properties

    $ENV_DIR\CCM\etc\prop

    $BAK_DIR\CCM\etc\stxc.alias

    $ENV_DIR\CCM\etc

    $BAK_DIR\CCM\etc\stxc_ext.alias

    $BAK_DIR\CCM\etc\stxcvolinf

    Using Explorer or a similar program, copy the files belonging to the following directory from their backup location.

    Copy Source Directory

    Copy Destination Directory

    $BAK_DIR\CCM\etc\db\cg

    $ENV_DIR\CCM\etc\db\cg

  12. Restore the license management database.

    Execute the following command. For <filename>, input the file name which was specified when the backup data was created.

    $INS_DIR\LM\bin\esflm restore $BAK_DIR\LM\<filename>
  13. Restore the files associated with the Reporting function. (For Reporting Function only)

    If the files associated with the Reporting function are not backed up, this procedure is not needed.

    Delete the subdirectories and files belonging to the restore destination directory.
    However, be sure not to delete the restore destination directory itself. If the restore destination directory itself does not exist, create one.

    • $TMP_DIR\Common\var\report

    Copy the files under the following directories from the backup location using Explorer or the like:

    Copy Source Directory

    Copy Destination Directory

    $BAK_DIR\Common\etc\report

    $ENV_DIR\Common\etc\report

    $BAK_DIR\Common\etc\scheduler

    $ENV_DIR\Common\etc\scheduler

    Copy the files under the following directory from the backup location using Explorer or the like:

    Copy Source Directory

    Copy Destination Directory

    $BAK_DIR\Common\var\report

    $TMP_DIR\Common\var\report

  14. Restore the Optimization Option environment. (For Optimization Option only)

    Delete the subdirectories and files belonging to the restore destination directory.
    However, be sure not to delete the restore destination directory itself. If the restore destination directory itself does not exist, create one.

    • $TMP_DIR\AST\Manager\var\opt\FJSVssast\data\perf

    Using Explorer or a similar program, copy the following files from their backup locations.

    Copy Source File

    Copy Destination Directory

    $BAK_DIR\AST\Manager\etc\opt\FJSVssast\data\policy\TierPolicy.xml

    $ENV_DIR\AST\Manager\etc\opt\FJSVssast\data\policy

    Using Explorer or a similar program, copy the subdirectories and files belonging to the following directory from their backup location.

    Copy Source Directory

    Copy Destination Directory

    $BAK_DIR\AST\Manager\etc\opt\FJSVssast\data\pool

    $ENV_DIR\AST\Manager\etc\opt\FJSVssast\data\pool

    $BAK_DIR\AST\Manager\var\opt\FJSVssast\data\perf

    $TMP_DIR\AST\Manager\var\opt\FJSVssast\data\perf

  15. Restore the Quality of Service Management Option environment. (For Quality of Service Management Option only)

    Copy the files under the following directories from the backup location using Explorer or the like:

    Copy Source Directory

    Copy Destination Directory

    $BAK_DIR\Common\etc\qos

    $ENV_DIR\Common\etc\qos

  16. Execute the following batch to start ETERNUS SF Manager services.

    $INS_DIR\Common\bin\Start_ESFservice.bat
11.1.1.3.6 Restoring Windows Manager (Cluster Environment)

For cluster environment, follow the procedure below to restore the environment for the Storage Cruiser's manager.

For restoration after reinstalling Manager, be sure to complete installation and setup before restoration. Refer to "Installation of ETERNUS SF Manager" and "Customization for Management Server Transaction" in the ETERNUS SF Cluster Environment Setup Guide for installation and setup.

  1. Stop all cluster transactions which the Manager belongs to.

    Refer to "Cluster Transaction and Local Transaction" in the ETERNUS SF Cluster Environment Setup Guide for details of cluster transaction.

  2. Mount the shared disk on the primary node.

  3. Start the ETERNUS SF Manager Postgres service.
    Open Service Control Manager to start the following service:

    • ETERNUS SF Manager Postgres Service

  4. Perform steps 3 and step 5 to 15 of "11.1.1.3.5 Restoring Windows Manager" on the primary node.

    Directory description in "11.1.1.3.5 Restoring Windows Manager" are replaced to the following directories.

    • $BAK_DIR means the backup destination directory.

    • $INS_DIR means "Program Directory" specified at the ETERNUS SF Manager installation.

    • $ENV_DIR means "Environment Directory" specified at the ETERNUS SF Manager installation.

    • $TMP_DIR means "Work Directory" specified at the ETERNUS SF Manager installation.

  5. Stop the ETERNUS SF Manager Postgres service.
    Open Service Control Manager to stop the following service:

    • ETERNUS SF Manager Postgres Service

  6. Unmount the shared disk mounted in step 2.

  7. Start all cluster transactions which the Manager belongs to.