Best practice with Directly transaction logs for 2003 DC's

[HBBC]

I'm just finialising plans for our migration to Active Directory (we've decided on virtual DCs only).

Smallish environment, one site, two DCs 350 users.

I can't decide whether or not it's worth seperating AD transaction logs onto another vDisk. If we did, it'd probably only be worth creating a disk a couple of gig or so.

I've created a RAID1 LUN on our EVA4000 in preparation, but with all data being on the same SAN/DIsk Group, I'm struggling to see if it's worth the "hassle".

Views?

Regards,

Paul

[cemetric]

First off, I know it's not best practice to use virtual Domain Controllers only, on the other hand, I haven't got any real-life experience with that setup, so I can't comment actually

As putting the logs on a seperate LUN or Hard disk for that matter, is also not in the best practice(http://technet2.microsoft.com/WindowsServer/en/library/5712b108-176a-4592-bcde-a61e733579301033.mspx?mfr=true)

But I know it can't harm either, it has some advantages, but you need to be sure to have enough space on the LUN or Disk, as these logs work in circular motion, they can grow quite rapidly I've noticed.

It can prevent IO overhead also, especially with busy DCs.

[esiebert7625]

I wouldn't bother with it. Also the below guides are good to read when virtualizing AD...

Considerations when hosting Active Directory domain controller in virtual hosting environments - http://support.microsoft.com/kb/888794

Virtualizing a Windows Active Directory Domain Infrastructure - http://download3.vmware.com/vmworld/2006/tac9710.pdf