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:
See "Repository" and estimate the size of the database area.
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.
Note
Although the four directories can be created on the same partition, for reliability and update performance considerations, Fujitsu recommends preparing these directories on another partition.
When the directories are used on a cluster system, create them on the shared disk.
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.
Note
If the parameters listed in Table have already been set, perform the following. For a parameter listed as "Maximum value" in the "Standard configuration" column, specify the larger of the current value and the default value. For a parameter listed as "Addition", specify the value obtained by adding to the default value or current value.
A method for making entries in the /etc/project file under Solaris 10 has been added, in addition to the previous method for making entries in the /etc/system file.
Solaris 8 and 9 and Solaris 10 (tuning using /etc/system)
Tuning values for kernel parameters
Resource | Parameter | Required value | Standard configuration |
|---|---|---|---|
Shared memory | shmsys:shminfo_shmmax | 2150000 | Maximum value |
shmsys:shminfo_shmmni | 80 | Addition | |
shmsys:shminfo_shmseg (*1) | 60 | Maximum value | |
Semaphore | semsys:seminfo_semmni | 310 | Addition |
semsys:seminfo_semmns (*2) | 610 | Addition | |
semsys:seminfo_semmnu (*2) | 512 | Addition | |
semsys:seminfo_semmsl | 35 | Maximum value | |
Message | msgsys:msginfo_msgmax (*2) | 512 | Maximum value |
msgsys:msginfo_msgmnb | 4096 | Maximum value | |
msgsys:msginfo_msgmni | 3 | Addition | |
msgsys:msginfo_msgtql | 100 | Maximum value |
*1 The parameters need not be set for Solaris 9 and later.
*2 This setting is not required under Solaris 10.
Tuning procedure
To edit the kernel parameters, either add tuning records to the /etc/system file or change the value of existing records.
Use the following command to check the settings of the parameters in this table that are currently set in the system.
# /usr/sbin/sysdef |
Refer to the table "Table 3.3 Tuning values for kernel parameters" above, 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.
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 |
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 |
Restart the system, and then use the output of the following command to check that the new settings have been applied.
# /usr/sbin/sysdef |
Solaris 10 (tuning using /etc/project)
Note
Care is required when setting values if other software that only supports tuning using the /etc/system file is used on a server where this product is used.
If the /etc/system file and the /etc/project file are both used for tuning, refer to the operating system documentation to set the appropriate values.
If the /etc/project file is used for tuning, ensure that you do not set values that are lower than the Solaris default values.
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
Resource | Parameter | Required value | Standard configuration | Privilege level |
|---|---|---|---|---|
Shared memory | project.max-shm-memory | 172,000,000 | Addition | privileged |
project.max-shm-ids | 80 | Addition | privileged | |
Semaphore | project.max-sem-ids | 310 | Addition | privileged |
process.max-sem-nsems | 35 | Maximum value | privileged | |
Message | process.max-msg-qbytes | 4096 | Maximum value | privileged |
project.max-msg-ids | 3 | Addition | privileged |
For "privileged" in the "Privilege level" column, specify "privileged" in the /etc/project file.
Tuning procedure
To edit parameters, edit the /etc/project file.
Check the initial values and the upper limits of the values that can be set in a system project and a user.root project, as shown below:
# newtask -p system # prctl $$ 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 -- zone.cpu-shares privileged 1 - none - system 65.5K max none - # newtask -p user.root # prctl $$ 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 -- zone.cpu-shares privileged 1 - none - system 65.5K max none - |
Refer to the "Tuning values for resource control" Table 3.4 Tuning values for resource control above, 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
Use the projmod command to set values for the system project and for the user.root project.
The following example shows how to edit the /etc/project file.
(Note that this is an example only.)
# projmod -s -K 'project.max-msg-ids=(privileged,131,deny)' system # projmod -s -K 'project.max-shm-ids=(privileged,208,deny)' system # projmod -s -K 'project.max-sem-ids=(privileged,438,deny)' system # projmod -s -K 'project.max-shm-memory=(privileged,270585456,deny)' system # projmod -s -K 'project.max-msg-ids=(privileged,131,deny)' user.root # projmod -s -K 'project.max-shm-ids=(privileged,208,deny)' user.root # projmod -s -K 'project.max-sem-ids=(privileged,438,deny)' user.root # projmod -s -K 'project.max-shm-memory=(privileged,270585456,deny)' user.root |
Configuration information can be displayed by executing the following "projects -l" 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)
project.max-shm-memory=(privileged,270585456,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)
project.max-shm-memory=(privileged,270585456,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:
# |
Enable tuning of the kernel parameters.
The following is an example of executing the commands. Please refer to the manual etc. of Solaris for details of the command.
system projects
# newtask -p system |
user.root projects
# newtask -p user.root |
Check the kernel parameter values after modification.
The following is an example of executing the commands. Please refer to the manual etc. of Solaris for details of the command.
system projects
# prctl -i project system |
user.root projects
# prctl -i project user.root |
The Table 3.5 Kernel parameter required values required for AdvancedCopy Manager operation below lists the kernel parameters to be tuned and their values.
To edit a kernel parameter, add a record for tuning to the /etc/sysctl.conf file or modify the current record value.
Note
If a value has not been set for a parameter in the /etc/sysctl.conf file, the operating system default value is used for the parameter. In such cases, make an addition or change based on the operating system default value. To display the values being used by the operating system, execute the sysctl command with the "-a" option. See the section about the man command of the operating system for details of the sysctl command.
For a parameter described as "Maximum value" under "Parameters already set" in the Table 3.5 Kernel parameter required values required for AdvancedCopy Manager operation below, specify the larger of the tuning value and the specified or default value. For a parameter listed as "Addition", specify the value obtained by adding the tuning value to the specified or default value.
Resource | Parameter | Required value | If parameters have already been set |
|---|---|---|---|
Shared memory | kernel.shmmax | 2097152 | Maximum value |
kernel.shmmni | 50 | Addition | |
Semaphore | The 1st value of kernel.sem (*1) | 30 | Maximum value |
The 2nd value of kernel.sem (*1) | 600 | Addition | |
The 4th value of kernel.sem (*1) | 300 | Addition | |
Message | kernel.msgmax | 512 | Maximum value |
kernel.msgmnb | 4096 | Maximum value | |
kernel.msgmni | 3 | Addition |
*1 Because the kernel.sem parameter is specified in the following format, it indicates the order of the four set values.
For the third value, specify the specified or default value.
kernel.sem = para1 para2 para3 para4
The following is an example of an edited /etc/sysctl.conf file.
kernel.shmmax = 40000000 kernel.shmmni = 4200 kernel.sem = 250 32600 32 428 kernel.msgmax = 8192 kernel.msgmnb = 16384 kernel.msgmni = 18 |
Reboot the system or execute the sysctl command to reflect kernel parameter tuning.
The following shows the command for rebooting the system.
# cd / # /sbin/shutdown -r now |
The following provides an entry example where the sysctl command is executed to reflect the tuning.
# /sbin/sysctl -p /etc/sysctl.conf |
Start Database Merge Setup to create a database environment and database.
The procedure is described below.
Note
If the Storage Management Server operates in a cluster, then the following procedure is unnecessary because the configuration is specified during cluster setup.
For details on how to configure the cluster server environment, refer to "ETERNUS SF AdvancedCopy Manager Operator's Guide for Cluster Environment", chapter "Customization of Storage Management Server Transactions and Storage Server Transactions".
In advance, refer to "3.2.3.1 Estimation of database area","3.2.3.2 Directory creation" and "3.2.3.3 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 partition, 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.
Before activating the database integration setup, check and make sure the system is set to use a shadow password. The system should always be operated with the use shadow password setting turned on.
Activate the database integration setup.
Enter the following command to activate the database integration setup.
# /opt/swstorage/bin/stgdbset |
Note
When operating as a cluster system, database integration setup is activated from the cluster setup command, so this command need not be entered.
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
|
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 3.2.3.2 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
|
Enter the directory name for the RDB dictionary.
Enter the directory name that has been created as a directory for the RDB dictionary in 3.2.3.2 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
|
Enter the directory name for RDB log files.
Enter the directory name that has been created as a directory for RDB log files in 3.2.3.2 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
|
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 3.2.3.2 Directory creation. Then, enter the repository data size that has been estimated in "3.2.3.1 Estimation of database area". You must use an integer value in megabytes for this value (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
|
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
|
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, enter "y". To stop the process, enter "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
|
The common environment of the Storage Management Server is created.
The common environment of the Storage Management Server is created and the results can be displayed as required. An example of the execution results is shown below.
Note
If the confirmation message for overwriting the RDA-SV definition file is displayed on the screen during the process, enter "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).
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.
|
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.
|
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.
Point
It is recommended that a secure user other than root be used.
Specify a username and password that is valid in the operating system.
Specify a username and a password that are 18 bytes or less.
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.
# |
See
For the password changing of the repository accessible user, refer to "Deleting a repository accessible user or changing a repository accessible user's password" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide".
A daemon is started.
Use the following command to start a daemon.
# /opt/swstorage/bin/startacm |
Save the database.
In case of a failure, save the database for which the environment has been set up.
Refer to "Database save method" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for details on how to save the created database area.
