So, If the single host store that holds all of your virtual disks fails, which of the one, two or three that you split will survive and provide you recoverability?
Virtualization changes nothing within the underlying rational for separating volume concerns on "physically different arrays". From: [email protected] [mailto:[email protected]] On Behalf Of J- P Sent: Saturday, May 9, 2015 11:47 AM To: Exchange List Subject: RE: [Exchange] Log Files & DB on HyperV The host is a 6 disc raid10 , there are no other arrays available, would this be an issue? ________________________________ Date: Sat, 9 May 2015 17:20:44 +0000 From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: Re: [Exchange] Log Files & DB on HyperV For recovery purposes I would use a separate VHD for the OS and the Exchange database / logs, and then keep both of them on separate arrays. With that said you should be able to throw all the exchange files (database and logs) on the same volume as long as you are obtaining the IOPS required from the Exchange calc. Since IO has been reduced so much I don't think that should be an issue. Sent by Outlook<http://taps.io/outlookmobile> for Android On Sat, May 9, 2015 at 10:11 AM -0700, "J- P" <[email protected]<mailto:[email protected]>> wrote: Hi all, I'm cross-posting this because despite it being for Exchange, it does pertain Windows as well. Back in the physical days , it was always OS, LogFiles, and DB on separate disks/volumes/arrays etc.. Now with virtulization, is it still recommended /best practice to create separate VHD's for the OS/DB/Log files for performance gain? TIA
