Difference between revisions of "Pacemaker start and stop for Hana DB and application servers"
m |
m |
||
Line 97: | Line 97: | ||
To start database server use: | To start database server use: | ||
# Start HANA DB manually '''on primary node'''. Take Help from SAP team | # Start HANA DB manually '''on primary node'''. 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 cluster services on '''Primary node''' | ||
## Start pacemaker cluster | ## Start pacemaker cluster | ||
Line 110: | Line 111: | ||
##:: crm status | ##:: crm status | ||
##:</pre> | ##:</pre> | ||
# 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 cluster services on '''Secondary node''' | ||
## Start pacemaker cluster | ## Start pacemaker cluster | ||
Line 137: | Line 138: | ||
##:: crm status | ##:: crm status | ||
##:</pre> | ##:</pre> | ||
# Check the cluster services on Secondary node | # Check the cluster services on Secondary node | ||
## Slave node might automatically restart due to fencing, after the pacemaker cluster is started on the Primary node | ## Slave node might automatically restart due to fencing, after the pacemaker cluster is started on the Primary node | ||
Line 144: | Line 144: | ||
##:: crm status | ##:: crm status | ||
##:</pre> | ##:</pre> | ||
# Start SAP services (PAS & AAS services) with help of SAP Application team | |||
Revision as of 15:21, 17 April 2022
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:
- Put the cluster in maintenance mode:
- crm configure property maintenance-mode=true
- Stop SAP services (PAS & AAS services) with help of SAP Application team
- Stop cluster services on Secondary node
- Stop pacemaker cluster
- systemctl stop pacemaker.service
- Check services status
- crm status
- Stop cluster services on Primary node
- Stop pacemaker cluster
- systemctl stop pacemaker.service
- Check cluster services status
- crm status
- Stop pacemaker cluster
Stop Database servers
To stop database server use:
- Put the cluster in maintenance mode:
- crm configure property maintenance-mode=true
- Stop SAP DB services with help of SAP team
- Stop cluster services on Secondary node
- stop pacemaker cluster
- systemctl stop pacemaker.service
- Check cluster services status
- crm status
- Check HANA DB services status
- su - <username>
- HDB info
- stop pacemaker cluster
- Stop cluster services on Primary node
- Stop pacemaker cluster
- systemctl stop pacemaker.service
- Check cluster services status
- crm status
- Check HANA DB services status
- su - <username>
- HDB info
- Stop pacemaker cluster
Starting services
To start services:
- Start NFS servers
- Start database servers
- Start application servers
Start database servers
To start database server use:
- Start HANA DB manually on primary node. 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
- systemctl start pacemaker.service
- Remove cluster from maintenance mode:
- crm configure property maintenance-mode=false
- Check cluster services status
- crm status
- Start pacemaker cluster
- After starting the services in master node, wait for 5-10 minutes.
- Start cluster services on Secondary node
- Start pacemaker cluster
- systemctl start pacemaker.service
- Check cluster services status
- crm status
- Start pacemaker cluster
Start application servers
To start application servers use:
- Start cluster services on Primary node
- Start pacemaker cluster
- systemctl start pacemaker.service
- Remove cluster from maintenance mode:
- crm configure property maintenance-mode=false
- Check cluster services status
- crm status
- Start pacemaker cluster
- Check the cluster services on Secondary node
- Slave node might automatically restart due to fencing, after the pacemaker cluster is started on the Primary node
- Check cluster services status
- crm status
- Start SAP services (PAS & AAS services) with help of SAP Application team
Refer:
Home > Suse > SAP setup and maintenance > Pacemaker start and stop for Hana DB and application servers