Veeam for DR

We are planning on utilising veeam backup and replicayion for our DR site.  We currently have 'live' servers which use DFS for replicating the data over a WAN/VPN connection.
In the event of DR we simply close a DR client machine and utilise our providers LAN/WAN for the clients into the datacentre where the servers are.  Of course there is an element of manul restoration of some data but most is always there and up-to-date.
Live site = 172. - DR site = 192.

I see you can re-ip VM's from host to host (for different sites mainly?).  
So how would these replicated hosts with same server names (different IP's i guess) be accessible to the clients without clashes???
LVL 1
CHI-LTDAsked:
Who is Participating?
 
S00007359Cloud Engineering OfficerCommented:
You need to ensure that your DNS, and Routing is setup correctly. Network is extended across both sites and VLANS are presented on both sites.

ideally from a live env, shutdown one vm and power on that replicated vm in dr site and test connectivty.

no matter what, ensure that you don't replicate dc's, else there will be nightmare's with timiing etc.

have a phsical dc on both sites, and ensure dhcp for cleint desktops are split across two servers.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Should not be an issue, if IP addresses change, when clients resolve server names, providing WINS,DNS is correct.
0
 
CHI-LTDAuthor Commented:
dont you need vm standard edition for vdist-swithces...?
0
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

 
CHI-LTDAuthor Commented:
nudge...
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Distributed Switch are a feature of Enterprise Plus
0
 
CHI-LTDAuthor Commented:
So is vdistributed switch my only option for DR?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
no, I do not know why this came up!

just extend VLAN from Site A to Site B.....some do this, quite cheaply.
0
 
CHI-LTDAuthor Commented:
can you explain>?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you extend your current production LAN to a VLAN at your DR site, no need for IP Address Change.
0
 
CHI-LTDAuthor Commented:
the dr site is already setup as separate network 192. range over vpn.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
yes, it would be, but depending upon your network configuration, you could extend production LAN to DR site with VLAN, and have network devices on the same LAN at both sites.

BUT, depends on your network, and connection to DR site, you state VPN, which makes me a little suspicious....so you would have to REIP.

you tested DR?

all your VMs at that site with access for users?
0
 
CHI-LTDAuthor Commented:
Yes we have tested DR.  Currently physical not Virtual...
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
So IP addresses is not an issue for you at DR site.

So if virtual machines are at DR site and on your sorted.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.