Replicating and failing over IIS web server VM

[joebranca]

I've searched but haven't found any specific tips about bringing up IIS server VM replicas where IIS suddenly is running on different networking. Are there any caveats or best practices with IIS in failover networking? (certs, etc) I know we'll eventually want to setup SureReplica to test, but being unfamiliar with IIS I've still been tasked to get information on how Veeam replication will work as a DR strategy for this particular IIS server (as opposed to standing up a hot standby DR server configured with separate hostname, etc in the DR location)

[MarkBoothmaa]

Where are you planning to replicate the server to?
Is it internal / external facing?
Single or multi-homed IP?

Most networking issues should be solved by using network remapping. I assume you'll be replicating other servers if IIS requires them such as AD etc?

[joebranca]

External users via Internet would connect, and it appears to be single IP NIC.
With network remapping / re-IP, yes it would point to replicated AD DCs, etc.

As far as serving out websites, the only thing I could think of is if either a MAC address change breaks something that looks at MAC, or if anything within IIS references itself by IP instead of FQDN. I just don't know if those are likely issues, or if there are other considerations I'm unaware of.

[MarkBoothmaa]

You should be okay as you're replicating the VM so nothing underlying should change.