Open topic with navigation
While there are many different configurations depending upon which database management system is being used, below is the basic layout that should be adhered to.
Set up comm paths between the primary and secondary servers
Add virtual ip resources to etc/hosts
Create virtual ip resources for host and database
Set up shared disks
Create file systems for SAP (located on shared disk)
Create file systems for database (located on shared disk)
Mount the main SAP file systems
Create mount points
Mount the PAS, SCS and ASCS directories as well as any additional Application Servers
Please consult the SAP installation guide specific to the database management system for details on the directory structure for the database. All database files must be located on shared disks to be protected by the LifeKeeper Recovery Kit for the database. Consult the database specific LifeKeeper Recovery Kit Documentation for additional information on protecting the database.
The following example is only a sample of the many configurations than can be established, but understanding these configurations and adhering to the configuration rules will help define and set up workable solutions for your computing environment.
From the UI of the primary server, set up comm paths between the primary server and the secondary server.
Add an entry for the actual primary and secondary virtual ip addresses in /etc/hosts.
Log in to LifeKeeper on the primary server and create virtual ip resources for your host and your database (ex. ip-db10 and ip-sap10).
Set up shared disks between the two machines.
Note : One lun for database and another for SAP data is recommended in order to enable independent failover.
For certain configurations, the following tasks may need to be completed:
Create the physical devices
Create the volume group
Create the logical volumes for SAP
Create the logical volumes for Database
Create all file systems required for your database (Example: mirrlogA, mirrlogB, origlogA, origlogB, sapdata1, sapdata2, sapdata3, sapdata4, oraarch, saparch, sapreorg, saptrace, oraflash -- mkfs -t ext3 /dev/oracle/mirrlogA ).
Note: Consult the LifeKeeper for Linux Technical Documentation for the database-specific recovery kit and the Component Installation Guide SAP Web Application Server for additional information on which file systems need to be created and protected by LifeKeeper.
Create mount points for the main SAP file systems and then mount them (required). For additional information, see the NFS Mount Points and Inodes topic. (Note: /exports directory was used to mount the file systems.)
mount /dev/sap/sapmnt /exports/sapmnt
mount /dev/sap/saptrans /exports/saptrans
Create temporary mount points using the following command.
Mount the three SAP directories (the following mount points are necessary for each Application Server present whether using external NFS or not).
mount /dev/sap/ASCS00 /tmp/m1
mount /dev/sap/SCS01 /tmp/m2
mount /dev/sap/DVEBMGS02 /tmp/m3
Proceed to Moving Data to Shared Disk and LifeKeeper.
© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.
Open topic with navigation