SAPHanaSR_maintenance_examples(7)

NAME
SAPHanaSR_maintenance_examples - maintenance examples for SAPHana and SAPHanaController.

DESCRIPTION

Please see also the REQUIREMENTS section below.

EXAMPLES

* Initiate an administrative takeover of the HANA primary from one node to the other one. If the cluster should also register the former primary as secondary, AUTOMATED_REGISTER="true" is needed. Before the takeover will be initiated, the status of the Linux cluster and the HANA system replication has to be checked. The takeover should only be initiated as forced migration. After takeover of the primary has been finished, the migration rule has to be deleted. If AUTOMATED_REGISTER="true" is set, finally the former primary will be registred as secondary, once the migration rule has been deleted.

    # cs_clusterstate -i
    # SAPHanaSR-showAttr
    # crm configure show | grep cli
    # crm resource migrate msl_SAPHana_SLE_HDB10 force
    # cs_clusterstate -i
    # SAPHanaSR-showAttr
    # crm resource unmigrate msl_SAPHana_SLE_HDB10
    # SAPHanaSR-showAttr

* Manually start the HANA primary if only one node is available. This might be necessary in case the cluster could not detect the status of both nodes.

    1. Start the cluster on both nodes.
    2. Wait and check for cluster is running, and in status idle.
    3. Become sidadm, and start HANA manually.
    4. Wait and check for HANA is running.
    5. In case the cluster does not promote the HANA to primary, instruct the cluster to migrate the IP adress to that node.
    6. Wait and check for HANA has been promoted to primary by the cluster.
    7. Remove the migration rule from the IP adress.
    8. Check if cluster is in status idle.
    9. You are done, for now.
    10. Please bring back the other node and register that HANA as soon as possible. If the HANA primary stays alone for too long, the log area will fill up.

* Overview on maintenance procedure for HANA, the Linux cluster remains running.

    1. Set the Linux cluster into maintenance mode (crm configure property maintenance-mode=true)
    2. Perform the HANA maintenance, e.g. update to latest SPS
    3. Set the SAPHanaController master/slave resource to unmanaged (crm resource unmanage <resource>)
    4. Set the Linux cluster back into ready mode (crm configure property maintenance-mode=false)
    5. Cleanup the SAPHanaController master/slave resource (crm resource cleanup <resource> node <node>)
    6. Set the SAPHanaController master/slave resource back to managed (crm resource manage <resource>)
    7. Check if everything looks fine (crm_mon -1r, cs_clusterstate -i,
     SAPHanaSR-showAttr).

Note: The YaST module hana_updater does something similar, combined with an administrative takeover.

FILES

REQUIREMENTS
For the current version of the resource agents that come with the software packages SAPHanaSR and SAPHanaSR-ScaleOut, the support is limited to the scenarios and parameters described in the respective manual pages SAPHanaSR(7) and SAPHanaSR-ScaleOut(7).

BUGS
In case of any problem, please use your favourite SAP support process to open a request for the component BC-OP-LNX-SUSE. Please report any other feedback and suggestions to feedback@suse.com.

SEE ALSO
ocf_suse_SAPHanaTopology(7) , ocf_suse_SAPHana(7) , ocf_suse_SAPHanaController(7) , SAPHanaSR-monitor(8) , SAPHanaSR-showAttr(8) , SAPHanaSR(7) , SAPHanaSR-ScaleOut(7) , cs_clusterstate(8) , crm(8) , crm_simulate(8) , crm_mon(8) ,
https://www.suse.com/products/sles-for-sap/resource-library/sap-best-practices.html , https://www.suse.com/media/presentation/TUT90846_towards_zero_downtime%20_how_to_maintain_sap_hana_system_replication_clusters.pdf

AUTHORS
F.Herschel, L.Pinne.

COPYRIGHT
(c) 2017-2018 SUSE Linux GmbH, Germany.
(c) 2019 SUSE LLC
This maintenance examples are coming with ABSOLUTELY NO WARRANTY.
For details see the GNU General Public License at http://www.gnu.org/licenses/gpl.html