Skip to Content
Technical Articles

DR Drill for HANA 2.0 multi-tier replication with reverse replication

Hi Everyone,

 

This is my first blog:)

I have been trying to achieve reverse replication in HANA 3 tier replication environment avoiding full sync. I have referred many HANA replication blogs and thought to write one having clear picture how it works.

 

Here we have 3 Sites

Site A to Site B (Replication type : SyncMem, operation mode : logreplay)

SiteB to Site C (Replication type : Async, operation mode : logreplay)

 

Below is the graphical representation for DR drill which is performed

 

 

 

Before starting DR drill we need to set below parameter on all 3 Site and restart DB

enable_log_retention = force_on_takeover

So that log will be retained during replication for all direct secondaries until a takeover is executed.

for more information on above parameter you can refer below link

https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.03/en-US/004f3015b0d4410b89084c7aa5e45dfe.html

 

Starting DR drill

  1. Take backup of Site A (Primary DB)
  2. Verify the evidence which needs to be validate on DR
  3. Stop sap application
  4. Verify that all sites are in sync

 

 

5. Stop DB of siteA

6. login to Site B and perform takeover

 

 

 

after takeover is performed. you can check replication between SiteB and SiteC must be still active (This can be verify from SiteB)

 

 

7. Now shutdown DB of SiteB using HDB Stop

8. Login to SiteC and perform takeover

 

 

Once takeover is performed, we have to do reverse replication now

 

9. Login to Site B and click register secondary system

 

 

Here do not release initiate full data shipping to avoid full sync.

This will start the delta replication between SiteC to SiteB

 

 

10. Now, Enable replication on SiteB so that we can register SiteA to SiteB as tertiary.

 

Login to Site B and click enable replication

 

11. Now login to SiteA and click  register secondary system

 

 

 

 

This will start full sync between SiteB to SiteA but as both are in same datacenter it will complete in short time

 

 

This will setup the reverse replication from Site C to Site B to Site A

Now we can do fall back once all the testing is completed on Site C

Below are the steps

  1. Shutdown Site C
  2. Perform Takeover on Site B
  3. shutdown Site B
  4. Perform Takeover on Site A
  5. Register Site B to Site A (This will be delta sync)
  6. Enable replication on Site B
  7. Register Site C to Site B (This will be full sync)
  8. Once DR drill is completed you can revert the parameter enable_log_retention same as before.

 

With above mentioned steps we have save larger amout of time taken in Full sync during HANA DB replication.

Also can complete the DR testing in shorter time duration.

More over transaction performed in DR is not loss due to reverse replication. 🙂

 

Hope this is helpful.

 

Regards

Bhargav Bhatt

 

 

4 Comments
You must be Logged on to comment or reply to a post.
  • Hi Bhargav,

    Congratulations on your first blog post. Very easy steps and good to see the reverse replication.
    Just a question from my side, at step 9 and step 11, while registering SITE-B and SITE-A again, we used replication mode ‘Async’ for both of them. Can we register SITE-B as ‘Sync’ ?

    Best Regards,
    Vivek Sahu

    • HI Vivek,

      Thank you very much 🙂

      Yes, you can register Site B as ‘Sync’ and operation mode as logreplay.

      If both site are in same Data-center

       

      Regards

      Bhargav Bhatt

  • Good article Bhargav Bhatt

    I have a query.

    In step 4 , your studio screen from Site A shows both Site B (SYNCMEM) and Site C (ASYNC) . I believed only direct secondary could be seen from its Primary database studio because sql ports are disabled for logreplay and read-enabled for logreplay_readccess.

    A can know B because B is directly registered to A. How does Hana studio at A know about Site C which is secondary to B ?