Scribd
Upload
79 views

SAHANA for System Replication in SAP Solution Manager

Uploaded by

viteco1094
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
79 views

SAHANA for System Replication in SAP Solution Manager

Uploaded by

viteco1094
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Configuring SAP HANA for System Replication

Technical Scenario in SAP Solution Manager


To model an SAP HANA system replication landscape in SAP Solution Manager as a
technical scenario, you must configure SAP HANA to send the correct landscape data to
the Landscape Management Database (LMDB) via the System Landscape Directory
(SLD). SAP Solution Manager uses the system information managed in the LMDB.

System replication is a mechanism for ensuring the high availability of SAP HANA
systems, as well as disaster recovery. Through the continuous replication of data from a
primary to a secondary system, system replication

Landscape Configuration Settings Define Virtual Databases


(sldvirtdbhome)

A virtual database is the logical host name under which an SAP HANA database can
always be reached for the purposes of takeover. This ensures that application systems
remain associated with the correct database in SLD when a secondary system takes over
from the primary system.

In each SAP HANA system in the system replication landscape, configure a virtual
database at the system level, or if desired for each individual tenant database, by setting
the parameter [system_landscape_hostname_virtualization]
sldvirtdbhome in the global.ini file of the system database. This will result in
each virtual database being registered in SLD as an SAP_HDBSystem object
(<database_name>.DBTypeForSAP.HDB.SystemHome.<sldvirtdbhome>
).

Note the following:

● If you don't configure a value in the global.ini of each tenant database,


the value configured in the global.ini of the SYSTEMDB applies. If you
don't configure a value in the global.ini of the SYSTEMDB, the value of
the SLDVIRTDBHOME parameter in the default system profile
(hana/shared/ <sid>/profile/DEFAULT.PFL) is used; or if this value
hasn't been set, the host name from the landscape properties file
(hana/shared/<sid>/lm_structure/landscapeVariables.prop
erties).

● Important: Configure a virtual database name for either all tenants or none. If
some tenants are configured and some are not, the fallback values mentioned
above are not used for those tenants without a configured value. In this case, the
data supplier does not deliver this tenant completely and an error is written to the
indexserver trace: "e SLDCollect logical database hostname =
<empty>".

● Changing the sldvirtdbhome parameter in the global.ini file does


not require a restart, whereas changing the default profile does. Define Physical
Databases (sldsystemhome) A physical database is the logical host name
used to identify an SAP HANA database independently of internal host names for
the purposes of auto-host failover. Since the host names of master and standby
hosts are different, configuring a single physical database ensures that the same
database is registered in SLD after a failover as before. In each SAP HANA
system in the system replication landscape, you configure a unique physical
database at the system level, or if desired for each individual tenant database, by
setting the parameter SAP HANA Administration Guide for SAP HANA Platform
164 PUBLIC SAP HANA Administration Tools

̓ Note

The following configuration must be in place before you enable system replication on the
primary system and register secondary systems.

[system_landscape_hostname_virtualization] sldsystemhome in
the global.ini file of the system database. This will result in each physical database
being registered in SLD as an SAP_HDBSystem object
(<database_name>.DBTypeForSAP.HDB.SystemHome.<sldsystemhome>
).

Note the following:

● The LMDB does not support fully qualified domain names (FQDNs). We
therefore recommend specifying physical databases without domain names. The
data supplier will remove domains before sending physical databases to SLD.

● If you don't configure a value in the global.ini of each tenant database,


the value configured the global.ini of the SYSTEMDB applies. If you don't
configure a value in the global.ini of the SYSTEMDB, the value of the
SLDSYSTEMHOME parameter in the default system profile (hana/shared/
<sid>/profile/DEFAULT.PFL) is used; or if this value hasn't been set, the
host name from the landscape properties file
(hana/shared/<sid>/lm_structure/landscapeVariables.prop
erties).
● Important: Configure a physical database for either all tenants or none. If some tenants
are configured and some are not, the fallback values mentioned above are not
used for those tenants without a configured value. In this case, the data supplier
does not deliver this tenant completely and an error is written to the indexserver
trace: "e SLDCollect logical computer hostname = <empty>".

● Changing the sldsystemhome parameter in the global.ini file does


not require a restart, whereas changing the default profile does.

Configure the Dependency Chain In a system replication landscape, communication


between primary and secondary systems is based on internal host names. This
ensures that each site can resolve the host name of other sites and that the
replication chain can switch seamlessly in the event of a takeover. To model the
dependency relationship between databases in the replication chain in SLD, the
physical databases must be mapped to the internal host names of the systems to
which they belong. In the system_landscape_hostname_resolution
section of the global.ini file of the system database, create an entry for all
internal host names in the system replication landscape and as the value, set the
physical database available on the host. We recommend you do this in all
systems. The dependency relationship between databases will be modeled in SLD
with the association
SAP_DatabaseReplicationDependency. Association of Virtual and
Physical Names (enable_virtdbhome) Once the above configuration is in
place, the virtual and physical databases must be associated. This takes place
implicitly when the secondary system is registered with the primary system. With
the sr_register command, the parameter [sld] enable_virtdbhome
in the nameserver.ini file is set to true in the primary system and to false
in the secondary system(s). This results in the virtual databases being associated
with the physical databases of the primary system in SLD with the association
SAP_IdenticalDatabaseSystem. In the event of a takeover
(sr_takeover), the value of this parameter is set to true in the new primary
system and to false in the original primary system, thus changing the association
of virtual databases to the physical databases in the new primary.

You might also like