Where is this blog post? Cheers Ken
> -----Original Message----- > From: John Hornbuckle [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 23 July 2008 11:54 PM > To: NT System Admin Issues > Subject: RE: Two Drives vs. One on a Server > > Unfortunately, no. > > He was actually writing about virtual IDE drives vs. virtual SCSI drives > in Hyper-V, and just mentioned in passing that it was a best practice to > have two drives. > > > > > > -----Original Message----- > From: Miller Bonnie L. [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 23, 2008 9:41 AM > To: NT System Admin Issues > Subject: RE: Two Drives vs. One on a Server > > I would think your I/O could be a lot better with two physically > separate drives or drive sets (not sure from your post if that is the > case)--that is probably one of the biggest bottlenecks on newer > hardware. Does the blogger say at all why they recommend the two sets? > > -Bonnie > > -----Original Message----- > From: John Hornbuckle [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 23, 2008 6:21 AM > To: NT System Admin Issues > Subject: RE: Two Drives vs. One on a Server > > Good point. Although with virtualization, the drive can be expanded at > any time, so that wouldn't so much of a factor now... > > > > -----Original Message----- > From: Kennedy, Jim [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 23, 2008 9:04 AM > To: NT System Admin Issues > Subject: RE: Two Drives vs. One on a Server > > I never really did it for security reasons. I did it because if data is > on another drive it can't fill up the OS drive....or if I needed to > expand data storage I didn't have to rebuild the OS. > > > > > -----Original Message----- > > From: John Hornbuckle [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, July 23, 2008 9:01 AM > > To: NT System Admin Issues > > Subject: Two Drives vs. One on a Server > > > > So, I've been playing around with Hyper-V for a few days, I've created > > a > > couple of test servers, and I'm ready now to create a "real" one. > > > > One thing I'm not sure of is whether I should create one drive or two > > for the servers. A blog post from a member of Microsoft's Hyper-V team > > recommend two as a matter of best practice--one for the OS, and the > > other for data. We've always split up our physical servers this way, > > since the Windows NT days. My question is, is it still necessary? If > > so, > > why? > > > > Back in the day, security was a big reason. For instance, if you had a > > web server serving content on your D: drive and the server was hacked > > making the whole drive accessible, the OS couldn't be touched since it > > was on the C: drive. > > > > With the current versions of Windows Server and IIS, is this still a > > consideration? > > > > > > > > > > John Hornbuckle > > MIS Department > > Taylor County School District > > 318 North Clark Street > > Perry, FL 32347 > > > > www.taylor.k12.fl.us > > > > > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
