If any problem occurs in a system that uses this software, collect troubleshooting information according to "D.1 Troubleshooting information".
Perform the backup according to the procedure shown below, in which the backup destination directory is described as "backup_location". For details about backup in a cluster environment, refer to "9.1.1.2.2 Backup of Solaris OS Manager (cluster environment)".
Stop the Manager.
# /opt/FJSVssmgr/sbin/managerctl stop
Back up device management information.
For ordinary backup tasks, perform "Backing up device management information". For version upgrading from older versions, perform "Version upgrading from older versions".
Create a backup directory.
# mkdir -p backup_location/var/opt/FJSVssmgr/current/opencimom/logrCopy files to the backup location.
# cp -Rp /var/opt/FJSVssmgr/current/opencimom/logr/* backup_location/var/opt/FJSVssmgr/current/opencimom/logr/
Use cimbackup.sh to back up the device management information. For details on this file, refer to "Appendix G Version Upgrade Tool".
Create a backup directory.
# mkdir -p backup_location/logr
Move to the directory that contains cimbackup.sh, then execute cimbackup.sh as follows:
# ./cimbackup.sh backup_location/logr
Back up essential files.
Create the backup directories.
# mkdir -p backup_location/etc/opt/FJSVtrccb/2.0 # mkdir -p backup_location/var/opt/FJSVtrccb/2.0/ac # mkdir -p backup_location/var/opt/FJSVtrccb/2.0/db # mkdir -p backup_location/var/opt/FJSVtrccb/2.0/sr # mkdir -p backup_location/var/opt/FJSVssmgr/current # mkdir -p backup_location/var/opt/FJSVssmgr/current/vsccompose
Copy the subdirectories and files to the backup location.
# cp -Rp /etc/opt/FJSVtrccb/2.0/* backup_location/etc/opt/FJSVtrccb/2.0/ # cp -Rp /var/opt/FJSVtrccb/2.0/ac/* backup_location/var/opt/FJSVtrccb/2.0/ac/ # cp -Rp /var/opt/FJSVtrccb/2.0/db/* backup_location/var/opt/FJSVtrccb/2.0/db/ # cp -Rp /var/opt/FJSVtrccb/2.0/sr/* backup_location/var/opt/FJSVtrccb/2.0/sr/ # cp -Rp /var/opt/FJSVssmgr/current/vsccompose/* backup_location/var/opt/FJSVssmgr/current/vsccompose/ # cp -p /var/opt/FJSVssmgr/current/systemevent.csv backup_location/var/opt/FJSVssmgr/current/
If there are no subdirectories or files, backup is unnecessary.
Back up files that are related to the performance management function.
If you are not using the performance management function, this step is unnecessary.
Create the backup directories.
# mkdir -p backup_location/etc/opt/FJSVssmgr/current # mkdir -p backup_location/var/opt/FJSVssmgr/current/perf
Copy the subdirectories and files to the backup location.
# cp -p /etc/opt/FJSVssmgr/current/perf.conf backup_location/etc/opt/FJSVssmgr/current/ # cp -Rp /var/opt/FJSVssmgr/current/perf/* backup_location/var/opt/FJSVssmgr/current/perf/
Back up files for which the maximum memory that can be used is customized.
If the maximum memory that can be used is not customized, backup is unnecessary.
Create the backup directory.
# mkdir -p backup_location/opt/FJSVssmgr/bin
Copy the files to the backup location.
# cp -p /opt/FJSVssmgr/bin/manager.ini backup_location/opt/FJSVssmgr/bin/
Back up other files that can be customized.
If there are files that are not customized, backup is unnecessary. Backup is also unnecessary if these files do not exist.
Create the backup directory.
# mkdir -p backup_location/etc/opt/FJSVssmgr/current
Copy the files to the backup location.
# cp -p /etc/opt/FJSVssmgr/current/sanma.conf backup_location/etc/opt/FJSVssmgr/current/ # cp -p /etc/opt/FJSVssmgr/current/ssmgr.conf backup_location/etc/opt/FJSVssmgr/current/ # cp -p /etc/opt/FJSVssmgr/current/trapop.sh backup_location/etc/opt/FJSVssmgr/current/ # cp -p /etc/opt/FJSVssmgr/current/traprm.sh backup_location/etc/opt/FJSVssmgr/current/ # cp -p /etc/opt/FJSVssmgr/current/VscCommitScript backup_location/etc/opt/FJSVssmgr/current/ # cp -p /etc/opt/FJSVssmgr/current/FJSVssvsc.ini backup_location/etc/opt/FJSVssmgr/current/
Back up the SNMP trap XML definition file.
If you have not customized the SNMP trap XML definition file, this step is unnecessary.
In the example shown below, SNMP trap XML definition file "1_3_6_1_1588_2_1_1_1.xml" has been customized. Back up each customized file separately, as shown in the example.
Create the backup directory.
# mkdir -p backup_location/etc/opt/FJSVssmgr/current/snmpth
Copy the files to the backup location.
# cp -p /etc/opt/FJSVssmgr/current/snmpth/1_3_6_1_1588_2_1_1_1.xml backup_location/etc/opt/FJSVssmgr/current/snmpth/
Back up the device polling settings file.
If you have not customized the device polling settings file, this step is unnecessary.
In the example shown below, the device polling settings file "DP_config.xml" has been customized. Back up each customized file separately, as shown in the example.
Create the backup directory.
# mkdir -p backup_location/etc/opt/FJSVssmgr/current/devicepolling
Copy the files to the backup location.
# cp -p /etc/opt/FJSVssmgr/current/devicepolling/DP_config.xml backup_location/etc/opt/FJSVssmgr/current/devicepolling/
Back up the polling service setting file.
If this file has not been customized, then this step is unnecessary.
To backup the file, follow the steps below:
Create the backup directory.
# mkdir -p backup_location/etc/opt/FJSVssmgr/current/polling
Copy the file to the backup location.
# cp -p /etc/opt/FJSVssmgr/current/polling/pollingService.xml backup_location/etc/opt/FJSVssmgr/current/polling/
Restart the Manager.
# /opt/FJSVssmgr/sbin/managerctl start
Stop all cluster services that the Manager belongs to.
Mount the shared disk on the primary node.
Perform steps 2, 3, 4, 6, 7 and 8 of "9.1.1.2.1 Backup of Solaris OS Manager" on the primary node.
Perform step 5 of "9.1.1.2.1 Backup of Solaris OS Manager" on both nodes.
Unmount the shared disk that was mounted in step 2.
Start all cluster services that the Manager belongs to.
Perform the backup according to the procedure shown below, in which the backup destination directory is described as "backup_location". Refer to "9.1.1.2.4 Backup of Linux Manager (cluster environment)" for details on backing up in a cluster environment.
Stop the manager.
# /opt/FJSVssmgr/sbin/managerctl stop
Back up device management information.
For ordinary backup tasks, perform "Backing up device management information". For version upgrading from older versions, perform "Version upgrading from older versions".
Create a backup directory.
# mkdir -p backup_location/var/opt/FJSVssmgr/current/opencimom/logr
Copy files to the backup location.
# cp -Rp /var/opt/FJSVssmgr/current/opencimom/logr/* backup_location/var/opt/FJSVssmgr/current/opencimom/logr/
Use cimbackup.sh to back up the device management information. For details on this file, refer to "Appendix G Version Upgrade Tool".
Create a backup directory.
# mkdir -p backup_location/logr
Move to the directory that contains cimbackup.sh, then execute cimbackup.sh as follows:
# ./cimbackup.sh backup_location/logr
Back up essential files.
Create a backup directories.
# mkdir -p backup_location/etc/opt/FJSVtrccb/2.0 # mkdir -p backup_location/var/opt/FJSVtrccb/2.0/ac # mkdir -p backup_location/var/opt/FJSVtrccb/2.0/db # mkdir -p backup_location/var/opt/FJSVtrccb/2.0/sr # mkdir -p backup_location/var/opt/FJSVssmgr/current # mkdir -p backup_location/var/opt/FJSVssmgr/current/vsccompose
Copy the subdirectories and files to the backup location.
# cp -Rp /etc/opt/FJSVtrccb/2.0/* backup_location/etc/opt/FJSVtrccb/2.0/ # cp -Rp /var/opt/FJSVtrccb/2.0/ac/* backup_location/var/opt/FJSVtrccb/2.0/ac/ # cp -Rp /var/opt/FJSVtrccb/2.0/db/* backup_location/var/opt/FJSVtrccb/2.0/db/ # cp -Rp /var/opt/FJSVtrccb/2.0/sr/* backup_location/var/opt/FJSVtrccb/2.0/sr/ # cp -Rp /var/opt/FJSVssmgr/current/vsccompose/* backup_location/var/opt/FJSVssmgr/current/vsccompose/ # cp -p /var/opt/FJSVssmgr/current/systemevent.csv backup_location/var/opt/FJSVssmgr/current/
If there are no subdirectories or files, backup is unnecessary.
Back up the files relating to performance management functionality. When performance management functionality is not used, this procedure is unnecessary.
Create the backup directories.
# mkdir -p backup_location/etc/opt/FJSVssmgr/current # mkdir -p backup_location/var/opt/FJSVssmgr/current/perf
Copy the subdirectories and files to the the backup location.
# cp -p /etc/opt/FJSVssmgr/current/perf.conf backup_location/etc/opt/FJSVssmgr/current/ # cp -Rp /var/opt/FJSVssmgr/current/perf/* backup_location/var/opt/FJSVssmgr/current/perf/
Back up the file created when memory use is customized (that is, when the maximum amount of memory that can be used is defined). If memory usage has not been customized this backup is not necessary as the file will not exist.
Create the backup directory.
# mkdir -p backup_location/opt/FJSVssmgr/bin
Copy the file to the backup location.
# cp -p /opt/FJSVssmgr/bin/manager.ini backup_location/opt/FJSVssmgr/bin/
Back up other files created as a result of customization.The following procedure shows all customization files; however these files are only created when settings are made therefore some may not exist for the backup procedure.
Create the backup directory.
# mkdir -p backup_location/etc/opt/FJSVssmgr/current
Copy the files to the backup location.
# cp -p /etc/opt/FJSVssmgr/current/sanma.conf backup_location/etc/opt/FJSVssmgr/current/ # cp -p /etc/opt/FJSVssmgr/current/ssmgr.conf backup_location/etc/opt/FJSVssmgr/current/ # cp -p /etc/opt/FJSVssmgr/current/trapop.sh backup_location/etc/opt/FJSVssmgr/current/ # cp -p /etc/opt/FJSVssmgr/current/traprm.sh backup_location/etc/opt/FJSVssmgr/current/ # cp -p /etc/opt/FJSVssmgr/current/VscCommitScript backup_location/etc/opt/FJSVssmgr/current/ # cp -p /etc/opt/FJSVssmgr/current/FJSVssvsc.ini backup_location/etc/opt/FJSVssmgr/current/
Back up the SNMP trap XML definition file.
This step is only required if customizations have been performed.
In the example shown below, the existence of the SNMP trap XML definition file "1_3_6_1_1588_2_1_1_1.xml" indicates SNMP has been customized. Back up each file separately, as shown in the example.
Create the backup directory.
# mkdir -p backup_location/etc/opt/FJSVssmgr/current/snmpth
Copy the file to thebackup location.
# cp -p /etc/opt/FJSVssmgr/current/snmpth/1_3_6_1_1588_2_1_1_1.xml backup_location/etc/opt/FJSVssmgr/current/snmpth/
Back up the device polling settings file.
This step is only required if customizations have been performed.
In the example shown below, the existence of the device polling settings file "DP_config.xml" indicates that device polling has been customized. Back up each customized file separately, as shown in the example.
Create the backup directory.
# mkdir -p backup_location/etc/opt/FJSVssmgr/current/devicepolling
Copy the files to the backup location.
# cp -p /etc/opt/FJSVssmgr/current/devicepolling/DP_config.xml backup_location/etc/opt/FJSVssmgr/current/devicepolling/
Back up the polling service setting file.
If this file has not been customized, then this step is unnecessary.
To backup the file, follow the steps below:
Create the backup directory.
# mkdir -p backup_location/etc/opt/FJSVssmgr/current/polling
Copy the file to the backup location.
# cp -p /etc/opt/FJSVssmgr/current/polling/pollingService.xml backup_location/etc/opt/FJSVssmgr/current/polling/
Restart the Manager.
# /opt/FJSVssmgr/sbin/managerctl start
Stop all cluster services that relate to the Manager.
Mount a shared disk on the primary node.
Perform steps 2, 3, 4,6,7 and 8 of "9.1.1.2.3 Backup of Linux Manager" on the primary node.
Perform step 5 of "9.1.1.2.3 Backup of Linux Manager" on both nodes.
Un-mount the disk mounted in step 2.
Restart all cluster services that relate to the Manager.
Perform the backup according to the procedure shown below.
Information
About description in the procedure
$BAK_DIR means the backup destination directory.
$INS_DIR means "Program Directory" specified at the Manager installation.
$ENV_DIR means "Environment Directory" specified at the Manager installation.
$TMP_DIR means "Work Directory" specified at the Manager installation.
Stop the Manager.
Go to [Control Panel] - [Administrative Tools] - [Services], select "ETERNUS SF Storage Cruiser Manager" and stop the service.
Back up device management information.
For ordinary backup tasks, perform "Backing up device management information". For version upgrading from older versions, perform "Version upgrading from older versions".
Using Explorer, create the following backup directory:
$BAK_DIR\Manager\var\opt\FJSVssmgr\current\opencimom\logr
Using Explorer, copy the subdirectories and files in the following directories to the backup location.
Source directory | Destination directory |
|---|---|
$TMP_DIR\Manager\var\opt\FJSVssmgr\current\opencimom\logr | $BAK_DIR\Manager\var\opt\FJSVssmgr\current\opencimom\logr |
Use cimbackup.bat to back up the device management information. For details on this file, refer to "Appendix G Version Upgrade Tool".
Using Explorer, create the following backup directory:
$BAK_DIR\Manager\var\opt\FJSVssmgr\current\opencimom\logr
Move to the directory that contains cimbackup.bat, then execute cimbackup.bat as follows:
cimbackup.bat "$BAK_DIR\logr"
Back up essential files.
If there are no subdirectories or files, backup is unnecessary.
Using Explorer, create the following backup directories:
$BAK_DIR\Manager\etc\opt\FJSVtrccb\2.0
$BAK_DIR\Manager\var\opt\FJSVtrccb\2.0\ac
$BAK_DIR\Manager\var\opt\FJSVtrccb\2.0\db
$BAK_DIR\Manager\var\opt\FJSVtrccb\2.0\sr
$BAK_DIR\Manager\var\opt\FJSVssmgr\current
$BAK_DIR\Manager\var\opt\FJSVssmgr\current\vsccompose
Using Explorer, copy the subdirectories and files in the following directories to the backup location.
Source directory | Destination directory |
|---|---|
$ENV_DIR\Manager\etc\opt\FJSVtrccb\2.0 | $BAK_DIR\Manager\etc\opt\FJSVtrccb\2.0 |
$TMP_DIR\Manager\var\opt\FJSVtrccb\2.0\ac | $BAK_DIR\Manager\var\opt\FJSVtrccb\2.0\ac |
$TMP_DIR\Manager\var\opt\FJSVtrccb\2.0\db | $BAK_DIR\Manager\var\opt\FJSVtrccb\2.0\db |
$TMP_DIR\Manager\var\opt\FJSVtrccb\2.0\sr | $BAK_DIR\Manager\var\opt\FJSVtrccb\2.0\sr |
$TMP_DIR\Manager\var\opt\FJSVssmgr\current\vsccompose | $BAK_DIR\Manager\var\opt\FJSVssmgr\current\vsccompose |
Using Explorer, copy the following file to the backup location.
Source file | Destination directory |
|---|---|
$TMP_DIR\Manager\var\opt\FJSVssmgr\current\systemevent.csv | $BAK_DIR\Manager\var\opt\FJSVssmgr\current |
Back up files that are related to the performance management function.
If you are not using the performance management function, this step is unnecessary.
Using Explorer, create the following backup directories:
$BAK_DIR\Manager\etc\opt\FJSVssmgr\current
$BAK_DIR\Manager\var\opt\FJSVssmgr\current\perf
Using Explorer, copy the following files to the backup location.
Source file | Destination directory |
|---|---|
$ENV_DIR\Manager\etc\opt\FJSVssmgr\current\perf.conf | $BAK_DIR\Manager\etc\opt\FJSVssmgr\current |
Using Explorer, copy the subdirectories and files in the following directories to the backup location.
Source directory | Destination directory |
|---|---|
$TMP_DIR\Manager\var\opt\FJSVssmgr\current\perf | $BAK_DIR\Manager\var\opt\FJSVssmgr\current\perf |
Back up files that can be customized.
If there are files that are not customized, backup is unnecessary. Backup is also unnecessary if these files do not exist.
Using Explorer, create the following backup directories:
$BAK_DIR\Manager\opt\FJSVssmgr\bin
$BAK_DIR\Manager\etc\opt\FJSVssmgr\current
Using Explorer, copy the following files to the backup location.
Source file | Destination directory |
|---|---|
$INS_DIR\Manager\opt\FJSVssmgr\bin\manager.ini | $BAK_DIR\Manager\opt\FJSVssmgr\bin |
$ENV_DIR\Manager\etc\opt\FJSVssmgr\current\sanma.conf | $BAK_DIR\Manager\etc\opt\FJSVssmgr\current |
$ENV_DIR\Manager\etc\opt\FJSVssmgr\current\ssmgr.conf | |
$ENV_DIR\Manager\etc\opt\FJSVssmgr\current\trapop.bat | |
$ENV_DIR\Manager\etc\opt\FJSVssmgr\current\traprm.bat | |
$ENV_DIR\Manager\etc\opt\FJSVssmgr\current\VscCommitScript.bat | |
$ENV_DIR\Manager\etc\opt\FJSVssmgr\current\FJSVssvsc.ini |
Back up the SNMP trap XML definition file.
If you have not customized the SNMP trap XML definition file, this step is unnecessary.
In the example shown below, SNMP trap XML definition file "1_3_6_1_1588_2_1_1_1.xml" has been customized. Back up each customized file separately, as shown in the example.
Using Explorer, create the following backup directory:
$BAK_DIR\Manager\etc\opt\FJSVssmgr\current\snmpth
Using Explorer, copy the file to the backup location.
Source file | Destination directory |
|---|---|
$ENV_DIR\Manager\etc\opt\FJSVssmgr\current\snmpth\1_3_6_1_1588_2_1_1_1.xml | $BAK_DIR\Manager\etc\opt\FJSVssmgr\current\snmpth |
Back up the device polling settings file.
If you have not customized the device polling settings file, this step is unnecessary.
In the example shown below, the device polling settings file "DP_config.xml" has been customized. Back up each customized file separately, as shown in the example.
Using Explorer, create the following backup directory:
$BAK_DIR\Manager\etc\opt\FJSVssmgr\current\devicepolling
Using Explorer, copy the file to the backup location.
Source file | Destination directory |
|---|---|
$ENV_DIR\Manager\etc\opt\FJSVssmgr\current\devicepolling\DP_config.xml | $BAK_DIR\Manager\etc\opt\FJSVssmgr\current\devicepolling |
Back up the polling service setting file.
This step is only required if customizations have been performed.
In the example shown below, the existence of the device polling settings file "pollingService.xml" indicates that device polling has been customized. Back up each customized file separately, as shown in the example.
Using Explorer, create the following backup directory:
$BAK_DIR\Manager\etc\opt\FJSVssmgr\current\polling
Using Explorer, copy the file to the backup location.
Source file | Destination directory |
|---|---|
$ENV_DIR\Manager\etc\opt\FJSVssmgr\current\polling\pollingService.xml | $BAK_DIR\Manager\etc\opt\FJSVssmgr\current\polling |
Restart the Manager.
Go to [Control Panel] - [Administrative Tools] - [Services], select "ETERNUS SF Storage Cruiser Manager" and start the service.
Perform restore for the backup performed in "9.1.1.2.1 Backup of Solaris OS Manager" according to the procedure shown below.
To restore after reinstalling the Manager, first complete the entire installation and setup according to the description in "4.1 [Solaris OS] Manager" in the ETERNUS SF Storage Cruiser Installation Guide.
To upgrade from a Manager in a previous version, proceed according to the Notes for each procedure.
For details about restoring in a cluster environment, refer to "9.1.1.3.2 Restoring Solaris OS Manager (cluster environment)".
Stop the Manager.
# /opt/FJSVssmgr/sbin/managerctl stop
Restore the device management information.
For ordinary restoration tasks, perform "Restoring device management information". For version upgrading from older versions, perform "Version Upgrading from older versions".
Delete the subdirectories and files under the restore destination directory displayed below.
Do not delete the restore destination directories. Create them if they do not exist.
# rm -rf /var/opt/FJSVssmgr/current/opencimom/logr/*
Copy the files from the backup directory.
# cp -Rp backup_location/var/opt/FJSVssmgr/current/opencimom/logr/* /var/opt/FJSVssmgr/current/opencimom/logr/
Use cimrestore.sh to restore the device management information. For details on this file, refer to "Appendix G Version Upgrade Tool".
Delete the subdirectories and files under the restore destination directory displayed below.
Do not delete the restore destination directories. Create them if they do not exist.
# rm -rf /var/opt/FJSVssmgr/current/opencimom/logr/*
Move to the directory that contains cimrestore.sh, then execute cimrestore.sh as follows:
# ./cimrestore.sh backup_location/logr
Restore essential files.
Delete the subdirectories and files in the restore destination directories shown below.
Do not delete the restore destination directories themselves. If these directories do not exist, create them.
# rm -rf /etc/opt/FJSVtrccb/2.0/* # rm -rf /var/opt/FJSVtrccb/2.0/ac/* # rm -rf /var/opt/FJSVtrccb/2.0/db/* # rm -rf /var/opt/FJSVtrccb/2.0/sr/* # rm -rf /var/opt/FJSVssmgr/current/vsccompose/*
Please delete systemevent.csv the restoration ahead.
# rm -rf /var/opt/FJSVssmgr/current/systemevent.csv
Copy the subdirectories and files from the backup location.
# cp -Rp backup_location/etc/opt/FJSVtrccb/2.0/* /etc/opt/FJSVtrccb/2.0/ # cp -Rp backup_location/var/opt/FJSVtrccb/2.0/ac/* /var/opt/FJSVtrccb/2.0/ac/ # cp -Rp backup_location/var/opt/FJSVtrccb/2.0/db/* /var/opt/FJSVtrccb/2.0/db/ # cp -Rp backup_location/var/opt/FJSVtrccb/2.0/sr/* /var/opt/FJSVtrccb/2.0/sr/ # cp -Rp backup_location/var/opt/FJSVssmgr/current/vsccompose/* /var/opt/FJSVssmgr/current/vsccompose/ # cp -p backup_location/var/opt/FJSVssmgr/current/systemevent.csv /var/opt/FJSVssmgr/current/
If there are no subdirectories or files, restore is unnecessary.
Restore files that are related to the performance management function.
If you are not using the performance management function, this step is unnecessary.
Delete the subdirectories and files in the restore destination directories shown below.
Do not delete the restore destination directories themselves. If these directories do not exist, create them.
# rm -rf /var/opt/FJSVssmgr/current/perf/*
Copy the subdirectories and files from the backup location.
# cp -p backup_location/etc/opt/FJSVssmgr/current/perf.conf /etc/opt/FJSVssmgr/current/ # cp -Rp backup_location/var/opt/FJSVssmgr/current/perf/* /var/opt/FJSVssmgr/current/perf/
Restore files for which the maximum memory that can be used is customized.
If the maximum memory that can be used is not customized, restore is unnecessary.
Copy the files from the backup location.
# cp -p backup_location/opt/FJSVssmgr/bin/manager.ini /opt/FJSVssmgr/bin/Restore the other files that can be customized.
If there are files that are not customized, restore is unnecessary. Restore is also unnecessary if the files do not exist.
Copy the files from the backup location.
# cp -p backup_location/etc/opt/FJSVssmgr/current/sanma.conf /etc/opt/FJSVssmgr/current/ # cp -p backup_location/etc/opt/FJSVssmgr/current/ssmgr.conf /etc/opt/FJSVssmgr/current/ # cp -p backup_location/etc/opt/FJSVssmgr/current/trapop.sh /etc/opt/FJSVssmgr/current/ # cp -p backup_location/etc/opt/FJSVssmgr/current/traprm.sh /etc/opt/FJSVssmgr/current/ # cp -p backup_location/etc/opt/FJSVssmgr/current/VscCommitScript /etc/opt/FJSVssmgr/current/ # cp -p backup_location/etc/opt/FJSVssmgr/current/FJSVssvsc.ini /etc/opt/FJSVssmgr/current/
Restore the SNMP trap XML definition file.
If you have not customized the SNMP trap XML definition file, this step is unnecessary.
Copy the SNMP trap XML definition file from the backup location.
# cp -p backup_location/etc/opt/FJSVssmgr/current/snmpth/*.xml /etc/opt/FJSVssmgr/current/snmpth/Note
Do not copy the file if you are upgrading from a previous version. Instead, reflect the contents of the customization in the previous version, according to the description in "C.6 SNMP Trap XML Definition File".
Restore the device polling settings file.
If you have not customized the device polling settings file, this step is unnecessary.
Copy the device polling settings file from the backup location.
# cp -p backup_location/etc/opt/FJSVssmgr/current/devicepolling/*.xml /etc/opt/FJSVssmgr/current/devicepolling/Note
Do not copy the file if you are upgrading from a previous version. Instead, reflect the contents of the customization in the previous version, according to the description in "C.10 Device Polling Setting File".
Restore the polling service setting file.
If this file has not been customized, then this step is unnecessary.
Copy the file from the backup location.
# cp -p backup_location/etc/opt/FJSVssmgr/current/polling/*.xml /etc/opt/FJSVssmgr/current/polling/
Note
Do not copy the file if you are upgrading from an older version. Instead, reflect the customization of the older version file. For details on how to do that, refer to "C.13 Polling Service Setting File".
Restart the Manager.
# /opt/FJSVssmgr/sbin/managerctl start
Perform restore for the backup performed in "9.1.1.2.2 Backup of Solaris OS Manager (cluster environment)" according to the procedure shown below.
To restore after reinstalling the Manager, first complete the entire installation and setup according to the description in "Appendix A High-availability admin servers" in the ETERNUS SF Storage Cruiser Installation Guide.
Stop all cluster services that the Manager belongs to.
Mount the shared disk on the primary node.
Perform steps 2, 3, 4, 6, 7and 8 of "9.1.1.3.1 Restoring Solaris OS Manager" on the primary node.
Perform step 5 of "9.1.1.3.1 Restoring Solaris OS Manager" on both nodes.
Unmount the shared disk that was mounted in step 2.
Start all cluster services that the Manager belongs to.
The following procedure explains the process to restore files that were backed up using the procedure described above in "9.1.1.2.3 Backup of Linux Manager".
If the manager is to be restored by a reinstallation process all of the steps outlined in "4.2 [Linux] Manager" in the ETERNUS SF Storage Cruiser Installation Guide must be followed.
If the manager is to be restored by an upgrade process the procedures applicable to the upgrade must be followed.
For details about restoring in a cluster environment, refer to "9.1.1.3.4 Restoring Linux Manager (cluster environment)".
Execute the following command to stop the Manager.
# /opt/FJSVssmgr/sbin/managerctl stop
Restore the device management information.
For ordinary restoration tasks, perform "Restoring device management information". For version upgrading from older versions, perform "Version Upgrading from older versions".
Delete the subdirectories and files under the restore destination directory displayed below.
Do not delete the restore destination directories. Create them if they do not exist.
# rm -rf /var/opt/FJSVssmgr/current/opencimom/logr/*
Copy the files from the backup directory.
# cp -Rp backup_location/var/opt/FJSVssmgr/current/opencimom/logr/* /var/opt/FJSVssmgr/current/opencimom/logr/
Use cimrestore.sh to restore the device management information. For details on this file, refer to "Appendix G Version Upgrade Tool".
Delete the subdirectories and files under the restore destination directory displayed below.
Do not delete the restore destination directories. Create them if they do not exist.
# rm -rf /var/opt/FJSVssmgr/current/opencimom/logr/*
Move to the directory that contains cimrestore.sh, then execute cimrestore.sh as follows:
# ./cimrestore.sh backup_location/logr
Ressential files.
Delete the subdirectories and files in the restore destination directories shown below.
Do not delete the restore destination directories themselves. If these directories do not exist, create them.
# rm -rf /etc/opt/FJSVtrccb/2.0/* # rm -rf /var/opt/FJSVtrccb/2.0/ac/* # rm -rf /var/opt/FJSVtrccb/2.0/db/* # rm -rf /var/opt/FJSVtrccb/2.0/sr/* # rm -rf /var/opt/FJSVssmgr/current/vsccompose/*
Delete the restore destination files.
# rm -rf /var/opt/FJSVssmgr/current/systemevent.csv
Copy the subdirectories and files from the backup location.
# cp -Rp backup_location/etc/opt/FJSVtrccb/2.0/* /etc/opt/FJSVtrccb/2.0/ # cp -Rp backup_location/var/opt/FJSVtrccb/2.0/ac/* /var/opt/FJSVtrccb/2.0/ac/ # cp -Rp backup_location/var/opt/FJSVtrccb/2.0/db/* /var/opt/FJSVtrccb/2.0/db/ # cp -Rp backup_location/var/opt/FJSVtrccb/2.0/sr/* /var/opt/FJSVtrccb/2.0/sr/ # cp -Rp backup_location/var/opt/FJSVssmgr/current/vsccompose/* /var/opt/FJSVssmgr/current/vsccompose/ # cp -p backup_location/var/opt/FJSVssmgr/current/systemevent.csv /var/opt/FJSVssmgr/current/
Only files and subdirectories created during the backup procedure will be available to restore.
Restore files that are related to the performance management function.
This step is only required if the performance management function file was backed up.
Delete the subdirectories and files in the restore destination directories shown below.
Do not delete the restore destination directories themselves. If these directories do not exist, create them.
Copy the subdirectories and files from the backup location.
# cp -p backup_location/etc/opt/FJSVssmgr/current/perf.conf /etc/opt/FJSVssmgr/current/ # cp -Rp backup_location/var/opt/FJSVssmgr/current/perf/* /var/opt/FJSVssmgr/current/perf/
Restore files for which the maximum memory that can be used is customized.
This step is only required if the file was backed up.
Copy the files from the backup location.
# cp -p backup_location/opt/FJSVssmgr/bin/manager.ini /opt/FJSVssmgr/bin/
Restore the other files that can be customized.
This step is only required if customization had taken place and the relative file was backed up.
Copy the files from the backup location.
# cp -p backup_location/etc/opt/FJSVssmgr/current/sanma.conf /etc/opt/FJSVssmgr/current/ # cp -p backup_location/etc/opt/FJSVssmgr/current/ssmgr.conf /etc/opt/FJSVssmgr/current/ # cp -p backup_location/etc/opt/FJSVssmgr/current/trapop.sh /etc/opt/FJSVssmgr/current/ # cp -p backup_location/etc/opt/FJSVssmgr/current/traprm.sh /etc/opt/FJSVssmgr/current/ # cp -p backup_location/etc/opt/FJSVssmgr/current/VscCommitScript /etc/opt/FJSVssmgr/current/ # cp -p backup_location/etc/opt/FJSVssmgr/current/FJSVssvsc.ini /etc/opt/FJSVssmgr/current/
Restore the SNMP trap XML definition file.
This step is only required if the definition file was backed up.
Copy the SNMP trap XML definition file from the backup location.
# cp -p backup_location/etc/opt/FJSVssmgr/current/snmpth/*.xml /etc/opt/FJSVssmgr/current/snmpth/
Note
Do not copy the file if you are upgrading from a previous version, refer to "C.6 SNMP Trap XML Definition File" in the manual for that version.
Restore the device polling settings file.
This step is only necessary if the file was backed up.
Copy the device polling settings file from the backup location.
# cp -p backup_location/etc/opt/FJSVssmgr/current/devicepolling/*.xml /etc/opt/FJSVssmgr/current/devicepolling/
Note
Do not copy the file if you are upgrading from a previous version, refer to "C.10 Device Polling Setting File" in the manual for that version.
Restore the polling service setting file.
If this file has not been customized, then this step is unnecessary.
Copy the file from the backup location.
# cp -p backup_location/etc/opt/FJSVssmgr/current/polling/*.xml /etc/opt/FJSVssmgr/current/polling/
Note
Do not copy the file if you are upgrading from an older version. Instead, reflect the customization of the older version file. For details on how to do that, refer to "C.13 Polling Service Setting File".
Restart the Manager.
# /opt/FJSVssmgr/sbin/managerctl start
The following procedure explains the process to restore files that were backed up using the procedure described above in "9.1.1.2.4 Backup of Linux Manager (cluster environment)".
If the manager is to be restored by a reinstallation process all of the steps outlined in "4.2 [Linux] Manager" in the ETERNUS SF Storage Cruiser Installation Guide must be followed.
Stop all cluster services that relate to the Manager.
Mount a shared disk on the primary node.
Perform steps 2, 3, 4, 6, 7, and 8 of "9.1.1.3.3 Restoring Linux Manager" on the primary node.
Perform step 5 of "9.1.1.3.3 Restoring Linux Manager" on both nodes.
Un-mount the shared disk that was mounted in step 2.
Start all cluster services that relate to the Manager.
Perform restore for the backup performed in "9.1.1.2.5 Backup of Windows Manager" according to the procedure shown below.
To restore after reinstalling the Manager, first complete the entire installation and setup according to the description in "4.3 [Windows] Manager" in the ETERNUS SF Storage Cruiser Installation Guide.
To upgrade from a Manager in a previous version, proceed according to the Notes for each procedure.
Information
About description in the procedure
$BAK_DIR means the backup destination directory.
$INS_DIR means "Program Directory" specified at the Manager installation.
$ENV_DIR means "Environment Directory" specified at the Manager installation.
$TMP_DIR means "Work Directory" specified at the Manager installation.
Stop the Manager.
Go to [Control Panel] - [Administrative Tools] - [Services], select "ETERNUS SF Storage Cruiser Manager" and stop the service.
Restore the device management information.
For ordinary restoration tasks, perform "Restoring device management information". For version upgrading from older versions, perform "Version Upgrading from older versions".
By using Explorer, delete the subdirectories and files in the restore destination directories shown below.
Do not delete the restore destination directories themselves. If these directories do not exist, create them.
$TMP_DIR\Manager\var\opt\FJSVssmgr\current\opencimom\logr
By using Explorer, copy the subdirectories and files from the backup location.
Source directory | Destination directory |
|---|---|
$BAK_DIR\Manager\var\opt\FJSVssmgr\current\opencimom\logr | $TMP_DIR\Manager\var\opt\FJSVssmgr\current\opencimom\logr |
Use cimrestore.bat to restore the device management information. For details on this file, refer to "Appendix G Version Upgrade Tool".
Delete the subdirectories and files under the restore destination directory displayed below.
Do not delete the restore destination directories. Create them if they do not exist.
$TMP_DIR\Manager\var\opt\FJSVssmgr\current\opencimom\logr
Move to the directory that contains cimrestore.sh, then execute cimrestore.sh as follows:
cimrestore.bat "$BAK_DIR\logr"
Restore essential files.
By using Explorer, delete the subdirectories and files in the restore destination directories shown below.
Do not delete the restore destination directories themselves. If these directories do not exist, create them.
$ENV_DIR\Manager\etc\opt\FJSVtrccb\2.0
$TMP_DIR\Manager\var\opt\FJSVtrccb\2.0\ac
$TMP_DIR\Manager\var\opt\FJSVtrccb\2.0\db
$TMP_DIR\Manager\var\opt\FJSVtrccb\2.0\sr
$TMP_DIR\Manager\var\opt\FJSVssmgr\current\vsccompose
By using Explorer, delete the following file.
$TMP_DIR\Manager\var\opt\FJSVssmgr\current\systemevent.csv
By using Explorer, copy the subdirectories and files from the backup location.
Source directory | Destination directory |
|---|---|
$BAK_DIR\Manager\etc\opt\FJSVtrccb\2.0 | $ENV_DIR\Manager\etc\opt\FJSVtrccb\2.0 |
$BAK_DIR\Manager\var\opt\FJSVtrccb\2.0\ac | $TMP_DIR\Manager\var\opt\FJSVtrccb\2.0\ac |
$BAK_DIR\Manager\var\opt\FJSVtrccb\2.0\db | $TMP_DIR\Manager\var\opt\FJSVtrccb\2.0\db |
$BAK_DIR\Manager\var\opt\FJSVtrccb\2.0\sr | $TMP_DIR\Manager\var\opt\FJSVtrccb\2.0\sr |
$BAK_DIR\Manager\var\opt\FJSVssmgr\current\vsccompose | $TMP_DIR\Manager\var\opt\FJSVssmgr\current\vsccompose |
By using Explorer, copy the following file from the backup location.
Source file | Destination directory |
|---|---|
$BAK_DIR\Manager\var\opt\FJSVssmgr\current\systemevent.csv | $TMP_DIR\Manager\var\opt\FJSVssmgr\current |
If there are no subdirectories or files, restore is unnecessary.
Restore files that are related to the performance management function.
If you are not using the performance management function, this step is unnecessary.
By using Explorer, delete the subdirectories and files in the restore destination directories shown below.
Do not delete the restore destination directories themselves. If these directories do not exist, create them.
$TMP_DIR\Manager\var\opt\FJSVssmgr\current\perf
By using Explorer, copy the following file from the backup location.
Source file | Destination directory |
|---|---|
$BAK_DIR\Manager\etc\opt\FJSVssmgr\current\perf.conf | $ENV_DIR\Manager\etc\opt\FJSVssmgr\current |
By using Explorer, copy the subdirectories and files in the following directories from the backup location.
Source directory | Destination directory |
|---|---|
$BAK_DIR\Manager\var\opt\FJSVssmgr\current\perf | $TMP_DIR\Manager\var\opt\FJSVssmgr\current\perf |
Restore files that can be customized.
If there are files that are not customized, restore is unnecessary. Restore is also unnecessary if the files do not exist.
By using Explorer, copy the following files from the backup location.
Source file | Destination directory |
|---|---|
$BAK_DIR\Manager\opt\FJSVssmgr\bin\manager.ini | $INS_DIR\Manager\opt\FJSVssmgr\bin |
$BAK_DIR\Manager\etc\opt\FJSVssmgr\current\sanma.conf | $ENV_DIR\Manager\etc\opt\FJSVssmgr\current |
$BAK_DIR\Manager\etc\opt\FJSVssmgr\current\ssmgr.conf | |
$BAK_DIR\Manager\etc\opt\FJSVssmgr\current\trapop.bat | |
$BAK_DIR\Manager\etc\opt\FJSVssmgr\current\traprm.bat | |
$BAK_DIR\Manager\etc\opt\FJSVssmgr\current\VscCommitScript.bat | |
$BAK_DIR\Manager\etc\opt\FJSVssmgr\current\FJSVssvsc.ini |
Restore the SNMP trap XML definition file.
If you have not customized the SNMP trap XML definition file, this step is unnecessary.
By using Explorer, copy the SNMP trap XML definition file from the backup location.
Source file | Destination directory |
|---|---|
$BAK_DIR\Manager\etc\opt\FJSVssmgr\current\snmpth\*.xml | $ENV_DIR\Manager\etc\opt\FJSVssmgr\current\snmpth |
Note
Do not copy the file if you are upgrading from a previous version. Instead, reflect the contents of the customization in the previous version, according to the description in "C.6 SNMP Trap XML Definition File".
Restore the device polling settings file.
If you have not customized the device polling settings file, this step is unnecessary.
Using Explorer, copy the device polling settings file from the backup location.
Source file | Destination directory |
|---|---|
$BAK_DIR\Manager\etc\opt\FJSVssmgr\current\devicepolling\DP_config.xml | $ENV_DIR\Manager\etc\opt\FJSVssmgr\current\devicepolling |
Note
Do not copy the file if you are upgrading from a previous version. Instead, reflect the contents of the customization in the previous version, according to the description in "C.10 Device Polling Setting File".
Restore the polling service settings file.
If you have not customized the polling service settings file, this step is unnecessary.
Using Explorer, copy the polling service settings file from the backup location.
Source file | Destination directory |
|---|---|
$BAK_DIR\Manager\etc\opt\FJSVssmgr\current\polling\pollingService.xml | $ENV_DIR\Manager\etc\opt\FJSVssmgr\current\polling |
Note
Do not copy the file if you are upgrading from a previous version. Instead, reflect the contents of the customization in the previous version, according to the description in "C.13 Polling Service Setting File"
Restart the Manager.
Go to [Control Panel] - [Administrative Tools] - [Services], select "ETERNUS SF Storage Cruiser Manager" and start the service.