We are shutting down one of our publicly facing web apps from our internet farm, and I'm trying to come up with a list of everything that needs to be done to make that happen. It's only a brochure site, so there's no real data or security issues around the content on the site. We are not going to delete the app as it will be the ultimate DR site for what we are moving to. If I have to ever restart this site it will mean I'm having a VERY bad day.

So here are the things that I came up with:

1. Verify no scheduled jobs are running on either pre-prod or prod on any farm servers
2. Stop scheduled content deployment, clean up CD folders
3. Stop IIS app pool on all servers, turn off automatic start on it
4. After some time go ahead and remove any IIS logs for it
5. Stop SP Jobs??

We are going to still have 5 other externally facing web apps on that farm, and I'm not sure if I should stop all the SP job definitions for that web app.  Does it really save that much CPU?  Or are there any jobs in there that would make a difference that they weren't running if I ever did have to stand this site back up again.

For some reason this list just doesn't seem long enough :-)

Thanks.

Ted

Just turn the s

Sorry, do you only have a single server in the farm processing end user requests? If that's the case, just call:

$wa = Get-SPWebApplication http://webApp
$wa.UnprovisionGlobally()

The IIS site will be deleted, as will the App Pool for that Web App (given it isn't used by anything else).

If there is more than one SharePoint server processing the request and you don't need that SharePoint server online, then it would be fine to just turn it off.

Trevor,

I appreciate your willingness to help, and maybe I just wasn't clear, but I thought in my post I indicated that I don't want to delete it. 

This site, a pretty important one, is being move to a different platform.  During the next several months, or at least until they can do a solid DR test on it's new environment, we want to keep the SP site available in the event that something goes seriously wrong on that new environment.  Then we can just start up the IIS sites, (and whatever else we need to do), and we have a functioning site again.

The site in question is the brochure site.  I still have 5 other sites, including the 2 ecommerce sites, running on that 6 server farm.  I want to make sure that nothing I do interferes with those 5 sites.

I'm just trying to come up with a list of things that would need to be done to turn that one site off, reduce CPU load on that server as much as easily possible, but still keep that site available if needed.

Ted