ETERNUS SF AdvancedCopy Manager Installation Guide 13.0 -Solaris-

Contents Index

Chapter 4 Customization of Storage Management Server

This chapter explains the customization of the Storage management server.

4.1 Flow of Customizing Storage Management Server 

Set up the storage management server according to the following procedure:

4.2 Setting up the port number (/etc/services file)

Operation of the storage management server requires the following port numbers listed below.

Therefore, prepare the port numbers to be used in the storage management server and save them to the/etc/services file.

Figure 4.1 shows the port numbers to be written to the /etc/services file.

Table 4.1 shows the port number and purpose for each service,. If settings such as port filtering are required, refer to the description in the "Purpose" column to determine the object to connect to the port before making these settings.

[Figure 4.1 Contents of the /etc/services file]

#service-name  port-number/protocol-name

stgxfws  1226/tcp
rdaswstf 2004/tcp
rmiswstf 9851/tcp
semswstf 9852/tcp
smaclmgr 4660/tcp

If the port numbers in Figure 4.1 have already been used in the installed system, assign other numbers of available ports.

The following messages are outputted when there is a mistake in the setup of a port number. Check the setup.

Example:

component start : sh /opt/FJSVswstf/bin/stgdbcom start
SymfoWARE/RDB for AdvancedCopy Manager has been successfully started !!
RDA-SV for AdvancedCopy Manager failed to start !!

[Table4.1 Port numbers and purposes]

*1: In a cluster system, this service is required for each job that is created during the cluster setup. The logical node name is the name that was specified during the cluster setup, and the reception port is any port number that was specified for that job

If port numbers other than those listed in Figure 4.1 have been specified in the /etc/services file, use the port numbers in the /etc/services file instead of the port numbers listed in the "Reception port" column of Table 4.1.

4.3 Setting up the Repository

This section explains how to set up the repository used to operate the storage management server.

Use the following procedure to set up the repository:

1. Estimation of database area

2. Directory creation

3. Kernel parameter tuning

4. Database creation

4.3.1 Estimation of database area

See "Repository"and estimate the size of the database area.

4.3.2 Directory creation

In "Repository" it was explained that database areas are required in the following directories:

• The directory for database file

• The directory for RDB dictionary

• The directory for RDB log file

• The directory for repository data database space

In this Chapter, these directories are created on the device where the database area of a capacity indicated in "Repository" can be stored.

• Although the four directories can be created on the same device, for reliability and update performance considerations, Fujitsu recommends preparing these directories on another partition.

• When the directories are used on the cluster system, create them on the shared disk.

4.3.3 Kernel parameter tuning

The Storage management server requires tuning of the kernel parameters, which are necessary for operation. Refer to the following tables corresponding to each Solaris release for information about which kernel parameters require tuning and their values. Refer to the Solaris manuals for more information about kernel parameters.

If the parameters listed in Table have already been set, do the following. For a parameter listed as "Maximum value" in "If parameters have already been set," specify the larger of the current value and the tuning value. For a parameter listed as "Addition," specify the value obtained by adding the tuning value to the current value.

+Solaris 8 and 9

++Tuning values for kernel parameters

[Table 4. 2 Tuning values for kernel parameters ]

(*1) The parameters need not be set for Solaris 9.

++Tuning procedure

To edit the kernel parameters, either add tuning records to the /etc/system file or change the value of existing records.

1. Use the following command to check the settings of the parameters in this table that are currently set in the system.

   # /usr/sbin/sysdef

2. Refer to "Tuning values for kernel parameters" in Table 4.2, and compare the current value to the value in the table. Calculate the appropriate value to set by either adding the two values or taking the maximum value, as indicated in the table.

3. Edit the /etc/system file.

   An example of editing the /etc/system file is shown below. (This is only an example. Use suitable values for your environment.)

   set shmsys:shminfo_shmmax = 20000000 set shmsys:shminfo_shmmni = 180 set shmsys:shminfo_shmseg = 60 set semsys:seminfo_semmni = 320 set semsys:seminfo_semmns = 670 set semsys:seminfo_semmnu = 542 set semsys:seminfo_semmsl = 35 set msgsys:msginfo_msgmax = 2048 set msgsys:msginfo_msgmnb = 4096 set msgsys:msginfo_msgmni = 53 set msgsys:msginfo_msgtql = 140

