-
- Enthusiast
- Posts: 26
- Liked: never
- Joined: Feb 01, 2018 4:14 pm
- Full Name: juan cruz
- Contact:
Bi directional Replication
Hello everyone. I have this scenario:
We have two backup servers located at different sites: primary site and DR site. We're planning to failover on our DR Veeam Backup Server. On that server we have multiple replication jobs of VMs located on primary site.
Now, what we need besides the failback to production once the test is over (one week duration) is that when the failover is executed, VMs with status "Failover" have a "Inverse Replica" on primary site. At this moment this scenario is not being performed as this is for DR Tests only.
Is this possible? The link between both sites is 1Gb and it might be an important limitation to perform it.
Thanks in advance.
We have two backup servers located at different sites: primary site and DR site. We're planning to failover on our DR Veeam Backup Server. On that server we have multiple replication jobs of VMs located on primary site.
Now, what we need besides the failback to production once the test is over (one week duration) is that when the failover is executed, VMs with status "Failover" have a "Inverse Replica" on primary site. At this moment this scenario is not being performed as this is for DR Tests only.
Is this possible? The link between both sites is 1Gb and it might be an important limitation to perform it.
Thanks in advance.
-
- Expert
- Posts: 206
- Liked: 41 times
- Joined: Nov 01, 2017 8:52 pm
- Full Name: blake dufour
- Contact:
Re: Bi directional Replication
hi,
why not have one backup server hosted at your DR site? that would be much easier as everything is managed from a single console. im not sure about the inverse replica thing. but once you fail over your VMs, you can fail back to your primary site and all data while failed over will be written back to your primary site as part of the fail back.
why not have one backup server hosted at your DR site? that would be much easier as everything is managed from a single console. im not sure about the inverse replica thing. but once you fail over your VMs, you can fail back to your primary site and all data while failed over will be written back to your primary site as part of the fail back.
-
- Enthusiast
- Posts: 26
- Liked: never
- Joined: Feb 01, 2018 4:14 pm
- Full Name: juan cruz
- Contact:
Re: Bi directional Replication
hi blake.
I do have a backup server at DR site. In fact this server is running all replication jobs and it will run the failover plan. The inverse replica is for the case that we experiment any issue on the DR site while we're running the failover plan. What would you do in that case?
I do have a backup server at DR site. In fact this server is running all replication jobs and it will run the failover plan. The inverse replica is for the case that we experiment any issue on the DR site while we're running the failover plan. What would you do in that case?
-
- Expert
- Posts: 206
- Liked: 41 times
- Joined: Nov 01, 2017 8:52 pm
- Full Name: blake dufour
- Contact:
Re: Bi directional Replication
Hi Juan,
just saying, you could also run of any job that your production side is doing from the DR site as well - as you said you have 2 backup servers. it would only send calls back to production. but that's entirely up to you. as far as your question is concerned - take one TEST VM for now, replicate to DR site, failover over to replica permanently imo (one week is a long time to run on a snapshot), replicate from DR site to production site using vms on prod site as targets, failover from DR site to production site. then once on production - replicate back to DR site. once you understand this clearly - you can expand your test accordingly.
just saying, you could also run of any job that your production side is doing from the DR site as well - as you said you have 2 backup servers. it would only send calls back to production. but that's entirely up to you. as far as your question is concerned - take one TEST VM for now, replicate to DR site, failover over to replica permanently imo (one week is a long time to run on a snapshot), replicate from DR site to production site using vms on prod site as targets, failover from DR site to production site. then once on production - replicate back to DR site. once you understand this clearly - you can expand your test accordingly.
-
- Enthusiast
- Posts: 26
- Liked: never
- Joined: Feb 01, 2018 4:14 pm
- Full Name: juan cruz
- Contact:
Re: Bi directional Replication
Thanks Blake. Its a good point of view. I'll try it out and then tell you.
-
- Enthusiast
- Posts: 82
- Liked: 11 times
- Joined: Nov 11, 2016 8:56 am
- Full Name: Oliver
- Contact:
Re: Bi directional Replication
2 Veeam Backup & Replication Servers?itops wrote:We have two backup servers located at different sites: primary site and DR site.
But each one is a seperate Veeam Backup-Server Installation with its own license file right?
Or can you actually have a High-Availability Veeam-Backupserver which synchronizes the Database/Jobs between both Systems so that the Backup Server in the DR-Site kicks in if the production is down?
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Bi directional Replication
No, you do not need separate licences for different Veeam B&R servers.oliverL wrote:2 Veeam Backup & Replication Servers?
But each one is a seperate Veeam Backup-Server Installation with its own license file right?
No, there's no such built-in functionality.oliverL wrote:Or can you actually have a High-Availability Veeam-Backupserver which synchronizes the Database/Jobs between both Systems so that the Backup Server in the DR-Site kicks in if the production is down?
Who is online
Users browsing this forum: No registered users and 35 guests