Install ETERNUS SF Manager according to the procedure below.
Note
The port number for the communication service to be specified by installation is for communication service for local transactions. For setting port number of the cluster transaction communication service, execute the procedure according to the clustered system reference to "Chapter 8 Customization of Managed Server Transactions".
ETERNUS SF Manager determines the user ID used internally. (For example, 15999)
Refer to the /etc/passwd file for the primary node and secondary node to check that the user ID to be assigned is not used.
Specify the user ID determined in step 1 for the install parameter "esfpostgres_UID :" and perform a custom installation of ETERNUS SF Manager on the primary node. However, do not install it on a shared disk.
Refer to "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for details.
Set up ETERNUS SF Manager on the primary node.
Refer to "Setup of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for details. However, the procedure of "Updating Management Server IP address information" is not required.
Create a shared disk on the primary node as required.
Stop the daemons on the primary node.
Execute the following shell script:
# /opt/FJSVesfcm/bin/stopesf.sh
The following daemons are stopped.
ETERNUS SF Manager Apache daemon
ETERNUS SF Manager Tomcat daemon
ETERNUS SF Manager Postgres daemon
Storage Cruiser Management Server daemon
AdvancedCopy Manager daemon
On the primary node, execute the database unsetup.
Start uninstallation of the database integrated unsetup. Delete the database and its environment. Cancel the repository configurations.
Note
Perform this procedure on the location that is specified when the Management Server is installed.
The database unsetup utilizes Symfoware functions. If Symfoware is being monitored by other software at the same time, execution of the database unsetup may fail.
Therefore, stop Symfoware monitoring before executing the database unsetup.
The procedure is shown below.
Log in to the server as a superuser.
Start uninstallation of the database integrated unsetup.
Enter the following command to start uninstallation of the database integrated unsetup.
# /opt/swstorage/bin/stgdbunset |
Confirm whether to continue processing.
To continue processing, enter "y". To stop processing, enter "n".
////////////////////////////////////////////////////////////////////
AdvancedCopy Manager Storage management server ( kiku )
Database unsetup
////////////////////////////////////////////////////////////////////
+----------------------------------------------------------------+
| |
| All of database environments of AdvancedCopy Manager |
| will be deleted. |
| |
| [Notes] |
| Once processing has started, all stored data is discarded. |
| Make sure that the environment allows execution |
| before proceeding. |
| |
+----------------------------------------------------------------+
Do you want to continue with processing? [y/n] ==> y
|
The database and database environment of the Management Server are deleted.
During deletion of the database and database environment of the Management Server, the progress is displayed on the screen.
The following is an example of execution progress.
Note
If an RDA-SV definition file overwrite confirmation message is displayed on the screen during processing, enter "y".
////// AdvancedCopy Manager database unsetup //////
Activation of RDB is complete.
==================================================================
The replication management will be deleted.
==================================================================
==================================================================
Clearing of database will start. (replication management)
==================================================================
.
Tables have been deleted. (replication management)
==================================================================
Clearing of database is complete. (replication management)
==================================================================
==================================================================
The replication management has been deleted.
==================================================================
.
.
.
==================================================================
Clearing of database environment is complete.
==================================================================
==================================================================
The basic section has been deleted.
==================================================================
Database unsetup ended normally.
#
|
Specify the user ID determined in step 1 for the install parameter "esfpostgres_UID :" and perform a custom installation of ETERNUS SF Manager on the secondary node. However, do not install it on a shared disk.
Refer to "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for details.
For the installation target, specify the same path as the one specified for the primary node.
Set up ETERNUS SF Manager on the secondary node.
Refer to "Setup of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for details. However, the procedure of "Updating Management Server IP address information" is not required.
Stop the daemons on the secondary node.
Execute the following shell script:
# /opt/FJSVesfcm/bin/stopesf.sh
The following daemons are stopped.
ETERNUS SF Manager Apache Service
ETERNUS SF Manager Tomcat Service
Storage Cruiser Management Server daemon
AdvancedCopy Manager daemon
On the secondary node, execute DB unsetup.
Start uninstallation of the database integrated unsetup using same procedure as a primary node. Delete the database and its environment. Cancel the repository configurations.
