AD Log files on separate drive from Database

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi,
I have a Win2003 DC which is set up with the AD log files on a separate
drive to the database files. When I asked the person who set it up why they
did that, they said that it was an MS recommendation. I haven't been able to
find anything to support or contradict that.
Can someone tell me why this setup would be desirable? It is causing an
issue when creating LiveState recovery points for restoring to VMs.
Thanks


.

Relevant Pages

  • Re: Outlook is trying to retrieve data
    ... > come across for Exchange ... > files should be separate from the OS, ... If your log files start growing out of control ... > then while the databases will dismount, ...
    (microsoft.public.exchange.admin)
  • Re: New install partitioning question
    ... You should separate out your log files to a separate array if ... data/application I/O's, and then also writing to log files, you're wasting ... Depending on how your RAID10 is built, you might consider swiping two disks ... to build a RAID1 array for logging. ...
    (microsoft.public.windows.server.setup)
  • Re: Change Log File Location
    ... separate drive for recovery purposes. ... >If all you want to do is move the transaction log files ... >> underneath that one for the System Path Location. ...
    (microsoft.public.exchange.setup)
  • Re: AD Log files on separate drive from Database
    ... I have a Win2003 DC which is set up with the AD log files on a separate ... drive to the database files. ... issue when creating LiveState recovery points for restoring to VMs. ...
    (microsoft.public.windows.server.active_directory)
  • separating log directories to different partitions
    ... >I didn't separate the database files and the log files of ... active directory when I was setting up the W2K server. ...
    (microsoft.public.win2000.active_directory)