Hi guys,
We are in the process of implementing SRM for our DR. We have our VM's being replicated to another location, and then SRM is changing the IP's on them.
We have a lot of web boxes that have two or three IP's assigned to them and both HTTP and HTTPs site bindings to these IP's for different web pages.
When we fail over, what is the best practice to change the site bindings? I have two ideas that we have come up with:
1. Add duplicate site binding for the secondary IP address into production. These in theory should just sit unused until SRM activates the VM and switches to the new IP addresses. I however can not find any articles backing this up.
2. Use scripts to change the Site Bindings to the new ip's. I got this working using appcmd to first delete the old site bindings and then add the new ones, however, when it adds the HTTPS binding it does not have a method that allows me to add the SSL cert.
Does anyone have experience with this or a best practice?
Much appreciated.