SAP BASIS-1 SOLUTION

Here i am explaining different replication Modes between Sites in the HANA Replication setup. Synchronous (SYNC) : The secondary system sends an acknowledgment back to the primary system as soon as the data is received and persisted to the log volumes on disk. Asynchronous (ASYNC): Asynchronous replication, the primary does not wait until the secondary sends an acknowledgement. Synchronous in-memory (SYNCMEM):The secondary system sends an acknowledgment back to the primary system as soon as the data is received in memory. The disk I/O speed on the secondary system doesn’t influence the primary’s performance. Site Distance  Replication Mode  < 100 KM SYNC ……

Parameter : allocationlimit  Key Highlights : This parameter is very useful in the Multi-tenant database container (MDC) system to set memory limit on each tenant system. Example : If we have 4 tenant systems in the landscape then we can set on indexsever.ini file –> allocationlimit for each tenant system to the accepted memory limit for each tenant system. Parameter: allocationlimit Description: Sets an upper limit of memory usable by individual processes in megabytes. When set to 0 or missing, the SAP HANA system implicitly calculates a default value based on global_allocation_limit. Multi-tenant database container (MDC) systems: In a tenant database, the parameter ……

Parameter: interval   Description: Sets a time interval in seconds between two checks for differences of ini file parameters between primary and secondary systems in a system replication scenario. To disable/enable those checks, set the parameter [inifile_checker] enable. Value: Positive integer   Default: 3600 (seconds = 1 hour)   Restart required: No     Ref: SAP HANA Admin Guide and Frequently Used Configuration Parameters in SAP HANA

Key Highlights: This parameter will help in the scenario where we don’t want to replicate few parameter from primary to secondary site. Scenario where we want to have different value of particular parameters in primary and secondary site. This parameter is helpful where replication on the primary site with [inifile_checker]/replicate = true is enables With parameter replication activated, any changes made on the primary are automatically replicated to the secondary sites; without this parameter replication activated changes should be manually duplicated on the other system.   Parameter: exclusion_[<inifilename>|*][/<LAYER>] Description: The ini file name can be replaced with an asterisk. The LAYER ……

  inifile_checker –> enable = True  &  [inifile_checker]/replicate = true Key Highlights : [inifile_checker]/replicate = true- This parameter is very useful in the scenario where we have muli -tier and multi-target replication setup in the landscape . If we are changing any parameter in the primary site and [inifile_checker]/replicate = true- parameter is enabled then automatically it will be reflected in the secondary site . It helps to sync-up the parameters across all the HANA sites . If we don’t have [inifile_checker]/replicate = true : parameters set on HANA then there are chances that if we are changing any parameter in the primary site then ……