I'm with you Michael, Just add another mount point and be done with it. DB and logs, one each per mount point, on the same disk, drive, whatever. It makes it much easier to keep track of them. With having well over a hundred Dags in just about every configuration one could imagine in just one environment I can't say "keep it simple" enough. As for virtual mailbox servers, not sure I'd go down that road but you already have. In my opinion, virtual servers are not all they're cracked up to be, even in less demanding rolls such as DC's they're affecting the performance and reliability of the orgs for a host of reasons (hehe that's a pun son.).
M From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Wednesday, June 01, 2011 11:58 AM To: MS-Exchange Admin Issues Subject: RE: Am I in a corner? Members of a DAG require that databases protected by the DAG must be consistently deployed. So..they all must be on E: once you Add-MailboxDatabaseCopy (or perform the similar activity in the GUI). What method are you wanting to use to grow the partition? Regardless, the easiest thing would be to present a new mount point as G: (or something) and put the new DB there. In Exchange 2010 there is rarely reason to separate log and database volumes. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Robert Peterson [mailto:robert.peter...@prin.edu] Sent: Wednesday, June 01, 2011 1:49 PM To: MS-Exchange Admin Issues Subject: Am I in a corner? All, Current Setup: Exchange 2010 using DAG - all servers are Hyper-V guests, spread across 4 hosts. 4 - Mailbox servers Each server mounts 2 disks - SAN volumes, presented as iSCSI attached disks. E:\ all Database storage ( 6 -250GB databases) --- passive copies on other servers. F:\ all Log storage (6 databases) 4 - CAS/HT servers Concern: All Mailbox DBs were "partitioned" as mount points on the same "disk" or volume (E:\) being presented from the SAN. Issues: . I need to allow room for one of the databases to grow OR create a new DB and move some of the mailboxes. o I cannot grow a single DB partition without letting it convert to a "dynamic" disk which looks messy and I understand is not supported by Microsoft. Questions: 1. If I present a new "disk" for a new database, is there a good reason to keep the "log" on a separate disk(volume), thus having to present two new disks? The examples I see from Microsoft show the DB and log file on the same path. 2. I am thinking I need to eventually get all my DBs to their own "disk". 3. What am I not knowing, that I should be thinking about? Thanks, Robert --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
