-
- Novice
- Posts: 7
- Liked: 7 times
- Joined: May 20, 2014 6:31 am
- Full Name: Martin Meyer
Replication, but what about the Veeam server?
I am still pretty new to virtualization and to Veeam, but here goes. Imagine this scenario.
Host #1 (ESXi 5.5):
6 guests of which 1 is the Veeam server.
Host #2 (ESXi 5.5):
I want this as my Replication Job target.
NAS:
My default Backup Job repository. I run a Backup Job on this every single night, and it works like a charm.
I setup my Host #1 to replicate all guests to Host #2 through a Veeam Replication Job. Then disaster strikes, and Host #1 dies. Will Host #2 automatically "stand in" for Host #1, so that I can access Host #2 just as I did it with Host #1 before the disaster? Will all guests be exactly the same, and up to date, but only running from a different host?
Is this how a Replication Job works in Veeam?
Host #1 (ESXi 5.5):
6 guests of which 1 is the Veeam server.
Host #2 (ESXi 5.5):
I want this as my Replication Job target.
NAS:
My default Backup Job repository. I run a Backup Job on this every single night, and it works like a charm.
I setup my Host #1 to replicate all guests to Host #2 through a Veeam Replication Job. Then disaster strikes, and Host #1 dies. Will Host #2 automatically "stand in" for Host #1, so that I can access Host #2 just as I did it with Host #1 before the disaster? Will all guests be exactly the same, and up to date, but only running from a different host?
Is this how a Replication Job works in Veeam?
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Replication, but what about the Veeam server?
Hello Martin,
Thank you.
Not automatically, you will have to start your VMs either using Veeam console or manually. In a case of disaster failover will work and your target host (Host #2) will work as a source. Then you have a choice either to with keep using the target host (Host #2) as a primary one, called permanent failover or to failback.MartinM wrote:Will Host #2 automatically "stand in" for Host #1, so that I can access Host #2 just as I did it with Host #1 before the disaster? Will all guests be exactly the same, and up to date, but only running from a different host?
Thank you.
-
- Veeam Software
- Posts: 21144
- Liked: 2143 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Replication, but what about the Veeam server?
In case of DR, you will be able to failover to the latest replica restore point available, so changes occurred inside the original VM since this restore point was created and until the actual DR will be lost (RPO).MartinM wrote:Will all guests be exactly the same, and up to date, but only running from a different host?
-
- Novice
- Posts: 7
- Liked: 7 times
- Joined: May 20, 2014 6:31 am
- Full Name: Martin Meyer
Re: Replication, but what about the Veeam server?
Thank you for your replies. I would never want to do a permanent failover in my environment, because my Host #2 is way less powerful then Host #1.
But … What about doing the Failback. For doing that, I will need to be inside my Veeam server, with Veeam opened up and pressing the buttons - but then, all guests will be "failed back" to the Host #1. Wouldn't I lose the connection to my Veeam server session, as it does its Failback? Or is it (dream scenario) a matter of maybe one or two pings missed, and that I would probably never know anything happened, if I didn't know about it?
But … What about doing the Failback. For doing that, I will need to be inside my Veeam server, with Veeam opened up and pressing the buttons - but then, all guests will be "failed back" to the Host #1. Wouldn't I lose the connection to my Veeam server session, as it does its Failback? Or is it (dream scenario) a matter of maybe one or two pings missed, and that I would probably never know anything happened, if I didn't know about it?
-
- VP, Product Management
- Posts: 27451
- Liked: 2822 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Replication, but what about the Veeam server?
In your case the full procedure for failover should look like this:MartinM wrote:Wouldn't I lose the connection to my Veeam server session, as it does its Failback? Or is it (dream scenario) a matter of maybe one or two pings missed, and that I would probably never know anything happened, if I didn't know about it?
1. start the replicated Veeam backup server manually
2. do other VMs failover using your DR Veeam backup server console (in this case you will be able to automatically run a failback procedure)
3. once source site is up and running, initiate a failback operation for all VMs except backup server
4. replicate latest changes occurred on the DR backup server to the HQ host (via replication jobs and replica mapping functionality)
5. start Veeam backup server on the main site via vSphere Client
P.S. you could avoid steps 1,4,5 if your backup server managing replication jobs was located on the DR site (recommended approach).
-
- Novice
- Posts: 7
- Liked: 7 times
- Joined: May 20, 2014 6:31 am
- Full Name: Martin Meyer
Re: Replication, but what about the Veeam server?
Thank you. I will read up on your recommended approach regarding the location of the Veeam server.
-
- VP, Product Management
- Posts: 27451
- Liked: 2822 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Replication, but what about the Veeam server?
Please note that you can keep your existing backup server for doing backup jobs and install the new server to manage replication jobs. The consolidated view of entire infrastructure will be achieved via installing Veeam Backup Enterprise Manager. Thanks!
-
- Novice
- Posts: 7
- Liked: never
- Joined: Jul 17, 2014 2:16 pm
- Full Name: James MacCallum
- Contact:
[MERGED] Veeam Replication / Failover
Hi. I have recently implemented Veeam replication to replicate virtual servers to a second geographic location. This is working wonderfully.
I currently have the Veeam Backup & Replicaton Console installed on a server in my "source" (main) site and I use this to manage my replication jobs. My question is, if something major happens at my source site which means the server with the Veeam management console in not operational, how do I manage / failover Veeam replicas to my second site?
Am I able to install the Veeam management console at my second site and have it manage the configuration from my main site?
James
I currently have the Veeam Backup & Replicaton Console installed on a server in my "source" (main) site and I use this to manage my replication jobs. My question is, if something major happens at my source site which means the server with the Veeam management console in not operational, how do I manage / failover Veeam replicas to my second site?
Am I able to install the Veeam management console at my second site and have it manage the configuration from my main site?
James
-
- VP, Product Management
- Posts: 27451
- Liked: 2822 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Replication, but what about the Veeam server?
You will be able to start your VM replicas manually via vSphere Client. If you want to manage all replication jobs from the Veeam backup console, then installing it in the DR site is indeed the recommended approach.
-
- Novice
- Posts: 7
- Liked: never
- Joined: Jul 17, 2014 2:16 pm
- Full Name: James MacCallum
- Contact:
Re: Replication, but what about the Veeam server?
Hi. Thanks for the update (Its actually a hyper-v environment but the same principal applies).
So when I install Veeam at my DR site, what do I need to do to allow it to manage my existing jobs / servers / Veeam environment?
So when I install Veeam at my DR site, what do I need to do to allow it to manage my existing jobs / servers / Veeam environment?
-
- Product Manager
- Posts: 20450
- Liked: 2318 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Replication, but what about the Veeam server?
You should recreate existing jobs on DR VB&R server. Otherwise, you can backup and restore VB&R server configuration. Thanks.
-
- VP, Product Management
- Posts: 27451
- Liked: 2822 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Replication, but what about the Veeam server?
Also if you're running backup jobs against these VMs, then make sure replication and backup jobs do not overlap with each other.
-
- Novice
- Posts: 7
- Liked: never
- Joined: Jul 17, 2014 2:16 pm
- Full Name: James MacCallum
- Contact:
Re: Replication, but what about the Veeam server?
Hi. I have a follow up question about the above (apologies for the large gap in posting).
I have now installed Veeam at my DR site. You mention above that I need to export the configuration from my Live site and restore it at the DR site. Can I double check this is correct? Does this mean that if job configuration changes at the Live site, I have to do another export and restore?
I though that once I had configured Veeam at my DR site and had added my DR servers and Live host servers to the infrastructure, I would be able to see my replicated VMs via Veeam at my DR site?
I have now installed Veeam at my DR site. You mention above that I need to export the configuration from my Live site and restore it at the DR site. Can I double check this is correct? Does this mean that if job configuration changes at the Live site, I have to do another export and restore?
I though that once I had configured Veeam at my DR site and had added my DR servers and Live host servers to the infrastructure, I would be able to see my replicated VMs via Veeam at my DR site?
-
- Veeam Software
- Posts: 21144
- Liked: 2143 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Replication, but what about the Veeam server?
You'd better maintain two separate instances, one responsible for backup jobs (local) and another responsible for replication jobs (remote). So after deploying the remote instance, just disable backup jobs there and replication jobs on the local one.
-
- Enthusiast
- Posts: 41
- Liked: 1 time
- Joined: Mar 02, 2015 11:53 am
- Full Name: Andrej
- Contact:
Re: Replication, but what about the Veeam server?
Hi,
We are planning to add Veeam B&R server on remote DR site for only for replication jobs. How about licensing in this case? Will we need to split them beetween the B&R servers.
Also how failover will be performed in case if our vCenter is on primary site and will be not avalable during disaster? Can we for example replicate vCenter VM as well and perform failover from B&R server on DR site.
Thank you.
We are planning to add Veeam B&R server on remote DR site for only for replication jobs. How about licensing in this case? Will we need to split them beetween the B&R servers.
Also how failover will be performed in case if our vCenter is on primary site and will be not avalable during disaster? Can we for example replicate vCenter VM as well and perform failover from B&R server on DR site.
Thank you.
-
- Veeam Software
- Posts: 21144
- Liked: 2143 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Replication, but what about the Veeam server?
As long as the number of sockets on the hosts you're backing up/replicating VMs from does not exceed the number specified in the license, you're ok. You can use use Enterprise Manager that will push the license to both backup servers.andriktr wrote:We are planning to add Veeam B&R server on remote DR site for only for replication jobs. How about licensing in this case? Will we need to split them beetween the B&R servers.
Replicating vCenter Server is one of the options.andriktr wrote:Also how failover will be performed in case if our vCenter is on primary site and will be not avalable during disaster? Can we for example replicate vCenter VM as well and perform failover from B&R server on DR site.
Who is online
Users browsing this forum: Bing [Bot] and 22 guests