Any solution for redundant system that is running in a redundant site.

[riderfaiz]

Hi everyone,

Hope you are all doing well. Someone brings up this topic and I like to see if you can help and share your experience. I am sorry if I should post this in "Virtualized System" company :)

We are a small shop of running a virtual system running at our corporate site. Now we are thinking to have another system and copy/replicate all the virtual servers to that redundant location. That location is also one of our networks...which has its own router and traffic is run by layer 3 (in fact it is by  our single mode fiber but somehow it is set up as layer 3 while it could also been set up as layer 2).

Anyway, I would like to ask... Our virtual servers run in different vlans with different IP schemes. If we duplicate the system in that redundant location, that means all the ip settings with the VMs be carried over still.

Let's say, how should the network setup to be for the redundant location so that when we need to turn on those servers, they would still be accessible as if they were at the corporate site? Any solutions for this? Or anyone can share the experience on what can be done.

Thank you very much for your help!

Takami Chiro

[Philip D'Ath]

First let me recommend Veeam.

https://www.veeam.com/

It can replicate your servers and can automate DR failover.  One of the things it can do is automatically change the IP addresses on your servers so they can operate in the DR site.

Failing that, then yes, you will need to stretch the VLANs from the production site to the DR site.  The easiest way to do this is to go to your favourite service provider and buy a QinQ layer 2 circuit to link the two sites.  Then the same subnets can exist at the same time at both places.

You will need to consider how anything else in your network will connect to the DR site as well.

[Ganesh Hariharan]

Hi everyone,
Hope you are all doing well. Someone brings up this topic and I like to see if you can help and share your experience. I am sorry if I should post this in "Virtualized System" company :)
We are a small shop of running a virtual system running at our corporate site. Now we are thinking to have another system and copy/replicate all the virtual servers to that redundant location. That location is also one of our networks...which has its own router and traffic is run by layer 3 (in fact it is by  our single mode fiber but somehow it is set up as layer 3 while it could also been set up as layer 2).Anyway, I would like to ask... Our virtual servers run in different vlans with different IP schemes. If we duplicate the system in that redundant location, that means all the ip settings with the VMs be carried over still.Let's say, how should the network setup to be for the redundant location so that when we need to turn on those servers, they would still be accessible as if they were at the corporate site? Any solutions for this? Or anyone can share the experience on what can be done.
Thank you very much for your help!
Takami Chiro

Hi Takami,

Agree with Philip, Either if you have stretched Data Centre which is having VLANS stretched across the DC, where you can do simple VMotion and preserve with same ip for VM and all settings.

or if you have layer 3 Data centre with different ip address then 1 way is to have Vmotion and do some scripting to change the IP setting and gateway etc.

and another way is like product Veeam ,Commvault give benefit to achieve all this stuff , if you don't want to involve in manual scripting or manipulation.

Hope it Helps..

-GI