Building new DC Server 2008, disk has write caching enabled.

[Guest MT]

I'm building a new DC for our network that will replace an older machine.

This machine will host FSMO,GC and DNS for the network. It's a Dell server in

a RAID-1 array with a PERC 6/i SCSI controller. I've already run dcpromo on

the machine and noticed the event logs warning about the write caching. This

dis kcontroller does have battery backup on it so I believe I'm ok to leave

this enabled? What does eveyone think in general about this? I want the the

event logs clean as a whistle before I continue moving roles or at least know

that I have a server in optimal condition. Should I disable write caching or

not? Thanks

[Guest MT]

RE: Building new DC Server 2008, disk has write caching enabled.

 

No input on this? Dang, I really need some advice.

 

"MT" wrote:

> I'm building a new DC for our network that will replace an older machine.

> This machine will host FSMO,GC and DNS for the network. It's a Dell server in

> a RAID-1 array with a PERC 6/i SCSI controller. I've already run dcpromo on

> the machine and noticed the event logs warning about the write caching. This

> dis kcontroller does have battery backup on it so I believe I'm ok to leave

> this enabled? What does eveyone think in general about this? I want the the

> event logs clean as a whistle before I continue moving roles or at least know

> that I have a server in optimal condition. Should I disable write caching or

> not? Thanks

[Guest realized]

RE: Building new DC Server 2008, disk has write caching enabled.

 

Try posting on http://www.experts-exchange.com. sign up for a free account (its more

then worth it and you might end up liking it so much you will pay for an

account like i do). Or you can try http://www.msfn.org.

 

sorry i dont have the answer for you..

 

"MT" wrote:

> No input on this? Dang, I really need some advice.

>

> "MT" wrote:

>

> > I'm building a new DC for our network that will replace an older machine.

> > This machine will host FSMO,GC and DNS for the network. It's a Dell server in

> > a RAID-1 array with a PERC 6/i SCSI controller. I've already run dcpromo on

> > the machine and noticed the event logs warning about the write caching. This

> > dis kcontroller does have battery backup on it so I believe I'm ok to leave

> > this enabled? What does eveyone think in general about this? I want the the

> > event logs clean as a whistle before I continue moving roles or at least know

> > that I have a server in optimal condition. Should I disable write caching or

> > not? Thanks

[Guest Dusko Savatovic]

Re: Building new DC Server 2008, disk has write caching enabled.

 

A general rule is that on any database server, write caching should be

disabled. And DC role (Active Directory) stores information in a database.

Otherwise you risk corruption of a database in case of power failure or some

other interruption. With write caching disabled the database transactions

are recorded correctly and consistently and your risk of database corruption

is greatly minimized.

 

The only exception to this rule is if you use a RAID contoller with a backup

battery. This is the battery on the board itself (not to be confused with

UPS). In that case, the contents of the write cache are preserved in case of

power failure and written to the disk as soon as power is restored.

 

HTH,

Dush

 

"MT" <MT@discussions.microsoft.com> wrote in message

news:23E02F23-E42D-4DD0-B6A5-EEA4E0285F43@microsoft.com...

> I'm building a new DC for our network that will replace an older machine.

> This machine will host FSMO,GC and DNS for the network. It's a Dell server

> in

> a RAID-1 array with a PERC 6/i SCSI controller. I've already run dcpromo

> on

> the machine and noticed the event logs warning about the write caching.

> This

> dis kcontroller does have battery backup on it so I believe I'm ok to

> leave

> this enabled? What does eveyone think in general about this? I want the

> the

> event logs clean as a whistle before I continue moving roles or at least

> know

> that I have a server in optimal condition. Should I disable write caching

> or

> not? Thanks