what is the best practice of publishing website updates on IIS running on a webserver farm
Hello experts,
We are running a website on a virtual platform with .net and MS SQL (VMWare on SAN). where we are planning to to add multiple Web Servers running MS windows 2008 web edition. My question is what would be the best practice of publishing updates as it has to be done on all the servers at the same time. Thank you so much.
We are running a website on a virtual platform with .net and MS SQL (VMWare on SAN). where we are planning to to add multiple Web Servers running MS windows 2008 web edition. My question is what would be the best practice of publishing updates as it has to be done on all the servers at the same time. Thank you so much.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
These are good suggestions. Thank you. I figured it can be done via using a script. I just need to know what is the industry standard out there, if any, so I will keep looking into it. As you said every environment is different and we need to come up with our own plan. I will give you credit for you post but rather wait a few more days to see if there will be other suggestions. Thanks again.
Dahter
Dahter
Glad to be of service :)
I've run everything from single web servers which obviously need down time for updates (we would run a seperate web service on the same box with a different address to do the pre production testing and then put up a 'being updated' page for the update), all the way up to a load balancer with about 40 servers under it for International companies (which was the examples above).
Hopefully some other EExperts can give you other examples of what they do and you can pick the example that matches your needs the best.
I've run everything from single web servers which obviously need down time for updates (we would run a seperate web service on the same box with a different address to do the pre production testing and then put up a 'being updated' page for the update), all the way up to a load balancer with about 40 servers under it for International companies (which was the examples above).
Hopefully some other EExperts can give you other examples of what they do and you can pick the example that matches your needs the best.
ASKER