Veeam Replication DR site

Availability for the Always-On Enterprise

Veeam Replication DR site

Veeam Logoby mdaniels » Wed Feb 15, 2017 10:10 pm

Hi,

I'm setting up our disaster recovery documentation and updating configuration where needed.

We currently have a production site and disaster recovery site which contains critical servers. We currently only have one physical backup server on premise which replicates critical servers to our DR site.
However after searching through best practices in order to perform fallover and failback successfully we need to have another backup and replication console in our DR environment.

Is it as simple as setting up a new backup server in our DR environment? Will it be smart enough to see the replication jobs that had been configured in our on premise backup console and give us the ability to fallover in a disaster? Or do we have to re-configure replication jobs on our new console?

Will it cost in regards to licensing?

Any help would be appreciated.

Cheers
mdaniels
Lurker
 
Posts: 2
Liked: never
Joined: Wed Feb 15, 2017 5:27 am
Full Name: Matthew Daniels

Re: Veeam Replication DR site

Veeam Logoby jmmarton » Thu Feb 16, 2017 3:30 am 1 person likes this post

You would need to setup new replication jobs since this would be a separate, standalone instance of VBR running in your DR site. However one thing you could do to ease the transition is to use the existing replicas already in the DR site as a seed for the new replication jobs you configure. This way you wouldn't have to send the entire VMs over again.

As to cost, there's no additional cost. You can deploy as many Veeam servers as you'd like.

Joe
jmmarton
Veeam Software
 
Posts: 817
Liked: 89 times
Joined: Tue Nov 17, 2015 2:38 am
Location: Chicago, IL
Full Name: Joe Marton

Re: Veeam Replication DR site

Veeam Logoby blithespirit » Thu Feb 16, 2017 8:39 am 1 person likes this post

what best practice advises is that your VBR server be located in the DR site, not a second copy. this enables you to start recovery immiedietly in the event of a site failure, so you only need one running. Why not just move the full VBR server over to the DR site full stop. If possible just complete a replica and failover (after taking a copy of your config file with a backup). You can always leave a replica in your primary site in the event you lose your DR site.
blithespirit
Veeam Software
 
Posts: 44
Liked: 7 times
Joined: Tue May 03, 2016 2:06 pm
Full Name: Paul Szelsi

Re: Veeam Replication DR site

Veeam Logoby jmmarton » Thu Feb 16, 2017 3:50 pm 1 person likes this post

One of our recommendation is to use a backup server at the primary site for backup jobs and another at the DR site for replication jobs.

https://www.veeam.com/blog/physical-virtual-backup-server-placement-configuration.html

Joe
jmmarton
Veeam Software
 
Posts: 817
Liked: 89 times
Joined: Tue Nov 17, 2015 2:38 am
Location: Chicago, IL
Full Name: Joe Marton

Re: Veeam Replication DR site

Veeam Logoby mdaniels » Thu Feb 16, 2017 9:27 pm

Thanks for the prompt replies! As Joe said, we will most likely go with the secondary option in our DR environment and just configure replication jobs.

Will sort out seeding the new replication jobs. We currently have a our primary backup server directly connected to our backup repository SAN with good links as well as tape infrastructure so moving our primary is not really an option.

Thanks for the info!

Matt
mdaniels
Lurker
 
Posts: 2
Liked: never
Joined: Wed Feb 15, 2017 5:27 am
Full Name: Matthew Daniels

Re: Veeam Replication DR site

Veeam Logoby jmmarton » Sat Feb 18, 2017 3:51 pm 1 person likes this post

If you've already replicated some of the VMs to the DR site, you can use mapping in the new replication jobs you create in the new VBR instance in DR to map to those existing VMs in the DR site.

Joe
jmmarton
Veeam Software
 
Posts: 817
Liked: 89 times
Joined: Tue Nov 17, 2015 2:38 am
Location: Chicago, IL
Full Name: Joe Marton


Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Bing [Bot], BrentBPPI, Majestic-12 [Bot] and 27 guests