Difference between revisions of "Stopping and starting all LPARS deployed on power servers for SAP App and DB"

From Notes_Wiki
m
m
Line 44: Line 44:
# Start primary physical host
# Start primary physical host
# Start seconday physical host
# Start seconday physical host
# Start primary VIOS server
# Start primary VIOS server (Activate -> Normal)
# Start secondary VIOS server
# Start secondary VIOS server (Activate -> Normal)
# Start Database primary LPAR.
# Start all LPARs on primary host (Activate -> Normal)
# Start Database secondary LPAR.  
# Start all LPARs on secondary host (Activate -> Normal)
# Start NFS and Database servers as per [[Pacemaker start and stop for Hana DB and application servers]]
# SAP team should start SAP DB on primary server.
# Start the Application Primary LPAR
#: See [[Pacemaker start and stop for Hana DB and application servers]]
# Start the Application Secondary LPAR
# Start pacemaker services on primary DB host and remove cluster from maintenance mode.
# Start APP services in Primary & Secondary nodes as per [[Pacemaker start and stop for Hana DB and application servers]]
#:<pre>
# Start all the LPARs
#::        systemctl start pacemaker.service
#: Note: Backup LPAR should start last
#::        crm configure property maintenance-mode=false
#::        crm status
#:</pre>
# After 5 minutes start pacemaker services on secondary DB host:
#:<pre>
#::        systemctl start pacemaker.service
#::        crm status
#:</pre>
# After DB is successfully up along with primary to secondary replication, Start App cluster on primary host:
#:<pre>
#::        systemctl start pacemaker.service
#::        crm configure property maintenance-mode=false
#::        crm status
#:</pre>
# After this start pacemaker cluster on secondary App host
#:<pre>
#::         systemctl start pacemaker.service
#::        crm status
#:</pre>
#: Secondary App host might reboots automatically before becoming part of cluster.
 


Refer:
Refer:

Revision as of 11:41, 17 April 2022

Home > Suse > SAP setup and maintenance > 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

  1. Put both application and DB clusters in maintenance mode using: 
    crm configure property maintenance-mode=true
    See Pacemaker start and stop for Hana DB and application servers
    No point in stopping pacemaker service as anyway we are going to shutdown the LPARs
  2. Stop SAP Application and then SAP DB
  3. We can use vMHC to shutdown all LPARS using graphical shutdown option. After selecting shutdown choose "Operating System" option. There are also option such as "Delayed", "Immediate" or "Operating System Immediate".
    Refer: https://www.redbooks.ibm.com/redbooks/pdfs/sg247491.pdf
  4. Or if vHMC based shutdown is not preferred, shutdown all the LPAR's using: 
    shutdown -h now
  5. Shutdown second VIOS server
    In vHMC after clicking on a power server we get options such as LPARS and "VIOS Servers". LPARS are visible under LPARS and "VIOS servers" are visible under VIOS server. Same as for LPAR choose action "Shutdown" with option "Operating System"
  6. Shutdown first VIOS server
  7. Shutdown second physical host
    This can be done from vHMC. There is option to poweroff the servers.
  8. Shutdown first physical host
  9. Shutdown HMC VM
    You might have to poweroff (unclean shutdown) of VM from ESXi. Still need to figure out how to shutdown vHMC VM properly.
  10. Shutdown Physical server hosting HMC VM
  11. Shutdown storage
    In a few storages option to shutdown can be part of Monitoring tab.
  12. Shutdown Tape Library
    There might be option to change "Library State" to Offline, if there is no shutdown option.


SAP Infra start up procedure

  1. Start Tape Library
    Might have to change Library state to Online
  2. Start storage
    In a few storages there is only option to shutdown. There is no power on button. As soon as A/C power is restored the storage might get powered on automatically.
  3. Start host where vHMC VM is deployed. This can be done using OOBE such iDRAC, IMM or iLO, etc.
  4. Start HMC VM after ESXi has booted properly.
    Note: After storage, wait for 15-20mins for start physical hosts
  5. Start primary physical host
  6. Start seconday physical host
  7. Start primary VIOS server (Activate -> Normal)
  8. Start secondary VIOS server (Activate -> Normal)
  9. Start all LPARs on primary host (Activate -> Normal)
  10. Start all LPARs on secondary host (Activate -> Normal)
  11. SAP team should start SAP DB on primary server.
    See Pacemaker start and stop for Hana DB and application servers
  12. Start pacemaker services on primary DB host and remove cluster from maintenance mode. 
    systemctl start pacemaker.service
    

    crm configure property maintenance-mode=false
    

    crm status
  13. After 5 minutes start pacemaker services on secondary DB host: 
    systemctl start pacemaker.service
    

    crm status
  14. After DB is successfully up along with primary to secondary replication, Start App cluster on primary host: 
    systemctl start pacemaker.service
    

    crm configure property maintenance-mode=false
    

    crm status
  15. After this start pacemaker cluster on secondary App host 
    systemctl start pacemaker.service
    

    crm status
    Secondary App host might reboots automatically before becoming part of cluster.


Refer:


Home > Suse > SAP setup and maintenance > Stopping and starting all LPARS deployed on power servers for SAP App and DB

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