Trap XML definition file. For the contents of the customization, refer to the SNMP Trap XML definition file which was saved to the
arbitrary location.
Directory of Location of Customization Definition files
$ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\snmpth
$ENV_DIR is the "Environment Directory" of when ETERNUS SF Manager has been installed to a new environment.
3.
If the polling service setting file is customized in the environment of the previous version, it is necessary to customize this version
as well.
Save the polling service setting file that is stored in the following directory to an arbitrary location.
After that, refer to "Polling Service Setting File" in the
ETERNUS SF Storage Cruiser Operation Guide
and customize the Polling
Service Setting file. For the contents of the customization, refer to the polling service setting file which was saved to the arbitrary
location.
Customization Definition files
$ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\polling\pollingService.xml
$ENV_DIR is the "Environment Directory" of when ETERNUS SF Manager has been installed to a new environment.
7.1.2.5 Tasks to Be Performed After Upgrade (Secondary Node)
When the upgrade has been completed, the tasks below need to be performed on the secondary node.
1.
In the version level of this ETERNUS SF Manager, Symfoware is not used.
To upgrade from Version 16.1 or later, the procedures listed below are not needed.
To upgrade from Version 16.0 or earlier, follow the procedures listed below to uninstall the Symfoware Server.
a.
Confirm that other products are not utilizing the Symfoware. If Symfoware is in use by another product, refrain from
uninstalling Symfoware.
b.
Uninstall Symfoware from the Add or Remove Programs or Programs and Features page.
If Symfoware Server and Symfoware Client are both installed, uninstall the Symfoware Client first.
2.
Check that the ETERNUS SF Manager services are stopped.
If not stopped, use the Failover Cluster Manager to stop the transactions of ETERNUS SF Manager.
3.
Restore the environment setting files(sys.properties) for AdvancedCopy Manager Copy Control Module.
Overwrite the environment configurations file (sys.properties) saved during "
7.1.2.3 Performing Upgrade (Secondary Node)
onto the following file after upgrade installation.
Environment setting files for AdvancedCopy Manager Copy Control Module :
$INS_DIR\CCM\sys\sys.properties
4.
Restore the saved general scripts for the AdvancedCopy Manager CCM.
When general scripts are backed up in "
7.1.2.3 Performing Upgrade (Secondary Node)
", restore the backed-up general scripts to
the directory stored in "Preparing General Scripts for AdvancedCopy Manager CCM", which corresponds to respective operating
systems and nodes described in the
ETERNUS SF Cluster Environment Setup Guide
of the appropriate earlier version.
7.1.2.6 Starting ETERNUS SF Manager
After performing "
7.1.2.4 Tasks to Be Performed After Upgrade (Primary Node)
" and "
7.1.2.5 Tasks to Be Performed After Upgrade
", perform the following procedure:
1.
Check that start ETERNUS SF Manager services are started on the primary node.
If not started, use the Failover Cluster Manager to start the transactions of ETERNUS SF Manager.
2.
When using the ETERNUS VASA Provider, start the ETERNUS VASA Provider service on the primary node.
Use the Failover Cluster Manager to start the transactions of the ETERNUS VASA Provider.
- 93 -
