Top
ETERNUS SF Storage Cruiser V16.7 Operation Guide
FUJITSU Storage
Chapter 11 Maintenance of Administrative Environment > 11.1 Maintenance of Manager > 11.1.1 Maintenance of Manager
PreviousNext

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

    1. Create the directory for the backup data.

      # mkdir -p $BAK_DIR/Common

    2. Execute the following command to create the backup data. Specify the default value 15432 to portNumber, however, if you have changed the port number, specify the changed port number to portNumber. 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 portNumber -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

    Information

    Upon executing the shell script, multiple messages stating that the ETERNUS SF Manager Tomcat has already been stopped are 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. A backup is not required if there are no subdirectories or files.

    Point

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

    1. Create the directories for the backup data.

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

    2. 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 /etc/opt/FJSVssmgr/current/perfconf/* $BAK_DIR/etc/opt/FJSVssmgr/current/perfconf/
# cp -Rp /var/opt/FJSVssmgr/current/perf/* $BAK_DIR/var/opt/FJSVssmgr/current/perf/

  5. Back up the files related to the capacity management function.

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

    Point

    If a large amount of files that are related to the capacity graph exists, calculate the backup time according to the amount of files.

    1. Create the directories for the backup data.

      # mkdir -p $BAK_DIR/var/opt/FJSVssmgr/current/thinprovisioning
# mkdir -p $BAK_DIR/var/opt/FJSVssmgr/current/flexibletier
# mkdir -p $BAK_DIR/var/opt/FJSVssmgr/current/nas

    2. Copy the subdirectories and files to the backup locations.

      # cp -Rp /var/opt/FJSVssmgr/current/thinprovisioning/* $BAK_DIR/var/opt/FJSVssmgr/current/thinprovisioning/
# cp -Rp /var/opt/FJSVssmgr/current/flexibletier/* $BAK_DIR/var/opt/FJSVssmgr/current/flexibletier/
# cp -Rp /var/opt/FJSVssmgr/current/nas/* $BAK_DIR/var/opt/FJSVssmgr/current/nas/

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

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

    1. Create the directories for the backup data.

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

    2. 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 -Rp /etc/opt/FJSVssmgr/current/eventmail/* $BAK_DIR/etc/opt/FJSVssmgr/current/eventmail/

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

    1. Create the directory for the backup data.

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

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

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

    1. Create the directory for the backup data.

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

    2. Copy the file to the backup location.

      # cp -p /etc/opt/FJSVssmgr/current/devicepolling/DP_config.xml $BAK_DIR/etc/opt/FJSVssmgr/current/devicepolling/

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

    1. Create the directory for the backup data.

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

    2. Copy the file to the backup location.

      # cp -p /etc/opt/FJSVssmgr/current/polling/pollingService.xml $BAK_DIR/etc/opt/FJSVssmgr/current/polling/

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

    Perform this step only if you are using the Advanced Copy function.

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

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

  11. Back up the license management database.

    1. Create the directory for the backup data.

      # mkdir -p $BAK_DIR/LM

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

  12. Back up the files associated with the Reporting function. (For Reporting Function only)

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

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

  13. Back up the files related to the Automated Storage Tiering function.

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

    1. Create the directories for the backup data.

      # mkdir -p $BAK_DIR/etc/opt/FJSVssast/data
# mkdir -p $BAK_DIR/var/opt/FJSVssast/data

    2. Copy the subdirectories and files to the backup locations.

      # cp -Rp /etc/opt/FJSVssast/data/* $BAK_DIR/etc/opt/FJSVssast/data/
# cp -Rp /var/opt/FJSVssast/data/* $BAK_DIR/var/opt/FJSVssast/data/

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

    1. Create the directories for the backup data.

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

    2. Copy the subdirectories and files to the backup locations.

      # cp -p /etc/opt/FJSVesfcm/conf/qos/* $BAK_DIR/etc/opt/FJSVesfcm/conf/qos/

  15. 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/Linux 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:

    • For the Solaris/RHEL5/RHEL6 environment

      # /etc/init.d/startSFmanager start-postgres

    • For the RHEL7 environment

      # /opt/FJSVesfcm/bin/startSFmanager start-postgres

  4. Perform step 2 and step 4 to 14 of "11.1.1.2.1 Backup of Solaris OS/Linux 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:

    • For the Solaris/RHEL5/RHEL6 environment

      # /etc/init.d/startSFmanager stop-postgres

    • For the RHEL7 environment

      # /opt/FJSVesfcm/bin/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 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.

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

      • $BAK_DIR\Common

    2. Execute the following command to create the backup data. Specify the default value 15432 to portNumber, however, if you have changed the port number, specify the changed port number to portNumber. The backup data is created with the name specified in fileName.

      > $INS_DIR\Common\sys\postgres\bin\pg_dump -U esfpostgres -C --attribute-inserts
 -p portNumber -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

    Information

    Upon executing the batch, multiple messages stating that the ETERNUS SF Manager Tomcat Service has already been stopped are 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.

    Point

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

    1. 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\etc\opt\FJSVssmgr\current\perfconf

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

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

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

      Copy Source Directory

      Copy Destination Directory

      $TMP_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\perfconf

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

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

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

  5. Back up the files related to the capacity management function.

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

    Point

    If a large amount of files that are related to the capacity graph exists, calculate the backup time according to the amount of files.

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

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

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

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

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

      Copy Source Directory

      Copy Destination Directory

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

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

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

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

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

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

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

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

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

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

    3. Using Explorer or a similar program, copy the subdirectories and files under 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

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

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

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

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

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

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

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

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

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

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

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

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

  10. Back up the registry.

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

      • $BAK_DIR\ACM\etc

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

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

    Perform this step only if you are using the Advanced Copy function.

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

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

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

    4. Using Explorer or a similar program, copy the files under 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

  12. Back up the license management database.

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

      • $BAK_DIR\LM

    2. Execute the following command. The backup data is created with the file name specified in fileName.

      > $INS_DIR\LM\bin\esflm backup $BAK_DIR\LM\fileName

  13. Back up the files associated with the Reporting function. (For Reporting Function only)

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

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

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

  14. Back up the files related to the Automated Storage Tiering function.

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

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

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

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

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

      Copy Source Directory

      Copy Destination Directory

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

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

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

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

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

    1. Create the following backup directory using Explorer or the like:

      • $BAK_DIR\Common\etc\qos

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

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

    > $INS_DIR\Common\bin\Start_ESFservice.bat
11.1.1.2.4 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 15 of "11.1.1.2.3 Backup of Windows Manager" on the primary node.

    Directory description in "11.1.1.2.3 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/Linux 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.

    1. Execute the following command. Specify the default value 15432 to portNumber, however, if you have changed the port number, specify the changed port number to portNumber.

      # /opt/FJSVesfcm/postgres/bin/psql -U esfpostgres -p portNumber postgres

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

      master01!
drop database esfdb;
\q

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

      # /opt/FJSVesfcm/postgres/bin/psql -U esfpostgres -p portNumber
 -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

    Information

    Upon executing the shell script, multiple messages stating that the ETERNUS SF Manager Tomcat Service has already been stopped are 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 if you are not backing up the files related to the performance management function.

    1. Delete the subdirectories and files under the restore destination directory "/etc/opt/FJSVssmgr/current".
      However, do not delete the restore destination directory itself.

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

      If the restore destination directory does not exist, create it with the following owner, group, and access privilege.

      OS Type

      Owner

      Group

      Access Privilege

      Solaris OS
      Linux

      root (superuser)

      root

      755

    2. 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/etc/opt/FJSVssmgr/current/perfconf/* /etc/opt/FJSVssmgr/current/perfconf/
# cp -Rp $BAK_DIR/var/opt/FJSVssmgr/current/perf/* /var/opt/FJSVssmgr/current/perf/

  6. Restore the files related to the capacity management function.

    This step can be skipped if you are not backing up the files related to the capacity management function.

    1. Delete the subdirectories and files under the restore destination directory "/var/opt/FJSVssmgr/current".
      However, do not delete the restore destination directory itself.

      # rm -rf /var/opt/FJSVssmgr/current/thinprovisioning/*
# rm -rf /var/opt/FJSVssmgr/current/flexibletier/*
# rm -rf /var/opt/FJSVssmgr/current/nas/*

      If the restore destination directory does not exist, create it with the following owner, group, and access privilege.

      OS Type

      Owner

      Group

      Access Privilege

      Solaris OS
      Linux

      root (superuser)

      root

      755

    2. Copy the subdirectories and files from the backup location.

      # cp -Rp $BAK_DIR/var/opt/FJSVssmgr/current/thinprovisioning/* /var/opt/FJSVssmgr/current/thinprovisioning/
# cp -Rp $BAK_DIR/var/opt/FJSVssmgr/current/flexibletier/* /var/opt/FJSVssmgr/current/flexibletier/
# cp -Rp $BAK_DIR/var/opt/FJSVssmgr/current/nas/* /var/opt/FJSVssmgr/current/nas/

  7. Restore the other files which can be customized.

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

    1. Check whether the /etc/opt/FJSVssmgr/current/eventmail directory exist.
      If the directory does not exist, create it with the following owner, group, and access privilege.

      OS Type

      Owner

      Group

      Access Privilege

      Solaris OS

      root (superuser)

      sys

      755

      Linux

      root (superuser)

      root

      755

    2. 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 -Rp $BAK_DIR/etc/opt/FJSVssmgr/current/eventmail/* /etc/opt/FJSVssmgr/current/eventmail/

  8. Restore the SNMP Trap XML definition files.

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

    1. Check whether the /etc/opt/FJSVssmgr/current/snmpth directory exist.
      If the directory does not exist, create it with the following owner, group, and access privilege.

      OS Type

      Owner

      Group

      Access Privilege

      Solaris OS
      Linux

      root (superuser)

      sys

      755

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

  9. Restore the device polling setting files.

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

    1. Check whether the /etc/opt/FJSVssmgr/current/devicepolling directory exist.
      If the directory does not exist, create it with the following owner, group, and access privilege.

      OS Type

      Owner

      Group

      Access Privilege

      Solaris OS
      Linux

      root (superuser)

      sys

      755

    2. Copy the files from the backup location.

      # cp -p $BAK_DIR/etc/opt/FJSVssmgr/current/devicepolling/*.xml /etc/opt/FJSVssmgr/current/devicepolling/

  10. Restore the polling service setting file.

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

    1. Check whether the /etc/opt/FJSVssmgr/current/polling directory exist.
      If the directory does not exist, create it with the following owner, group, and access privilege.

      OS Type

      Owner

      Group

      Access Privilege

      Solaris OS
      Linux

      root (superuser)

      sys

      755

    2. Copy the file from the backup location.

      # cp -p $BAK_DIR/etc/opt/FJSVssmgr/current/polling/*.xml /etc/opt/FJSVssmgr/current/polling/

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

    Perform this step only if you are using the Advanced Copy function.

    1. Delete the subdirectories and files under the restore destination directories "/etc/opt/FJSVccm/db/cg", "/etc/opt/FJSVccm/prop", and "/etc/opt/FJSVccm/accc/etc".

      # 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

      If the restore destination directories do not exist, create them with the following owner, group, and access privilege.

      OS Type

      Restore Destination Directory

      Owner

      Group

      Access Privilege

      Solaris OS

      /var/opt/FJSVccm/micc/database

      root (superuser)

      root

      755

      Other than above

      root (superuser)

      bin

      755

      Linux

      /etc/opt/FJSVccm/accc/etc

      root (superuser)

      root

      644

      Other than above

      root (superuser)

      root

      755

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

  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.

    # /opt/FJSVesflm/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.

    1. Delete the subdirectories and files under the restore destination directories "/etc/opt/FJSVesfcm/conf/report", "/etc/opt/FJSVesfcm/conf/scheduler", and "/var/opt/FJSVesfcm/report".
      However, do not delete the restore destination directories themselves.

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

      If the restore destination directories do not exist, create them with the following owner, group, and access privilege.

      OS Type

      Owner

      Group

      Access Privilege

      Solaris OS
      Linux

      root (superuser)

      root

      755

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

  14. Restore the files related to the Automated Storage Tiering function.

    Restore is not required if there are no subdirectories or files.

    1. Delete the subdirectories and files under the restore destination directories "/etc/opt/FJSVssast/data" and "/var/opt/FJSVssast/data".
      However, do not delete the restore destination directories themselves.

      # rm -rf /etc/opt/FJSVssast/data/*
# rm -rf /var/opt/FJSVssast/data/*

      If the restore destination directories do not exist, create them with the following owner, group, and access privilege.

      OS Type

      Owner

      Group

      Access Privilege

      Solaris OS

      root (superuser)

      sys

      755

      Linux

      root (superuser)

      root

      755

    2. Copy the subdirectories and files from the backup location.

      # cp -Rp $BAK_DIR/etc/opt/FJSVssast/data/* /etc/opt/FJSVssast/data/
# cp -Rp $BAK_DIR/var/opt/FJSVssast/data/* /var/opt/FJSVssast/data/

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

    1. Delete the subdirectories and files under the restore destination directory "/etc/opt/FJSVesfcm/conf/qos".
      However, do not delete the restore destination directory itself.

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

      If the restore destination directory does not exist, create it with the following owner, group, and access privilege.

      OS Type

      Owner

      Group

      Access Privilege

      Solaris OS
      Linux

      root (superuser)

      root

      755

    2. Copy the subdirectories and files from the backup location.

      # cp -p $BAK_DIR/etc/opt/FJSVesfcm/conf/qos/* /etc/opt/FJSVesfcm/conf/qos/

  16. Execute the following shell script to start ETERNUS SF Manager services.

    # /opt/FJSVesfcm/bin/startesf.sh
11.1.1.3.2 Restoring Solaris OS/Linux 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:

    • For the Solaris/RHEL5/RHEL6 environment

      # /etc/init.d/startSFmanager start-postgres

    • For the RHEL7 environment

      # /opt/FJSVesfcm/bin/startSFmanager start-postgres

  4. Perform steps 3 and step 5 to 15 of "11.1.1.3.1 Restoring Solaris OS/Linux 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:

    • For the Solaris/RHEL5/RHEL6 environment

      # /etc/init.d/startSFmanager stop-postgres

    • For the RHEL7 environment

      # /opt/FJSVesfcm/bin/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 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. Stop the ETERNUS VASA Provider.

    If using the ETERNUS VASA Provider, open the Service Control Manager and stop the following service.

    • ETERNUS Information Provider

  4. Restore the backup data.

    1. Execute the following command. Specify the default value 15432 to portNumber, however, if you have changed the port number, specify the changed port number to portNumber.

      > $INS_DIR\Common\sys\postgres\bin\psql -U esfpostgres -p portNumber postgres

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

      master01!
drop database esfdb;
\q

    2. Execute the following command to restore the backup data. Specify the default value 15432 to portNumber, however, if you have changed the port number, specify the changed port number to portNumber. 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 portNumber
 -f $BAK_DIR\Common\fileName postgres

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

      master01!

  5. Execute the following batch to stop the ETERNUS SF Manager services.

    > $INS_DIR\Common\bin\Stop_ESFservice.bat

    Information

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

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

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

    1. Using Explorer or a similar program, delete the subdirectories and files under the following restore destination directories.
      However, do not delete the restore destination directories themselves.

      • $TMP_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\perfconf

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

      If the restore destination directories do not exist, create them.

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

    3. Using Explorer or a similar program, copy the subdirectories and files under the following directories from their backup location.

      Copy Source Directory

      Copy Destination Directory

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

      $TMP_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\perfconf

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

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

  7. Restore the files related to the capacity management function.

    This step can be skipped if you are not backing up the files related to the capacity management function.

    1. Using Explorer or a similar program, delete the subdirectories and files under the following restore destination directories.
      However, do not delete the restore destination directories themselves.

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

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

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

      If the restore destination directories do not exist, create them.

    2. Using Explorer or a similar program, copy the subdirectories and files under the following directories from their backup location.

      Copy Source Directory

      Copy Destination Directory

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

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

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

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

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

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

  8. Restore the other files which can be customized.

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

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

    2. Check whether the $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\eventmail directory exist.
      If the directory does not exist, create it.

    3. Using Explorer or a similar program, copy the subdirectories and files under 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

  9. Restore the SNMP Trap XML definition files.

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

    1. Check whether the $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\snmpth directory exist.
      If the directory does not exist, create it.

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

  10. Restore the device polling setting files.

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

    1. Check whether the $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\devicepolling directory exist.
      If the directory does not exist, create it.

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

  11. Restore the polling service setting file.

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

    1. Check whether the $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\polling directory exist.
      If the directory does not exist, create it.

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

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

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

    Perform this step only if you are using the Advanced Copy function.

    1. Using Explorer or a similar program, delete the files under 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

    2. Check whether the following restore destination directories exist.
      If the directories do not exist, create them.

      • $ENV_DIR\CCM\etc

      • $ENV_DIR\CCM\etc\db

      • $ENV_DIR\CCM\etc\db\cg

      • $ENV_DIR\CCM\etc\prop

      • $TMP_DIR\CCM\var\micc\database

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

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

    5. Using Explorer or a similar program, copy the files under 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

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

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

    1. Delete the subdirectories and files under the following restore destination directory.
      However, do not delete the restore destination directory itself.

      • $TMP_DIR\Common\var\report

      If the restore destination directory does not exist, create it.

    2. Check whether the following restore destination directories exist.
      If the directories do not exist, create them.

      • $ENV_DIR\Common\etc\report

      • $ENV_DIR\Common\etc\scheduler

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

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

  16. Restore the files related to the Automated Storage Tiering function.

    Restore is not required if there are no subdirectories or files.

    1. Delete the subdirectories and files under the following restore destination directories.
      However, do not delete the restore destination directories themselves.

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

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

      If the restore destination directories do not exist, create them.

    2. Using Explorer or a similar program, copy the subdirectories and files under the following directories from their backup location.

      Copy Source Directory

      Copy Destination Directory

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

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

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

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

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

    1. Check whether the following restore destination directory exists.
      If the directory does not exist, create it.

      • $ENV_DIR\Common\etc\qos

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

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

    > $INS_DIR\Common\bin\Start_ESFservice.bat

  19. Start the ETERNUS VASA Provider.

    To use the ETERNUS VASA Provider, open the Service Control Manager and start the following service.

    • ETERNUS Information Provider

  20. Restore the VMware vSphere Virtual Volumes environment.

    Perform the following procedure only when using the VMware vSphere Virtual Volumes function.

    1. Reloading the configuration of ETERNUS Disk Storage system
      Perform the Reload Conf. operation for all of the ETERNUS Disk storage systems using the VMware vSphere Virtual Volumes function from Web Console.

    2. Retrieving the ETERNUS Disk storage system configuration Information
      Execute the following command to retrieve the configuration information related to the VMware vSphere Virtual Volumes function from the ETERNUS Disk storage system.

      > $INS_DIR\Common\bin\esfadm esfdata restore -all

      This command may take some time to complete.

11.1.1.3.4 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 4 and step 6 to 17 of "11.1.1.3.3 Restoring Windows Manager" on the primary node.

    Directory description in "11.1.1.3.3 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.

  8. Perform steps 20 of "11.1.1.3.3 Restoring Windows Manager".
    Execute the esfadm esfdata command on the primary node.

PreviousNext
Copyright 2013-2019 FUJITSU LIMITED