The SAP HANA Recovery Kit is able to function in an environment with multiple tenant databases. However, please be aware of the following behaviors and special considerations:
- SAP HANA System Replication (HSR) must be able to successfully initialize replication for all tenant databases on the system in order for the HSR monitoring in the recovery kit to function correctly. This means, for example, that backups must be taken of all tenant databases before enabling HSR. If HSR is out-of-sync for any of the tenant databases contained within the protected instance, the SAP HANA Recovery Kit will leave the !HANA_DATA_OUT_OF_SYNC flag on the standby system, preventing switchover or failover of the SAP HANA resource hierarchy.
- The SAP HANA Recovery Kit currently does not restart individual tenant databases if they are manually stopped (e.g., with an HDBSQL ‘alter system stop database DB_NAME’ command). In this case, the SAP HANA software removes the corresponding indexserver process from the list of processes for the HDB instance, and the SAP HANA Recovery Kit will treat the manual stoppage of the tenant database as intentional.
- The SAP HANA Recovery Kit currently does not monitor the tenant databases at an individual level. It monitors the entire HDB instance (which will contain indexserver processes for each running tenant database) as a whole. If any process in the HDB instance has failed, the recovery kit will attempt to restart the entire instance. This means, for example, that the indexserver process for TENANT1 may be restarted unexpectedly in the case that the indexserver process for TENANT2 fails.
Thanks for your feedback.
Post your comment on this topic.