ETERNUS SF Express V16.9.1 / Storage Cruiser V16.9.1 / AdvancedCopy Manager V16.9.1 Installation and Setup Guide

4.1.5 Settings Required to Register Storage Devices (When Using the ETERNUS DX S2 series Only)

The required settings procedure for device registration of the ETERNUS DX S2 series is as follows.

Point

To delete the registration of the ETERNUS DX S2 series from the product after the settings in this section are performed and operations are started, the settings content must be restored. For the procedure to restore the settings content, refer to "Appendix N Work Required After Device Deletion of the ETERNUS DX S2 series".

For Windows environments

1. Log on to the Management Server using Administrator privileges.

2. Stop the ETERNUS SF Manager service.

   • When the Management Server is in a non-clustered system

     Execute the following batch to stop the ETERNUS SF Manager service.

     > $INS_DIR\Common\bin\Stop_ESFservice.bat

     From this step onward, $INS_DIR is "Program Directory" specified at the ETERNUS SF Manager installation.

   • When the Management Server is in a clustered system

     Use the Failover Cluster Manager to stop the ETERNUS SF Manager service.

3. Back up the settings file. Copy the following file to the backup destination directory.
   To use the Management Server in a clustered system, perform this step on both the primary node and secondary node.

   File to be Backed up	Backup Destination Directory
   $INS_DIR\Common\jre\conf\security\java.security	$INS_DIR\Common\sys\tomcat\webapps\esf\WEB-INF\config
   $INS_DIR\CCM\jre\conf\security\java.security	$INS_DIR\CCM\tools

4. Copy the following file over the copy destination file.
   To use the Management Server in a clustered system, perform this step on both the primary node and secondary node.

   Copy Source File	Copy Destination File
   $INS_DIR\Common\sys\tomcat\webapps\esf\WEB-INF\config\java.security.forS2.windows	$INS_DIR\Common\jre\conf\security\java.security
   $INS_DIR\CCM\tools\java.security.forS2.windows	$INS_DIR\CCM\jre\conf\security\java.security

5. Start the ETERNUS SF Manager service.

   • When the Management Server is in a non-clustered system

     Execute the following batch to start the ETERNUS SF Manager service.

     > $INS_DIR\Common\bin\Start_ESFservice.bat

   • When the Management Server is in a clustered system

     Use the Failover Cluster Manager to start the ETERNUS SF Manager service.

For Solaris or Linux environments

1. Log in to the Management Server as a superuser.

2. Stop the ETERNUS SF Manager daemon.

   • When the Management Server is in a non-clustered system

     Execute the following command to stop the ETERNUS SF Manager daemon.

     # /opt/FJSVesfcm/bin/stopesf.sh

   • When the Management Server is in a clustered system

     Use the cluster software in use to stop ETERNUS SF Manager daemon.

3. Back up the settings file. Copy the following file to the backup destination directory.
   To use the Management Server in a clustered system, perform this step on both the primary node and secondary node.

   • For Solaris environments

     File to be Backed up	Backup Destination Directory
     /opt/FJSVesfcm/JRE/lib/security/java.security	/opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config
     /opt/FJSVccm/jre/lib/security/java.security	/opt/FJSVccm/tools

     The command execution example is as follows.

     # cp -p /opt/FJSVesfcm/JRE/lib/security/java.security /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/
     # cp -p /opt/FJSVccm/jre/lib/security/java.security /opt/FJSVccm/tools/

   • For Linux environments

     File to be Backed up	Backup Destination Directory
     /opt/FJSVesfcm/JRE/conf/security/java.security	/opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config
     /opt/FJSVccm/jre/conf/security/java.security	/opt/FJSVccm/tools

     The command execution example is as follows.

     # cp -p /opt/FJSVesfcm/JRE/conf/security/java.security /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/
     # cp -p /opt/FJSVccm/jre/conf/security/java.security /opt/FJSVccm/tools/

4. Copy the following file over the copy destination file.
   To use the Management Server in a clustered system, perform this step on both the primary node and secondary node.

   • For Solaris environments

     Copy Source File	Copy Destination File
     /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/java.security.forS2.solaris	/opt/FJSVesfcm/JRE/lib/security/java.security
     /opt/FJSVccm/tools/java.security.forS2.solaris	/opt/FJSVccm/jre/lib/security/java.security

     The command execution example is as follows.

     # cp -p /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/java.security.forS2.solaris /opt/FJSVesfcm/JRE/lib/security/java.security
     # cp -p /opt/FJSVccm/tools/java.security.forS2.solaris /opt/FJSVccm/jre/lib/security/java.security

   • For Linux environments

     Copy Source File	Copy Destination File
     /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/java.security.forS2.linux	/opt/FJSVesfcm/JRE/conf/security/java.security
     /opt/FJSVccm/tools/java.security.forS2.linux	/opt/FJSVccm/jre/conf/security/java.security

     The command execution example is as follows.

     # cp -p /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/java.security.forS2.linux /opt/FJSVesfcm/JRE/conf/security/java.security
     # cp -p /opt/FJSVccm/tools/java.security.forS2.linux /opt/FJSVccm/jre/conf/security/java.security

5. Start the ETERNUS SF Manager daemon.

   • When the Management Server is in a non-clustered system

     Execute the following command to start the ETERNUS SF Manager daemon.

     # /opt/FJSVesfcm/bin/startesf.sh

   • When the Management Server is in a clustered system

     Use the cluster software in use to start ETERNUS SF Manager daemon.