Managing Serviceguard Extension for SAP Version B.05.10, September 2010

NOTE: In HA scenarios, valid for SAPDB/MAXDB versions up to 7.6, the untime directory
/sapdb/data/wrk is configured to be located at /sapdb/<DBSID>/wrk to support consolidated
failover environments with several MAXDB instances. The local directory /sapdb/data/wrk
is referred to by the VSERVER processes (vserver, niserver), that means VSERVER core
dump and log files will be located there.
Table 2-10 File System Layout for SAPDB Clusters
Device Minor
Number
VG NameVG TypePotential Owning
Packages
Access
Point
Mount Point
database specific
db<DBSID>
dbci<DBSID>
jdb<dbsid>
jdbjci<DBSID>
shared
disk
/sapdb/<DBSID>
/sapdb/<DBSID>/wrk*
/sapdb/<DBSID>/data<nr>
/sapdb/<DBSID>/saplog<nr>
/sapdb/<DBSID>/data**
environment
specific
db<DBSID>
dbci<DBSID>
jdb<DBSID>
jdbjci<DBSID>
SAPNFS
shared
disk and
HA NFS
/export/sapdb/programs
/export/sapdb/data
/export/sapdb/client**
/export/var/spool/sql/ini
nonelocal
/etc/opt/sdb
*Only valid for versions lower than 7.6.
**Only valid for versions 7.8 or higher.
NOTE: Using tar or cpio is not a safe method to copy or move directories to shared volumes.
In certain circumstances file or ownership permissions may not be correctly transported, especially
files having the s-bit set: /sapdb/<SID>/db/pgm/lserver and
/sapdb/<SID>/db/pgm/dbmsrv. These files are important for the vserver process ownership
and they have an impact on starting the SAPDB via <SID>adm. These files should retain the
same ownership and permission settings after moving them to a shared volume.
Database and SAP instances depend on the availability of /sapdb/programs. To minimize
dependencies between otherwise unrelated systems, using a dedicated SAPNFS package is
strongly recommended, especially when the cluster has additional SAP application servers
installed, more than one SAPDB is installed, or the database is configured in a separate DB
package. Keeping local copies is possible, though not recommended because of the fact that there
are no administration tools that keep track of the consistency between the local copies of these
files on all the systems.
DB2 Storage Considerations
SGeSAP supports failover of DB2 databases as part of SGeSAP NFS cluster option 1. Cluster File
Systems can not be used for the DB2 part of SGeSAP clusters.
Consolidation of SAP instances is possible in SGeSAP DB2 environments.
Database Instance Storage Considerations 35