There's no need to split tx logs and database except in some occasional high volume scenarios. What I do do is put sysvol on its' own LUN in distributed environments so some guy in the field can't DDOS the whole AD by filling the volume up.
Thanks, Brian Desmond [email protected] c - 312.731.3132 From: Ziots, Edward [mailto:[email protected]] Sent: Tuesday, August 10, 2010 7:55 AM To: NT System Admin Issues Subject: Question about Spliting Active directory files on seperate volumes Preface: Going from Windows 2003 R2 to Windows 2008 R2 domain ( X64), new Domain Controllers are going to be virtual ( ESX 4.x) all but one. I saw the following article from the Active Directory team about best practices and recommendations http://blogs.dirteam.com/blogs/sanderberkouwer/archive/2007/02/09/active-directory-on-separate-volumes.aspx I also saw the same recommendations in Miansi book, in splitting the sysvol/transaction Logs on separate Luns. Basically OS C:\ SYSVOL\NTDS.DIT ( D:\) Transaction Logs: E:\ Is anyone else doing this out there for a forest of less than 20K in users, and probably less than 100K in objects? Only issue I could see is usually we store additional virtual disks with the .VMX file which means they would be on the same SAN LUN, which would basically negate the benefit of splitting the IO and files on different disks in the virtual land. On the physical server I could go with 3 RAID 1 arrays and put each section on that accordingly. Thoughts, I am interested in hearin what others are doing, to increase the performance in there R2 AD environments. Z Edward E. Ziots CISSP, Network +, Security + Network Engineer Lifespan Organization Email:[email protected] Cell:401-639-3505 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
