dsmISI for Databases¶
Components¶
dsmISI for Databases consists of a single daemon which is handling all aspects of an NFS based access from a server to Isilon storage clusters.
dsmISI directories¶
The following directories are used by dsmISI:
Configuration |
/etc/dsmisi |
Logging |
/var/dsmisi/logs |
Internal |
/var/dsmisi/flags |
Executables |
/opt/generalstorage/dsmisi/bin |
Prerequisites¶
dsmISI must be installed on each system hosting the databases access to Isilon storage it is managing.
- The system must fulfill the following requirements:
NFS Client utilities (e.g. nfs-utils for RHEL, nfs-client for SLES)
IPv4 Connection between the operating system and the Dell EMC Isilon cluster(s)
Secure Shell (optional)
500 MB of free disk space in /opt
Additional free space for logs in /var
For details regarding the supported databases, exact specifications, versions, patch levels etc. for the operating system environment required, please contact the General Storage Support at (support@general-storage.com) and EMC’s Isilon specifications (http://www.emc.com/storage/isilon/isilon.htm).
The used ISILON OneFS should be set up for optimizing streaming performance before accessing it with dsmISI. For optimal performance, the streaming setting is recommended:
isi-9300-1# isi get /ifs/spord/
POLICY LEVEL PERFORMANCE COAL FILE
default 4x concurrency on ./
default 8x/2 concurrency on ../
isi-9300-1# isi set -l streaming /ifs/spord/
isi-9300-1# isi get /ifs/spord/
POLICY LEVEL PERFORMANCE COAL FILE
default 4x streaming/@18 on ./
default 8x/2 concurrency on ../
Planning¶
The following planning sheet describes the options needed to configure dsmISI for Databases. Be aware that there are stanzas for EMC ISILON cluster and for Databases. Some settings can be defined globally but also per instance.
Information |
Example Value |
Note |
|---|---|---|
ISILON Data IP |
10.10.20.30 |
One of the ISILON Clusters IP Adresses to be mounted |
Database Instance User/Group |
oracle:asmadmin |
Database server user and group information for the database instance to back up. In order to provide access to data on an Isilon, dsmISI will have to make sure that individual database instances are given correct permissions on directories. |
ISILON Server Custom Path |
/dbbkp/%ISI%/%ORA% |
The complete path for the database backup output directory. This is the complete path to the directory, which will be used in the database backup configuration. In this example, %ISI% is substituted with the actual ISILON Clustername and %ORA% with the oracle stanza name. |
ISILON Export Directory |
isilon01:/ifs/ORA |
This is the exported directory for ISP from the ISILON. Isilon file systems usually root in “/ifs”. It is customary to create one directory underneath that parent in order to identify the underlying content as belonging to the database instance. |
Installation¶
Once the planning sheet has been completed, copy the dsmISI installation package for your platform to your database server and install dsmISI from the same directory by issuing the following command as root user:
AIX:
installp -aX –d . dsmisi-db-X.X.X.X.bff
RHEL:
yum install dsmisi-db-X.X.X.X-X.x86_64.rpm
SLES:
zypper install dsmisi-db-X.X.X.X-X.x86_64.rpm
other Linux:
rpm -ivh dsmisi-db-X.X.X.X-X.x86_64.rpm
Add dsmISI as service¶
In order to easily start and stop dsmISI and allow automatic start during reboot, dsmISI should be added to the system as a service. Before you start dsmISI the configuration needs to be completed.
Instructions on how to configure the dsmISI daemon/service are found here
First steps after installation¶
Once installation has finished, all configuration regarding managed Isilon clusters and Database Instances is controlled via the dsmisi.conf options file.
This file is located in /etc/dsmisi.
The installation procedure places a sample options file in /etc/dsmisi/samples. You may copy this sample file to /etc/dsmisi/dsmisi.conf and edit it accordingly.
The dsmisi daemon will read dsmisi.conf only when starting or re-starting. Keep that in mind when making changes to dsmisi.conf.
Uninstallation¶
In order to remove dsmISI for Databases from your computer, stop the dsmisi daemon and issue the following commands as root user:
AIX:
installp –u dsmisi-db
RHEL:
yum remove dsmisi-db-x.x.x.x-x
SLES:
zypper remove dsmisi-db-x.x.x.x-x
other Linux:
rpm –e dsmisi-db-x.x.x.x-x
Configuration¶
dsmISI for Databases can be configured the same way as dsmISI for ISP, except for some specific Entries listed here:
Database Server Options¶
Once you configured all Isilon clusters in your dsmisi.conf file, you have to configure the database instances which have to access these clusters. The following options have to be provided for each database instance.
OracleName¶
Name of the database server instance. The OracleName doesn’t have to correspond with the real name of the database server instance in question. However, in order to avoid confusion, it is recommended to keep instance names consistent across the databases and dsmISI.
Values: Has the same limitations as file names in the system
Examples:
OracleName RMAN
ServerUsrGrp¶
User and group in which context the database server instance is running. In UNIX environments, this usually is a specific user and group exclusively used for an instance.
Values: None – determined by the existing database setup
Examples:
ServerUsrGrp oracle:asmadmin
ServerDirFormat¶
The database server name and the ISILON name can be placed by using variables %ORA% and %ISI%.
Examples:
OracleName RMAN
ServerUsrGrp oracle:asmadmin
ServerDirFormat /orabkp/%ISI%/%ORA%
IsiClusterList isilon001,isilon002
IsiClusterList¶
For each database server instance, the relevant ISILON clusters need to be defined. With comma separation more than one ISILON cluster can be configured.
Values: All restrictions regarding directory names on the platform dsmISI is running on in your environment do pertain. Be aware, certain user rights on ISILON paths cannot automatically be changed by dsmISI when you chose to use a non-root user as “IsiUser”.
Examples:
IsiClusterList isilon001
IsiClusterList isi_siteA,isi_siteB
Example Scenarios¶
Scenario: Implementing dsmISI for Databases¶
In this example, the following environment is present:
AIX Server with an installed Oracle database.
The database instance runs under the user oracle, which belongs to the user group asmadmin.
There is one ISILON cluster with 4 nodes which has already been installed. Its name is isilon01, the ip for mounting is 10.10.20.30.
The exported directory on ISILON is planned to be /ifs/ORA.
Step 1: Install dsmISI¶
The first step is to install the dsmISI package:
installp dsmisi-db 3.2.0.17
Step 2: Create the dsmisi.conf options file¶
The previously defined values for this installation need to be added to the configuration file:
hostname: # vi /etc/dsmisi/dsmisi.conf
# dsmisi.conf
FileLogLevel Error
SysLogLevel Error
ClaimWeight 50
IdleTime 300
MountArgs rw,soft,proto=tcp,timeo=600,retrans=2,intr,vers=3,nosuid
NfsRsize 524288
NfsWsize 524288
IsiName isilon1
IsiDataIp 10.10.20.30
IsiConnectionTimeout 60
IsiExport /ifs/ORA
OracleName RMAN
ServerUsrGrp oracle:asmadmin
ServerDirFormat /orabkp/%ISI%/%ORA%
IsiClusterList isilon1
Step 3: Configure dsmISI as a service¶
As dsmisi is a daemon it should be added as a service:
hostname: vi /etc/inittab
ADD: dsmisi:2:once:/usr/bin/startsrc -s dsmisi >/dev/null 2>&1
Optionally the executable can also be added to the default path:
hostname:~ vi /etc/environment
ADD: export PATH=$PATH:/opt/generalstorage/dsmisi/bin
Step 4: Start dsmisi¶
Now dsmisi can be started. If you start dsmisi for the first time after configuration it is recommended to check /var/dsmisi/logs/dsmisi.log for errors.
The mounts to all 4 nodes should be available.