Difference between revisions of "Pacemaker start and stop for Hana DB and application servers"

From Notes_Wiki
m
m
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
<yambe:breadcrumb self="Pacemaker start and stop for Hana DB and application servers">SAP setup and maintenance|SAP setup and maintenance</yambe:breadcrumb>
[[Main Page|Home]] > [[Suse]] > [[SAP setup and maintenance]] > [[Pacemaker start and stop for Hana DB and application servers]]
=Pacemaker start and stop for Hana DB and application servers=


=Stop Application servers=
=pacemaker should not auto-start on node after reboot=
The below article assumed paceamaker service does not automatically start on App and DB servers on OS boot.  If the App or DB has pacemaker service enabled to automatically start on boot then steps might differ.  Especially in that case the primary App (ACS) might start on secondary node and ERS might start on primary node.  Hence best option is to have auto-start of pacemaker disabled on machie boot.
 
If that is not possible, we should consider putting secondary node in maintenance mode before removing cluster from maintenance mode using:
<pre>
crm node maintenance <NODENAME>
</pre>
Once cluster services are up and running on primary properly.  Then for secondary node use:
<pre>
crm node ready NODENAME
</pre>
 
 
 
=Stopping services=
For stopping services:
* Stop Application servers
* Stop Database servers
* Stop NFS server
 
 
==Stop Application servers==
To stop application servers use:
To stop application servers use:
# Put the cluster in maintenance mode:
# Put the cluster in maintenance mode:
Line 9: Line 29:
#:</pre>
#:</pre>
# Stop SAP services (PAS & AAS services) with help of SAP Application team
# Stop SAP services (PAS & AAS services) with help of SAP Application team
# Stop cluster services on Slave node
# Stop cluster services on '''Secondary node'''
### Stop pacemaker cluster  
### Stop pacemaker cluster  
##:<pre>
##:<pre>
Line 18: Line 38:
##::  crm status
##::  crm status
##:</pre>
##:</pre>
# Stop cluster services on Master node
# Stop cluster services on '''Primary node'''
## Stop pacemaker cluster  
## Stop pacemaker cluster  
##:<pre>
##:<pre>
Line 29: Line 49:




 
==Stop Database servers==
=Stop Database servers:=
 
To stop database server use:
To stop database server use:
# Put the cluster in maintenance mode:
# Put the cluster in maintenance mode:
Line 38: Line 56:
#:</pre>
#:</pre>
# Stop SAP DB services with help of SAP team
# Stop SAP DB services with help of SAP team
# Stop cluster services on Slave node
# Stop cluster services on '''Secondary node'''
## stop pacemaker cluster
## stop pacemaker cluster
##:<pre>
##:<pre>
Line 52: Line 70:
##:: HDB info
##:: HDB info
##:</pre>
##:</pre>
# Stop cluster services on Master node
# Stop cluster services on '''Primary node'''
## Stop pacemaker cluster
## Stop pacemaker cluster
##:<pre>
##:<pre>
Line 68: Line 86:




=Starting services=


=Start Database servers=
To start services:
* Start NFS servers
* Start database servers
* Start application servers


==Start database servers==
To start database server use:
To start database server use:
# Start cluster services on Master node
# Start HANA DB manually '''on primary node'''. Take Help from SAP team
## Start HANA DB manually. Take Help from SAP team
# Also wait for '''SAP application team''' to start Primary to Secondary replication at DB level.  Once replication to secondary is in proper state, we can proceed further.
# Start cluster services on '''Primary node'''
## Start pacemaker cluster
## Start pacemaker cluster
##:<pre>
##:<pre>
Line 86: Line 111:
##:: crm status
##:: crm status
##:</pre>
##:</pre>
# Start cluster services on Slave node
# After starting the services in master node, '''wait for 5-10 minutes'''. 
## After starting the services in master node, wait for 5-10 minutes
# Start cluster services on '''Secondary node'''
## Start pacemaker cluster
## Start pacemaker cluster
##:<pre>
##:<pre>
Line 98: Line 123:




 
==Start application servers==
=Application servers=
To start application servers use:
To start application servers use:
# Start cluster services on Master node
# Start cluster services on Primary node
##  Start pacemaker cluster
##  Start pacemaker cluster
##:<pre>
##:<pre>
Line 114: Line 138:
##:: crm status
##:: crm status
##:</pre>
##:</pre>
## Start SAP services (PAS & AAS services) with help of SAP Application team
# Check the cluster services on Secondary node
# Check the cluster services on Slave node
## Start cluster on secondary node
## Slave node will automatically restarts, Once the pacemaker cluster started on the Master node
##:<pre>
## Check cluster services status
##:: systemctl start pacemaker
##:</pre>
## Secondary node might automatically restart due to fencing, after the pacemaker cluster is started on the Primary node
## After reboot, again start pacemaker on secondary node and check cluster services status
##:<pre>
##:<pre>
##:: systemctl start pacemaker
##:: crm status
##:: crm status
##:</pre>
##:</pre>
# Start SAP services (PAS & AAS services) with help of SAP Application team.  This typically involves below on both application servers one for ERS and for ASCS:
#:<pre>
#:: su - <sapuser>
#:: startsap
#:</pre>




