View source for Stopping and starting all LPARS deployed on power servers for SAP App and DB

<yambe:breadcrumb self="Stopping and starting all LPARS deployed on power servers for SAP App and DB">SAP setup and maintenance|SAP setup and maintenance</yambe:breadcrumb>
=Stopping and starting all LPARS deployed on power servers for SAP App and DB=

It is possible to required shutting down all LPARs, followed by power server for some UPS / Cooling / Network maintenance activity at DC.  In such cases to shutdown and start entire SAP related infrastructure refer below steps:


==SAP Infra shutdown process==
# Put the Linux cluster related to SAP App and DB in maintenance mode
# SAP team should stop application servers
# SAP team should stop database servers
# Stop the pacemaker cluster serives in Application & Database servers as per [[Pacemaker start and stop for Hana DB and application servers]]
# Shutdown all the LPAR's using:
#:<pre>
#:: shutdown -h now
#:</pre>
#: Note: Backup LPAR should be powered of at last
# Shutdown second VIOS server
# Shutdown first VIOS server
# Shutdown second physical host
# Shutdown first physical host
# Shutdown HMC VM
# Shutdown Physical server hosting HMC VM
# Shutdown storage
# Shutdown Tape Library



==SAP Infra start up procedure==

# Start Tape Library
# Start storage
# Start Dell host
# Start HMC VM
#: Note: After storage, wait for 15-20mins for start physical hosts
# Start primary physical host
# Start seconday physical host
# Start primary VIOS server
# Start secondary VIOS server
# Start Database primary LPAR. 
# Start Database secondary LPAR. 
# SAP team start the Database in both the LPARs, Replication between the databases should work
# Start the pacemaker cluster in primary node  as per [[Pacemaker start and stop for Hana DB and application servers]]
# Start the pacemaker cluster in secondary node
#: Primary and Secondary nodes cluster services are in maintanence mode, because custer services was stopped in the maintenance mode state
# Get confirmation from SAP team on Database & Replication services working status
# Remove the database primary node from the maintenance using:
#:<pre>
#:: crm node ready <nodename>
#:</pre>
# Remove the database secondary node from the maintenance
# Get confirmation from SAP team on the Database & Replication services working status
# After nodes are in online state, Then only cluster services is in start state.  Check cluster services health using:
#:<pre>
#:: crm status
#:</pre>
# Start the Application Primary LPAR
# Start the Application Secondary LPAR
#: Primary and Secondary nodes are in maintanence mode, because custer services was stopped in maintenance mode state
# Remove the Application primary node from the maintenance using:
#:<pre>
#:: crm node ready <nodename>
#:</pre>
# Remove the Application secondary node from the maintenance. 
# After nodes are in online state, Then cluster services is in start state and able to see all the mount points
# SAP team will start APP services in Primary & Secondary nodes as per [[Pacemaker start and stop for Hana DB and application servers]]
# Start all the LPARs
#: Note: Backup LPAR should start last



Refer:
* https://documentation.suse.com/sle-ha/15-SP1/html/SLE-HA-all/cha-ha-maintenance.html



<yambe:breadcrumb self="Stopping and starting all LPARS deployed on power servers for SAP App and DB">SAP setup and maintenance|SAP setup and maintenance</yambe:breadcrumb>