4. To register the new kernel parameter values in the system, reboot the system.

   Use the following command to reboot the system:

   # cd / # /usr/sbin/shutdown -y -i6 -g0

5. Restart the system, and then use the output of the following command to check that the settings have been applied.

   # /usr/sbin/sysdef

+Solaris 10

AdvancedCopy Manager runs under the following project:

system project

This is the project in which daemons such as those in the initialized operating system status run.

user.root project

Processes that run with root permissions in the initialized operating system status belong to this project.

++Tuning values for resource control

[Table 4.3 Tuning values for resource control]

For "privileged" in the "Privilege level" column, specify "privileged" in the /etc/project file.

++Tuning procedure

To edit parameters, edit the /etc/project file.

1. The default values for the system, and the maximum values that can be set can be checked as follows:

   # projects -l system projid : 0 comment: "" users : (none) groups : (none) attribs: user.root projid : 1 comment: "" users : (none) groups : (none) attribs: noproject projid : 2 comment: "" users : (none) groups : (none) attribs: default projid : 3 comment: "" users : (none) groups : (none) attribs: <-- Confirm that there is a project with no entry for "attribs" group.staff projid : 10 comment: "" users : (none) groups : (none) attribs: # newtask -p default # prctl $$ # prctl $$ process: 3711: sh NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT process.max-port-events privileged 65.5K - deny - system 2.15G max deny - process.max-msg-messages privileged 8.19K - deny - system 4.29G max deny - omitted

2. Refer to "Tuning values for resource control" in Table 4.3, and compare the current value to the value in the table. Calculate the appropriate value to set by either adding the two values or taking the maximum value, as indicated in the table

3. Edit the /etc/project file.

   The following example shows how to edit the /etc/project file. (Note that this is only an example, and make the correct settings for the environment.)

   system:0::::project.max-msg-ids=(privileged,131,deny);project.max-shm-ids=(privileged,208, deny);project.max-sem-ids=(privileged,438,deny) user.root:1::::project.max-msg-ids=(privileged,131,deny);project.max-shm-ids=(privileged,208,deny);project.max-sem-ids=(privileged,438,deny) noproject:2:::: default:3:::: group.staff:10::::

4. Settings information can be displayed by executing the following command.

   The following example shows how the confirmation command executes.

   # projects -l system projid : 0 comment: "" users : (none) groups : (none) attribs: project.max-msg-ids=(privileged,131,deny) project.max-shm-ids=(privileged,208,deny) project.max-sem-ids=(privileged,438,deny) user.root projid : 1 comment: "" users : (none) groups : (none) attribs: project.max-msg-ids=(privileged,131,deny) project.max-shm-ids=(privileged,208,deny) project.max-sem-ids=(privileged,438,deny) noproject projid : 2 comment: "" users : (none) groups : (none) attribs: default projid : 3 comment: "" users : (none) groups : (none) attribs: group.staff projid : 10 comment: "" users : (none) groups : (none) attribs: #

4.3.4 Database creation

Start Database Merge Setup to create a database environment and database.

• If the storage management server operates in a cluster, then the following procedure is unnecessary because the settings are specified during cluster setup.
  Specify the settings for the cluster environment while referring to "Customization of Storage Management Server Transactions" in the ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment.

• In advance, refer to "Estimation of database area" "Directory creation" and "Kernel parameter tuning" and verify the IP address of the storage management server.

• To activate the database integration setup, log in as the root user.

• Although the four directories can be created on the same device, for reliability and update performance considerations, Fujitsu recommends preparing these directories on another partition.

• Execute it at the locale specified at the time of installation on the Storage management server (or at the time of Symfoware installation if Symfoware is already installed).

1. Activate the database integration setup.

   Enter the following command to activate the database integration setup.

   # /opt/swstorage/bin/stgdbset

   
   

   

   Since it performs from a cluster setup command when applying by the cluster system, it is not necessary to input a command.

2. Confirm whether to continue processing.

   To continue processing, enter "y." To not continue processing, enter "n."

   In the following display example, the machine name is displayed in parentheses on the second line.

   //////////////////////////////////////////////////////////////////// AdvancedCopy Manager Storage management server ( kiku ) Common environment creation //////////////////////////////////////////////////////////////////// +----------------------------------------------------------------+ | A common environment for the AdvancedCopy Manager | | Storage management server will be created. | | [Notes] | | Prepare the following directories before starting processing.| | ============================================================== | | | | 1) Directory for the DB file | | 2) Directory for the RDB dictionary | | 3) Directory for the RDB log file | | 4) Directory for the DB space to store the repository data | | | +----------------------------------------------------------------+ Do you want to continue with processing? [y/n] ==> y

