Volsync rysnc for dr strategy

[chaitutvsk1989]

DR Scenario -
Source - Dr
Dr - Source

How can we implement rysnc in both sides?
As we know rsync is 1-1 but we wanted it to get implemented for Dr case on both sides.

Every Saturday we will have one hour to sync pvcs around 60 pvcs Source to destination & service will be running in Dr site for two weeks.

Again after two weeks later we will come back from dr back to Source cluster.

What is best way to set async rsync volsync in both sides ? what type of trigger we should choose? For the users to have the files in pvc consistent and with out any corruption ??

@tesshuflower please help.

[tesshuflower]

Hi @chaitutvsk1989

Let's say site A is your original source and site B is your destination:

You would need to setup a ReplicationDestination on B and then a ReplicationSource on A. After you've done a failover and your app is backup and running, you could then reverse the process and create a ReplicationDestination on B (and you can point this to your old PVC) and a ReplicationSource on site A.

When it comes to your own controlled failover, I would suggest:

• Stop your app on A
• Set a manual trigger on your replicationsource on A - to do one final sync.
• After the sync is complete, you can convert the snapshot on B to a PVC (you can use volume populator for this to make it easier).

Generally during normal operation of let's say A syncing to B - you can use a cron trigger to schedule that you want to sync over specific intervals - this way the data on B is up-to-date after every interval. And then during your final controlled failover, you are only sending the data from the time of the last sync interval until you shut down your app.