chiprule
asked on
Distaster recovery IP management
Hi Guys,
I have 2 site in 2 towns. There are some vm on site A that will be replicated on site B and viceversa.
There are DC, file server, and a pair of ERP based on sqlexpress, and other vms.
I have not yet decided which hypervisor to install and I am open to advice.
My question is how to deal with IP management?
The best solution is to have same IP server subnet on site A and site B excluding VLAN streching that is DEVIL.
Thanks!
I have 2 site in 2 towns. There are some vm on site A that will be replicated on site B and viceversa.
There are DC, file server, and a pair of ERP based on sqlexpress, and other vms.
I have not yet decided which hypervisor to install and I am open to advice.
My question is how to deal with IP management?
The best solution is to have same IP server subnet on site A and site B excluding VLAN streching that is DEVIL.
Thanks!
I would not stretch VLANs. Use different subnets for each site.
Agree with kevinhsieh. Stretching VLAN is a bad idea.
ASKER
Hi Guys,
I was the first to say "excluding VLAN stretching that is DEVIL" ...
On, different subnets ... ok .... but how to deal with changing of IP of vm?
The main problem is when vm are starting on DR site, they are no longer reachable (since they still have the original IP)
I was the first to say "excluding VLAN stretching that is DEVIL" ...
On, different subnets ... ok .... but how to deal with changing of IP of vm?
The main problem is when vm are starting on DR site, they are no longer reachable (since they still have the original IP)
You can try something like https://totaluptime.com/
This is not an automatic failover
It is not available in all the countries. Not sure it is supported in your country.
This is not an automatic failover
It is not available in all the countries. Not sure it is supported in your country.
You need to change the IP addresses of the VMs to match the new site. You can use DHCP, or inject new IP addresses if supported by your recovery system, or do it manually.
I would keep a running DC at the other site if possible, as well as have offline backups of all systems. Remember, it was a disconnected office with a DC that saved Maersk when they got hit by Wannacry. (No idea what happened to their backups...did they not backup DCs?)
I would keep a running DC at the other site if possible, as well as have offline backups of all systems. Remember, it was a disconnected office with a DC that saved Maersk when they got hit by Wannacry. (No idea what happened to their backups...did they not backup DCs?)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Steve. the users are both internal and external.
DHCP lan reservation can be a good solution. In case site A goes down, dhcp server on site B can give the new ip address and DNS server update this. Only thing to remember is to connect client to servers via DNS name instead of ip address.
DHCP lan reservation can be a good solution. In case site A goes down, dhcp server on site B can give the new ip address and DNS server update this. Only thing to remember is to connect client to servers via DNS name instead of ip address.