Why is it good to have website content files on a separate drive other than system (OS) drive?
Posted
by Jeffrey
on Server Fault
See other posts from Server Fault
or by Jeffrey
Published on 2010-03-17T23:41:24Z
Indexed on
2010/03/17
23:41 UTC
Read the original article
Hit count: 262
I am wondering what benefits will give me to move all website content files from the default inetpub directory (C:) to something like D:\wwwroot. By default IIS creates separate application pool for each website and I am using the built-in user and group (IURS) as the authentication method. I’ve made sure each site directory has the appropriate permission settings so I am not sure what benefits I will gain. Some of the environment settings are as below:
- VMWare Windows 2008 R2 64
- IIS 7.5
- C:\inetpub\site1
- C:\inetpub\site2
Also as this article (moving the iis7 inetpub directory to a different drive) points out, not sure if it's worth the trouble to migrate files to a different drive:
PLEASE BE AWARE OF THE FOLLOWING: WINDOWS SERVICING EVENTS (I.E. HOTFIXES AND SERVICE PACKS) WOULD STILL REPLACE FILES IN THE ORIGINAL DIRECTORIES. THE LIKELIHOOD THAT FILES IN THE INETPUB DIRECTORIES HAVE TO BE REPLACED BY SERVICING IS LOW BUT FOR THIS REASON DELETING THE ORIGINAL DIRECTORIES IS NOT POSSIBLE.
© Server Fault or respective owner