3. Enter the directory name for database files.

   Use the absolute path to enter the directory that has been created as a directory for database files in "Directory creation".

   //////////////////////////////////////////////////////////////////// AdvancedCopy Manager Storage management server ( kiku ) Common environment creation //////////////////////////////////////////////////////////////////// -----------------------< DB device setting >---------------------- Enter the directory name for the DB file. [Notes] Enter the absolute path name of the directory. Enter ==> /aaa1

4. Enter the directory name for the RDB dictionary.

   Enter the directory name that has been created as a directory for the RDB dictionary in "Directory creation".

   //////////////////////////////////////////////////////////////////// AdvancedCopy Manager Storage management server ( kiku ) Common environment creation //////////////////////////////////////////////////////////////////// -----------------------< DB device setting >---------------------- Enter the directory name for the RDB dictionary. [Notes] Enter the absolute path name of the directory. Enter ==> /aaa2

5. Enter the directory name for RDB log files.

   Enter the directory name that has been created as a directory for RDB log files in "Directory creation".

   //////////////////////////////////////////////////////////////////// AdvancedCopy Manager Storage management server ( kiku ) Common environment creation //////////////////////////////////////////////////////////////////// -----------------------< DB device setting >---------------------- Enter the directory name for the RDB log file. [Notes] Enter the absolute path name of the directory. Enter ==> /aaa3

6. Enter the directory name for a repository data database space and the repository data size.

   Enter the directory name that has been created as a directory for a repository data database space in "Directory creation". Later, enter the repository data size that has been estimated in "Estimation of a database area" In this case, use an integer value in megabytes. (65 megabytes or more)

   //////////////////////////////////////////////////////////////////// AdvancedCopy Manager Storage management server ( kiku ) Common environment creation //////////////////////////////////////////////////////////////////// -----------------------< DB device setting >---------------------- Enter the directory for the DB space used to save repository data. [Notes] Enter the absolute path name of the directory. Enter ==> /aaa4 Enter the repository data size. (minimum: 65MB) [Notes] Enter only the number of 65MB or more values in MB unit. Enter ==> 65

7. Verify the entered contents.

   If the entry is correct, press "y." To reenter the contents, press "n."

   After "y" is pressed, the entry is checked. If an error is detected, an error message is displayed and control returns to step 2.

   If "n" is pressed, control returns to step 2.

   //////////////////////////////////////////////////////////////////// AdvancedCopy Manager Storage management server ( kiku ) Common environment creation //////////////////////////////////////////////////////////////////// ==================================================================== Directory name for the DB file ............/aaa1 Directory name for the RDB dictionary ...../aaa2 Directory name for the RDB log file ......./aaa3 Directory name for the DB space used to save repository data ..../aaa4 Repository data Size ......................65MB ==================================================================== Okay? [y/n] ==> y

8. Confirm whether to continue the creation of the common environment for the storage management server.

   To continue creation of the environment for the storage management server, press "y." To stop the process, press "n."

   //////////////////////////////////////////////////////////////////// AdvancedCopy Manager Storage management server ( kiku ) Common environment creation //////////////////////////////////////////////////////////////////// +----------------------------------------------------------------+ | Creation of the AdvancedCopy Manager Storage management | | server environment will start. | | ============================================================== | | | | Once processing has started, system information is rewritten.| | Make sure that the environment allows execution | | before proceeding. | | | +----------------------------------------------------------------+ Do you want to continue with processing? [y/n] ==> y

