ntfrs error - corrupt ntfrs jet database

We are taxing the limits of the dfs using it to replicate large volumes of
traffice across our 2003 domain for various purposes. Yesterday, for the
second time, we received event id 13555 letting us know that we had a corrupt
ntfrs jet database. Following the directions and deleting the database and
rebuilding our structure is painful because it is live data and it is put
into pre-existing folders.

We noticed that the size of the database was 2gb! Is this the cause of the
failure and if so, is there any kind of utility that would allow us to
monitor and possibly prevent this corruption? Would an occasonal defrag
help?

Any suggestions would be greatly appreciated.

Issues that are resolved in the pre-Service Pack 1 release of Ntfrs.exe
http://support.microsoft.com/?id=823230

HTH

"Raymond" <(E-Mail Removed)> wrote in message
news:1F3CFFB1-C694-4D22-BEAA-(E-Mail Removed)...
> We are taxing the limits of the dfs using it to replicate large volumes of
> traffice across our 2003 domain for various purposes. Yesterday, for the
> second time, we received event id 13555 letting us know that we had a
> corrupt
> ntfrs jet database. Following the directions and deleting the database
> and
> rebuilding our structure is painful because it is live data and it is put
> into pre-existing folders.
>
> We noticed that the size of the database was 2gb! Is this the cause of
> the
> failure and if so, is there any kind of utility that would allow us to
> monitor and possibly prevent this corruption? Would an occasonal defrag
> help?
>
> Any suggestions would be greatly appreciated.

We have SP1 installed - I assume this would be included?

"seth" wrote:

>
> Issues that are resolved in the pre-Service Pack 1 release of Ntfrs.exe
> http://support.microsoft.com/?id=823230
>
> HTH
>
> "Raymond" <(E-Mail Removed)> wrote in message
> news:1F3CFFB1-C694-4D22-BEAA-(E-Mail Removed)...
> > We are taxing the limits of the dfs using it to replicate large volumes of
> > traffice across our 2003 domain for various purposes. Yesterday, for the
> > second time, we received event id 13555 letting us know that we had a
> > corrupt
> > ntfrs jet database. Following the directions and deleting the database
> > and
> > rebuilding our structure is painful because it is live data and it is put
> > into pre-existing folders.
> >
> > We noticed that the size of the database was 2gb! Is this the cause of
> > the
> > failure and if so, is there any kind of utility that would allow us to
> > monitor and possibly prevent this corruption? Would an occasonal defrag
> > help?
> >
> > Any suggestions would be greatly appreciated.
>
>
>

yeah it would be
ok found something else to look into

Configuration and operational recommendations for the File Replication
service in Windows Server 2003 and Windows 2000 Server
http://support.microsoft.com/kb/840675/en-us


"Raymond" <(E-Mail Removed)> wrote in message
news:34469D9D-EF08-420B-A64F-(E-Mail Removed)...
> We have SP1 installed - I assume this would be included?
>
> "seth" wrote:
>
>>
>> Issues that are resolved in the pre-Service Pack 1 release of Ntfrs.exe
>> http://support.microsoft.com/?id=823230
>>
>> HTH
>>
>> "Raymond" <(E-Mail Removed)> wrote in message
>> news:1F3CFFB1-C694-4D22-BEAA-(E-Mail Removed)...
>> > We are taxing the limits of the dfs using it to replicate large volumes
>> > of
>> > traffice across our 2003 domain for various purposes. Yesterday, for
>> > the
>> > second time, we received event id 13555 letting us know that we had a
>> > corrupt
>> > ntfrs jet database. Following the directions and deleting the database
>> > and
>> > rebuilding our structure is painful because it is live data and it is
>> > put
>> > into pre-existing folders.
>> >
>> > We noticed that the size of the database was 2gb! Is this the cause of
>> > the
>> > failure and if so, is there any kind of utility that would allow us to
>> > monitor and possibly prevent this corruption? Would an occasonal
>> > defrag
>> > help?
>> >
>> > Any suggestions would be greatly appreciated.
>>
>>
>>

Thanks for the reference - I've seen that - I feel like I've read everything
that's out there on the topic this weekend! Unfortunately, I'm not sure
there is anything that we can do that we aren't already to guarantee that
this database remains "safe". We definitely need to rethink our dfs
configuration and get some of the data out of there. We are exceeding the
limits and need to take a step back and look forward to the new dfs engine
promised in R2.

Thanks so much for your help and for looking into this.

"seth" wrote:

> yeah it would be
> ok found something else to look into
>
> Configuration and operational recommendations for the File Replication
> service in Windows Server 2003 and Windows 2000 Server
> http://support.microsoft.com/kb/840675/en-us
>
>
> "Raymond" <(E-Mail Removed)> wrote in message
> news:34469D9D-EF08-420B-A64F-(E-Mail Removed)...
> > We have SP1 installed - I assume this would be included?
> >
> > "seth" wrote:
> >
> >>
> >> Issues that are resolved in the pre-Service Pack 1 release of Ntfrs.exe
> >> http://support.microsoft.com/?id=823230
> >>
> >> HTH
> >>
> >> "Raymond" <(E-Mail Removed)> wrote in message
> >> news:1F3CFFB1-C694-4D22-BEAA-(E-Mail Removed)...
> >> > We are taxing the limits of the dfs using it to replicate large volumes
> >> > of
> >> > traffice across our 2003 domain for various purposes. Yesterday, for
> >> > the
> >> > second time, we received event id 13555 letting us know that we had a
> >> > corrupt
> >> > ntfrs jet database. Following the directions and deleting the database
> >> > and
> >> > rebuilding our structure is painful because it is live data and it is
> >> > put
> >> > into pre-existing folders.
> >> >
> >> > We noticed that the size of the database was 2gb! Is this the cause of
> >> > the
> >> > failure and if so, is there any kind of utility that would allow us to
> >> > monitor and possibly prevent this corruption? Would an occasonal
> >> > defrag
> >> > help?
> >> >
> >> > Any suggestions would be greatly appreciated.
> >>
> >>
> >>
>
>
>