Skip to Content

     In my previous posts I have described so far some interesting topics related to SAP Sybase Replication Server (SRS) architecture, e.g., some of the most important features, interesting functionalities, useful techniques and I have even shown integration with other SAP and non SAP products.

     In today’s post I am going to focus on a new SAP solution developed using SAP Sybase Replication Server as key point to allow SAP customers implement a Disaster Recovery system for Business Suite on ASE. This new Solution is called HADR for Business Suite on ASE and was available in July 2013.

     HADR for Business Suite architecture

     In the SAP SRS architecture for Business Suite disaster recovery on ASE we have the usual components we have in normal SAP SRS systems plus one new component developed specifically for this solution called Distaster Recovery Agent (DR Agent):


    • Primary SAP system:

                         SAP production system where users are connected in a normal situation

    • Standby SAP system:

SAP standby system, no users are connected in a normal situation, the only database transactions

applied here are sent by SAP Sybase Replication Server to keep the system up to date


    • Replication servers:

                         One Replication Server is configured with each SAP system


    • Disaster Recovery Agent:

                         New component developed by SAP SRS engineering to simplify HADR installation, configuration and



    • SAP installer (Software Provisioning Manager):

                         Used for both installing SAP SRS software and configuring HADR system. Check screen shotbelow

                         to see installation integrated with SAP installer:



  • SAP Sybase ASE should be version 15.7 SP102 or higher
  • SAP Sybase Replication Server version should be 15.7.1 SP102 or higher.


     HADR solution for Business Suite on ASE consists of 3 Multiple Site Availability (3 database replication definitions and 3 subscriptions) created for each of the 2 possible replication directions, that is, from Primary system to Standby system and from Standby system to Primary system. The 3 databases that are going to be replicated are:


  • Master (logins and users have to be synchronized between both servers)
  • Saptools
  • SAP System DB

    DR Agent

     As said before DR agent is a new component created to ease installation, configuration and monitoring for the HADR system, its function basically is to execute both ASE and Replication Server commands that you would otherwise execute manually. DR Agent has its own API with specific commands (for example sap_status, sap_disable_replication, sap_enable_replication … etc)

     DR Agent Capabilities:


     1.- Simplify the setup of a Business Suite disaster recovery environment

    • Consolidate the steps required to establish the environment
    • Establish a standard replication configuration
    • Support servers configured on separate hosts 
    • Integrate with the SAP Business Suite Installer (DBA Cockpit and DBCntrl − coming soon)

     2.- Automate the failover process

    • Reverse the direction of replication
    • Support both planned and unplanned events
    • Provide solutions for different recovery scenarios

      3.- Monitor replication

    • Availability of servers, connections, and routes
    • Replication Latency

More details in SAP Sybase documentation:

Other/Related Posts:

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member

    Hi Javier,

    I’ve got a comment from two SAP IT colleagues who like the document but (after checking back w/ development) stated that the saptools DB is not supposed to be replicated.

    Thanks & regards


    1. Javier Martin Post author

      Hi Volker,

      First of all thanks a lot for your comment. In the current HADR architecture 3 databases are replicated es explained in this post and the config tool is prepared to start replication for those 3 dbs, there is not way to avoid replication for saptools. It would be great if I can contact our IT colleagues to discuss about this and if saptools is not supposed to be replicated then we should talk to SRS engineering and discover why it is done and check it it can be removed.

      Can you send me an email copying IT people to talk about this ?.



      1. Former Member

        Dear Javier

        We are planning to set SRS – DR in our ECC6 with EHP6 Business suit 2011 on Windows 2008 R2 with Sybase ASE 110.

        Please advise any manual activities to be done before installing SRS.



        1. Javier Martin Post author

              Hi Laurus,

              Basillaly you have to install ERP in both Windows boxes, identical installations with same SID.

              Please contact me by email and we can discuss some details.



  2. Former Member

    Hi Javier,

    We are having a SAP Business object business intelligence software (BOBI) with Sybase ASE as database for CMS and auditing store. Can we use the same steps/documentation as for HADR for business suite on ASE ?  Since BOBI is not a typical application based on SAP Netweaver.



    1. Javier Martin Post author

      Hi Vikash,

      The architecture described in the blog is valid only for SAP BS applications, it is not certified for BOBI CMS db and indeed will not work.

      You have other solutions you can try:

      1.- Check HADR Architecture on ASE 16 SP02 (Always-on option), Take a look at this other blog I created weeks ago:

      2.- Use the typical SAP Replication server Warmstandby architecture:



      1. Nicholas Chang

        Hi Javier,

        SAP SRS only supports business suite, any update on BW or netweaver? Based on one of the SRS note, BW is currently not supported.

        Therefore, is warm standby supported? as it only support to replicate one database. correct me if i’m wrong.


        Nicholas Chang

  3. Former Member

    Dear Javier,

    We are planning to migrate (OS) from WIN SRV 2008 to WIN SRV 2012 R2 using Export/Import Method.

    Our Current DB is ASE 15.7 and Target DB will be 16.0.

    We also want SAP clustering to be installed and Configured in our PROD environment to make it  zero downtime.

    Could you please guide us with the steps we need to follow to make it success.

    Thanks in advance…


    Gouri Prasad


Leave a Reply