VMware Cloud Community
GFFG
Contributor
Contributor
Jump to solution

What happens to Server Ip's when a migration occurs

Hi,

If our main site which has 192.168.93.x fails, how would site manager on another site with a 192.168.91.x know the other site has failed?

Does site manager server have some heart beats between the two sites?

Also even when it did fail over all the vm's come up in another subnet with all the servers configured with static ip's, how does vmware handle that situation?

Or how does site manager handle that?

Reply
0 Kudos
1 Solution

Accepted Solutions
Jay_Judkowitz
Enthusiast
Enthusiast
Jump to solution

> If our main site which has 192.168.93.x fails, how would site manager on another site with a 192.168.91.x know the other site has failed? Does site manager server have some heart beats between the two sites?

SRM has a heartbeat that pings between the sites and triggers an event if connectivity is lost. If you make an alarm from that event, this can trigger an e-mail or an SNMP trap.

What SRM will not do is trigger the failover. Two reasons for this (a) we are don't want false positives in split-brain scenarios and (b) DR failover is a major business decision that warrants a manual initiation by someone with proper authority. The recovery itself is made up of hundreds of steps all of which are automated AFTER the person hits the run button.

> Also even when it did fail over all the vm's come up in another subnet with all the servers configured with static ip's, how does vmware handle that situation? Or how does site manager handle that?

SRM will change the recovery VMs' IP settings for you on first boot (IP, subnet, gateway, DNS servers). SRM exports a spreadsheet that outlines all the information you need to supply for the VM networking. After filling in the spreadsheet with the proper values for the VMs when they recover at the second site, you import the spreadsheet to SRM which creates customization specifications and associates them with the recovery VMs. When a failover occurs, the IP settings are changed on first boot. All of this saves minutes of manual work per VM - a huge savings if you're recovering hundreds of workloads.

View solution in original post

Reply
0 Kudos
2 Replies
Jay_Judkowitz
Enthusiast
Enthusiast
Jump to solution

> If our main site which has 192.168.93.x fails, how would site manager on another site with a 192.168.91.x know the other site has failed? Does site manager server have some heart beats between the two sites?

SRM has a heartbeat that pings between the sites and triggers an event if connectivity is lost. If you make an alarm from that event, this can trigger an e-mail or an SNMP trap.

What SRM will not do is trigger the failover. Two reasons for this (a) we are don't want false positives in split-brain scenarios and (b) DR failover is a major business decision that warrants a manual initiation by someone with proper authority. The recovery itself is made up of hundreds of steps all of which are automated AFTER the person hits the run button.

> Also even when it did fail over all the vm's come up in another subnet with all the servers configured with static ip's, how does vmware handle that situation? Or how does site manager handle that?

SRM will change the recovery VMs' IP settings for you on first boot (IP, subnet, gateway, DNS servers). SRM exports a spreadsheet that outlines all the information you need to supply for the VM networking. After filling in the spreadsheet with the proper values for the VMs when they recover at the second site, you import the spreadsheet to SRM which creates customization specifications and associates them with the recovery VMs. When a failover occurs, the IP settings are changed on first boot. All of this saves minutes of manual work per VM - a huge savings if you're recovering hundreds of workloads.

Reply
0 Kudos
GFFG
Contributor
Contributor
Jump to solution

Perfect! Thanks!

Reply
0 Kudos