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 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, it is strongly recommended to use a dedicated SAPNFS package, especially in case that 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.

32 Planning the Storage Layout

Page 32
Image 32
HP Serviceguard Extension for SAP (SGeSAP) manual Planning the Storage Layout