HADR Availability on SAP Adaptive Server Enterprise 16.0
I am pleased to announce the general availability of HA/DR feature for SAP Business Suite on SAP Adaptive Server Enterprise version 16.0 SP02 PL04. This version brings a lot of exciting features that have been highly anticipated.
In the new setup, a lot has changed (for the better). Some of the highlights of the new release are as follows:
- Additional replication modes are now supported with SAP ASE 16.0
- Synchronous Replication Mode (Hot Standby)
- Near-Synchronous Replication Mode (Hot Standby)
- Asynchronous Replication Mode (Warm Standby) – Also present in SAP ASE 15.7
- Only remote distribution mode is supported
- SAP Replication Server will be installed on the same hardware as SAP ASE 16.0 (co-located). No additional hardware is required.
- Additional features for monitoring SAP Replication Server using RMA (Replication Management Agent).
- HA/DR Configuration will be done using a command line utility called “setuphadr” which will make automation a lot easier than in the past.
HA/DR Architecture with SAP ASE 16.0 is as follows:
For more information, see:
- SAP Adaptive Server Enterprise product documentation on SAP Adaptive Server Enterprise 16.0 SP02 – SAP Help Portal Page
- SAP Note relevant to HADR: 1891560
Thanks Wajeeh Samdani,
Can you please more elaborate below.
Where can I get installation documentation.
I checked in installation directory but they have not updated.
One more question when we use Synchronous/Near - Synchronous modes what is the performance impact on the primary system.
Synchronous Replication Mode – ASE 16 only (“Hot Standby” / HA solution)
Near-Synchronous Replication Mode – ASE 16 only (“Hot Standby” / HA solution)
Asynchronous Replication Mode (“Warm Standby”/ DR solution)
Updated documentation "HADR User Guide" will be uploaded to the official documentation page that I linked. Also, you can also find it on SCN at the following link
I guess when you decide to choose which method to use then you need to evaluate your network latency whether it can support sync replication. If your network latency is very good and temporarily there is a latency increase then replication will switch from sync mode to async mode and switch back to sync as soon as latency returns back to normal. The value for defining what is "high latency" is defined by a parameter which as a default value of 500ms. Which means, if latency goes above 500ms then replication will switch to async and as soon as it comes back down below 500ms, it will switch back to sync mode. This additional functionality was added to avoid any major impact on Primary ASE in the case of temporary latency increases.
I have tested HADR on my virtual environment and I have two extra questions:
1. I am not sure what you mean with MSA or regular replication. In a Business Suite scenario, you can only use this setup for HADR purposes.
2. Well, in SAP ASE 16.0 with SAP Business Suite setup, it is not supported to separate ASE and SRS.
Is there any plans to support 3 nodes to allow sync HA in the Primary Datacenter and then async to a Remote Datacenter ?
3 nodes supported for HADR Custom applicaiton but not yet for Business Suite env.
It is now officially supported starting with SAP ASE 16.0 SP03 PL03. See my blog on following link:
Hi Dear All,
I get an error during the HADR configuration like below. Could you please suggest me any solution ?
Status Start Time Tue Jul 18 23:03:23 IRDT 2017
Status Elapsed Time 00:13:22
SetupReplicationTask Task Name Setup replication
SetupReplicationTask Task State Error
SetupReplicationTask Short Description Setup replication between two SAP ASE servers.
SetupReplicationTask Long Description Setting up replication on 'standby' host for local database 'SID'.
SetupReplicationTask Current Task Number 5
SetupReplicationTask Total Number of Tasks7
SetupReplicationTask Task Start Tue Jul 18 23:03:23 IRDT 2017
SetupReplicationTask Task End Tue Jul 18 23:16:45 IRDT 2017
SetupReplicationTask Hostname STB_HOSTNAME
AddASEDatabaseForDisasterRecovery Task Name Add Database to Replication
AddASEDatabaseForDisasterRecovery Task State Error
AddASEDatabaseForDisasterRecovery Short Description Add an ASE database to the Replication System for Disaster Recovery support.
AddASEDatabaseForDisasterRecovery Long Description Adding database 'SID' to the replication server on host 'STB_HOSTNAME'.
AddASEDatabaseForDisasterRecovery Current Task Number 0
AddASEDatabaseForDisasterRecovery Total Number of Tasks20
AddASEDatabaseForDisasterRecovery Hostname STB_HOSTNAME
AddLocalASEDatabaseForDisasterRecoveryTask Name Add Local Database to Replication
AddLocalASEDatabaseForDisasterRecoveryTask State Error
AddLocalASEDatabaseForDisasterRecoveryShort Description Add an ASE database to the local Replication System for Disaster Recovery support.
AddLocalASEDatabaseForDisasterRecoveryLong Description Adding database 'SID' to the replication server on host 'STB_HOSTNAME'.
CreateReplicationServerASEConnection Task Name Create Database Connection
CreateReplicationServerASEConnection Task State Error
CreateReplicationServerASEConnection Short Description Creates a connection to a database to support replication.
CreateReplicationServerASEConnection Long Description Reseting the secondary truncation point for database 'SID'.
CreateReplicationServerASEConnection Hostname STB_HOSTNAME
Please check errorlog of replication server in replication directory under $SYBASE\DM\. Ensure you are able to ping one server from other with hostname/IP address, if not add appropriate details in /etc/hosts
Hi Wajeeh Samdani,
we are planning to Implement DR for our SAP Production Server which is on Cloud and Lanscap is as Follows.
SAP ASE is installed in One Host,
Need to Do A DR which is one should i Implement.
Please provide a Information
Hey Wajeeh Samdani,
Question - We are planning primary and DR only for ASE 16, do we really required Standby(HA node) ? in other words is it compulsory to have HA Node to build DR solution?