Re: AD Log files on separate drive from Database
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Wed, 10 Jan 2007 15:00:01 -0500
"Chris Herbert" <nojunk@xxxxxxxxxx> wrote in message
news:O5217FPNHHA.320@xxxxxxxxxxxxxxxxxxxxxxx
Hi,they
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
did that, they said that it was an MS recommendation. I haven't been ableto
find anything to support or contradict that.
It is an MS best practice (just logical too) IF there is any
performance issue -- with many small domains the performance
not an issue and there is no reason to follow this guideline
slavishly.
If it helps performance (significantly for you) then do it -- otherwise
don't worry about it.
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
.
- Follow-Ups:
- References:
- AD Log files on separate drive from Database
- From: Chris Herbert
- AD Log files on separate drive from Database
- Prev by Date: Re: adprep /forestprep fails
- Next by Date: AD Log files on separate drive from Database
- Previous by thread: AD Log files on separate drive from Database
- Next by thread: Re: AD Log files on separate drive from Database
- Index(es):
Relevant Pages
|