9. The common environment of the storage management server is created.

   The common environment of the storage management server is created and the results are displayed periodically. An example of the exaction results is shown below.

   

   If the confirmation message for overwriting the RDA-SV definition file is displayed on the screen during the process, press "y."

   ================================================================== Creation of database disk environment will start. ================================================================== ================================================================== Creation of database disk environment is complete. ================================================================== ================================================================== Creation of database operating environment will start. ================================================================== Copying of the DB definition and setting files are complete. Creation of a log management file is complete. Creation of a RDB temporary log file is complete. Creation of a RDB archive log file is complete. Creation of a RDB dictionary and RDB directory file is complete. Activation of RDB is complete. ================================================================== Creation of database operating environment is complete. ================================================================== ================================================================== Creation of database will start (basic section). ================================================================== Creation of database disk environment will start. ================================================================== ================================================================== Creation of database disk environment is complete. ================================================================== ================================================================== Creation of database operating environment will start. ================================================================== Copying of the DB definition and setting files are complete. Creation of a log management file is complete. Creation of a RDB temporary log file is complete. Creation of a RDB archive log file is complete. Creation of a RDB dictionary and RDB directory file is complete. Activation of RDB is complete. ================================================================== Creation of database operating environment is complete. ================================================================== ================================================================== Creation of database will start (basic section). ================================================================== Definition of database is complete. Definition of database space is complete. Table definition will start. .................. Table definition is complete. ================================================================== Creation of database is complete (basic section). ================================================================== . . . ================================================================== Setup for replication management is complete. ==================================================================

10. Enter the IP address of the storage management server

    Enter the IP address of the storage management server that communicates with a storage server.
    If the storage management server uses a logical IP address, enter the logical IP address.

    If the contents have been entered correctly, the database integration setup ends.

    //////////////////////////////////////////////////////////////////// AdvancedCopy Manager Storage management server ( kiku ) Database integrated setup //////////////////////////////////////////////////////////////////// Enter the IP address of the Storage management server. [Notes] For operating by a logical IP address, enter a logical IP address. ( format : ???.???.???.??? ) Enter ==> 1.10.11.100 Storage management server has been registered.

11. Enter the user name and password for repository access.

    Enter the user name and password for repository access. Enter the registered user name and password.

    

    It is recommended that a secure user other than root be used.

    If the contents have been entered correctly, the database integration setup ends.

    //////////////////////////////////////////////////////////////////// AdvancedCopy Manager Storage management server ( kiku ) Database integrated setup //////////////////////////////////////////////////////////////////// Enter the user name and password for accessing the repository of AdvancedCopy Manager. [Notes] We recommend you to input a general user other than root. Username : user Password : Password(Re-enter) : Password for accessing the repository has been registered. Database integrated setup ended normally. #

12. A daemon is started.

    Use the following command to start a daemon.

    # /opt/swstorage/bin/startacm

13. Save the database.

    In case of an accident or failure, save the database for which the environment has been set up.

    Refer to "Saving a database," in the ETERNUS SF AdvancedCopy Manager Operator's Guide for details on how to save the created database area.

4.4 Setting up the Web Server 

The following setting needs to be made to display data from the Web screen. If only the command mode is to be used, the setting does not need to be made to display data from the WEB screen.

• Web server user settings

• Automatic startup of web server

4.4.1 Web server user settings 

The web server user settings are dependent on web server to be used.

The following sections explain how to set up the directory (alias) for each major web server

The following example of settings is explained with the default installation destination and file name of each web server. If the Web server is used with custom (nondefault) settings, be sure those settings conform to the installation destination and file name used.

A symbolic link exists below the real directory set by alias.

Therefore, please set for the use of a symbolic link below a real directory

when a detailed setting concerning alias is done to become possible.

4.4.1.1 Setting up Apache 

This section provides an example of setting up the directory (alias) for Apache.

Add the following lines to settings file "/etc/apache/httpd.conf."

Lines to be added:

Alias        /swstorage/      /opt/swstorage/inet/wwwroot/
Alias        /swstorage-j/    /opt/swstorage/java/
Alias        /swstorage-d/    /opt/swstorage/java/data/
ScriptAlias  /swstorage-cgi/  /opt/swstorage/inet/cgi-bin/

Add the following line to setting file "/etc/apache/mime.types". If "policy" has already been registered, the line need not be added.

application/x-swstf-policy    policy

4.4.2 Setting up automatic startup of the web server

The Web server must be operating before it can be used. Therefore, Fujitsu recommends that the web server be started automatically when the storage server machine is started.

For details on automatic starting of the machine, refer to the handbook of the web server program to be used.

4.5 Automatic Activation of Daemons 

Accessing data from the web screen in the storage management server requires the activation of several daemons of the storage management server. However, the system determines the setup so that all the daemons are automatically activated during database setup and installation. However, separately set up the web server so that it starts up automatically. For more information on setting up the web server, refer to the manual of the relevant web server.

Contents Index