Line 128: Line 161:




<yambe:breadcrumb self="Pacemaker start and stop for Hana DB and application servers">SAP setup and maintenance|SAP setup and maintenance</yambe:breadcrumb>
[[Main Page|Home]] > [[Suse]] > [[SAP setup and maintenance]] > [[Pacemaker start and stop for Hana DB and application servers]]

Latest revision as of 03:45, 10 April 2024

Home > Suse > SAP setup and maintenance > Pacemaker start and stop for Hana DB and application servers

pacemaker should not auto-start on node after reboot

The below article assumed paceamaker service does not automatically start on App and DB servers on OS boot. If the App or DB has pacemaker service enabled to automatically start on boot then steps might differ. Especially in that case the primary App (ACS) might start on secondary node and ERS might start on primary node. Hence best option is to have auto-start of pacemaker disabled on machie boot.

If that is not possible, we should consider putting secondary node in maintenance mode before removing cluster from maintenance mode using: 

crm node maintenance <NODENAME>

Once cluster services are up and running on primary properly. Then for secondary node use: 

crm node ready NODENAME


Stopping services

For stopping services:

  • Stop Application servers
  • Stop Database servers
  • Stop NFS server


Stop Application servers

To stop application servers use:

  1. Put the cluster in maintenance mode: 
    crm configure property maintenance-mode=true
  2. Stop SAP services (PAS & AAS services) with help of SAP Application team
  3. Stop cluster services on Secondary node
      1. Stop pacemaker cluster
      systemctl stop pacemaker.service
    2. Check services status 
      crm status
  4. Stop cluster services on Primary node
    1. Stop pacemaker cluster 
      systemctl stop pacemaker.service
    2. Check cluster services status 
      crm status


Stop Database servers

To stop database server use:

  1. Put the cluster in maintenance mode: 
    crm configure property maintenance-mode=true
  2. Stop SAP DB services with help of SAP team
  3. Stop cluster services on Secondary node
    1. stop pacemaker cluster 
      systemctl stop pacemaker.service
    2. Check cluster services status 
      crm status
    3. Check HANA DB services status 
      su - <username>
      

      HDB info
  4. Stop cluster services on Primary node
    1. Stop pacemaker cluster 
      systemctl stop pacemaker.service
    2. Check cluster services status 
      crm status
    3. Check HANA DB services status 
      su - <username>
      

      HDB info


Starting services

To start services:

  • Start NFS servers
  • Start database servers
  • Start application servers


Start database servers

To start database server use:

  1. Start HANA DB manually on primary node. Take Help from SAP team
  2. Also wait for SAP application team to start Primary to Secondary replication at DB level. Once replication to secondary is in proper state, we can proceed further.
  3. Start cluster services on Primary node
    1. Start pacemaker cluster 
      systemctl start pacemaker.service
    2. Remove cluster from maintenance mode: 
      crm configure property maintenance-mode=false
    3. Check cluster services status 
      crm status
  4. After starting the services in master node, wait for 5-10 minutes.
  5. Start cluster services on Secondary node
    1. Start pacemaker cluster 
      systemctl start pacemaker.service
    2. Check cluster services status 
      crm status


Start application servers

To start application servers use:

  1. Start cluster services on Primary node
    1. Start pacemaker cluster 
      systemctl start pacemaker.service
    2. Remove cluster from maintenance mode: 
      crm configure property maintenance-mode=false
    3. Check cluster services status 
      crm status
  2. Check the cluster services on Secondary node
    1. Start cluster on secondary node 
      systemctl start pacemaker
    2. Secondary node might automatically restart due to fencing, after the pacemaker cluster is started on the Primary node
    3. After reboot, again start pacemaker on secondary node and check cluster services status 
      systemctl start pacemaker
      

      crm status
  3. Start SAP services (PAS & AAS services) with help of SAP Application team. This typically involves below on both application servers one for ERS and for ASCS: 
    su - <sapuser>
    

    startsap


Refer:


Home > Suse > SAP setup and maintenance > Pacemaker start and stop for Hana DB and application servers

Retrieved from "http://www.sbarjatiya.com/notes_wiki/index.php?title=Pacemaker_start_and_stop_for_Hana_DB_and_application_servers&oldid=8160"