SAP server maintenance overview

From Notes_Wiki
Revision as of 04:40, 6 April 2022 by Saurabh (talk | contribs) (Created page with "Home > Suse > SAP setup and maintenance > SAP server maintenance overview =Scheduled maintenance= Following different scenarios are possible for base IT infrastructure maintenance for SAP servers: ; Only App and DB software maintenace : In this case we can stop or start SAP cluster using Pacemaker start and stop for Hana DB and application servers ; Entire power servers and LPARs need to be powered off and on : In this case we can follow th...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Home > Suse > SAP setup and maintenance > SAP server maintenance overview

Scheduled maintenance

Following different scenarios are possible for base IT infrastructure maintenance for SAP servers:

Only App and DB software maintenace
In this case we can stop or start SAP cluster using Pacemaker start and stop for Hana DB and application servers
Entire power servers and LPARs need to be powered off and on
In this case we can follow the sequence described at Stopping and starting all LPARS deployed on power servers for SAP App and DB


Primary server failure

In any kind of primary server failure (App or DB)

  • Secondary will automaticlly become primary. Primary App or DB will start running from Secondary
    Owner:Automatic
  • Put cluster in maintenance mode
    Owner: IT Infrastructure team
  • Fix issue with primary server (Hardware / OS /SAP)
    Owner:Appropriate teams
  • Shutdown App or DB from secondary server
    Owner:SAP Application/DB team
  • Validating that replication between primary and secondary is working properly
    Onwer: SAP Application/DB team
  • Reboot both primary and secondary nodes
    Owner: IT Infrastructure team
  • After this follow Pacemaker start and stop for Hana DB and application servers


Secondary server failure

  • Nothing happens to production : Primary continues to be primary. Dev/QA running from secondary will stop.
    Owner: Automatic
  • Put cluster in maintenance mode
    Owner: IT infrastructure team
  • Fix issue with secondary server (Hardware / OS / SAP)
    Owner:Appropriate teams
  • Validating that replication between primary and secondary working properly
    Owner: SAP Application/DB team
  • Reboot secondary node
    Owner: IT infrastructure team
  • After this follow Pacemaker start and stop for Hana DB and application servers



Home > Suse > SAP setup and maintenance > SAP server maintenance overview