FRS bails on huge folder/file structure -2k3 SP2

I have replication working on a few smaller links within a single root
target. These folders range from 200 megs to 2gb with a few thousand
files in each.

The problem i'm running into is when i add our main my document
redirection folder. This folder structure is massive with well over a
million folders/files (nested of course, its the My Documents redirect
for about 600 users) totaling about 800GB.

As soon as i enable replication i'll start seeing Event ID 13555 in FRS
event log "The File Replication Service is in an error state. Files will
not replicate to or from one or all of the replica sets on this computer
until the following recovery steps are performed: "

Then nothing replicates. If i remove the links/replication to the My
Documents shares and restart the FRS service all is back to being well
again.

Is there some jet DB limit on files/directories that i'm hitting? The
whole purpose of the DFS setup was to provide fault tolerance to users
if the server hosting their documents went down, but so far we're not
doing so well.

Would migrating to R2 or even Server 2008 rectify this problem? Am i
better off calling MS Support and opening a case?

Thanks!!

Anyone have any input on this? We're sill struggling to figure this out.
Should i just bite the bullet and open a support case with MS?

Thx!

UMH Tech wrote:
> I have replication working on a few smaller links within a single root
> target. These folders range from 200 megs to 2gb with a few thousand
> files in each.
>
> The problem i'm running into is when i add our main my document
> redirection folder. This folder structure is massive with well over a
> million folders/files (nested of course, its the My Documents redirect
> for about 600 users) totaling about 800GB.
>
> As soon as i enable replication i'll start seeing Event ID 13555 in FRS
> event log "The File Replication Service is in an error state. Files will
> not replicate to or from one or all of the replica sets on this computer
> until the following recovery steps are performed: "
>
> Then nothing replicates. If i remove the links/replication to the My
> Documents shares and restart the FRS service all is back to being well
> again.
>
> Is there some jet DB limit on files/directories that i'm hitting? The
> whole purpose of the DFS setup was to provide fault tolerance to users
> if the server hosting their documents went down, but so far we're not
> doing so well.
>
> Would migrating to R2 or even Server 2008 rectify this problem? Am i
> better off calling MS Support and opening a case?
>
> Thanks!!

UMH,
Here are the guidelines: http://support.microsoft.com/kb/840675
The things I would check out first are:
- staging area size
- USN journal size
FRS is quite difficult to troubleshoot. You can get a block where you have
created a failed replica adn are unable to create a new one. Sonar and
Ultrasound are two tools that can give you a better idea of what is going
on.
If you can, I would adopt R2 DFSR anyway,
Anthony, http://www.airdesk.co.uk


"UMH Tech" <> wrote in message
news:...
> Anyone have any input on this? We're sill struggling to figure this out.
> Should i just bite the bullet and open a support case with MS?
>
> Thx!
>
> UMH Tech wrote:
>> I have replication working on a few smaller links within a single root
>> target. These folders range from 200 megs to 2gb with a few thousand
>> files in each.
>>
>> The problem i'm running into is when i add our main my document
>> redirection folder. This folder structure is massive with well over a
>> million folders/files (nested of course, its the My Documents redirect
>> for about 600 users) totaling about 800GB.
>>
>> As soon as i enable replication i'll start seeing Event ID 13555 in FRS
>> event log "The File Replication Service is in an error state. Files will
>> not replicate to or from one or all of the replica sets on this computer
>> until the following recovery steps are performed: "
>>
>> Then nothing replicates. If i remove the links/replication to the My
>> Documents shares and restart the FRS service all is back to being well
>> again.
>>
>> Is there some jet DB limit on files/directories that i'm hitting? The
>> whole purpose of the DFS setup was to provide fault tolerance to users if
>> the server hosting their documents went down, but so far we're not doing
>> so well.
>>
>> Would migrating to R2 or even Server 2008 rectify this problem? Am i
>> better off calling MS Support and opening a case?
>>
>> Thanks!!

Hi Anthony,

Great information, thank you. I think the problem is the USN journal
size.

I'd love to go to R2 or 2008 but the existing server that holds all the
data currently is a DC and a few other small things. AFAIK there's no
upgrade path to R2 that i can do other then wiping it clean and
reinstalling fresh.



Anthony [MVP] wrote:
> UMH,
> Here are the guidelines: http://support.microsoft.com/kb/840675
> The things I would check out first are:
> - staging area size
> - USN journal size
> FRS is quite difficult to troubleshoot. You can get a block where you
> have created a failed replica adn are unable to create a new one. Sonar
> and Ultrasound are two tools that can give you a better idea of what is
> going on.
> If you can, I would adopt R2 DFSR anyway,
> Anthony, http://www.airdesk.co.uk
>
>
> "UMH Tech" <> wrote in message
> news:...
>> Anyone have any input on this? We're sill struggling to figure this
>> out. Should i just bite the bullet and open a support case with MS?
>>
>> Thx!
>>
>> UMH Tech wrote:
>>> I have replication working on a few smaller links within a single
>>> root target. These folders range from 200 megs to 2gb with a few
>>> thousand files in each.
>>>
>>> The problem i'm running into is when i add our main my document
>>> redirection folder. This folder structure is massive with well over
>>> a million folders/files (nested of course, its the My Documents
>>> redirect for about 600 users) totaling about 800GB.
>>>
>>> As soon as i enable replication i'll start seeing Event ID 13555 in
>>> FRS event log "The File Replication Service is in an error state.
>>> Files will not replicate to or from one or all of the replica sets on
>>> this computer until the following recovery steps are performed: "
>>>
>>> Then nothing replicates. If i remove the links/replication to the My
>>> Documents shares and restart the FRS service all is back to being
>>> well again.
>>>
>>> Is there some jet DB limit on files/directories that i'm hitting?
>>> The whole purpose of the DFS setup was to provide fault tolerance to
>>> users if the server hosting their documents went down, but so far
>>> we're not doing so well.
>>>
>>> Would migrating to R2 or even Server 2008 rectify this problem? Am i
>>> better off calling MS Support and opening a case?
>>>
>>> Thanks!!
>

Hi UMH,
Glad it helped.
R2 is just a set of additional features (e.g DFSR) that require a schema
change ( with a price tag to keep the cash flow going before Server 2008 was
released).
If you are licensed you can easily update to R2.
http://technet.microsoft.com/en-us/l.../cc772804.aspx. Obviously back up
everything first, including System State.
Anthony,
http://www.airdesk.co.uk


"UMH Tech" <> wrote in message
news:...
> Hi Anthony,
>
> Great information, thank you. I think the problem is the USN journal
> size.
>
> I'd love to go to R2 or 2008 but the existing server that holds all the
> data currently is a DC and a few other small things. AFAIK there's no
> upgrade path to R2 that i can do other then wiping it clean and
> reinstalling fresh.
>
>
>
> Anthony [MVP] wrote:
>> UMH,
>> Here are the guidelines: http://support.microsoft.com/kb/840675
>> The things I would check out first are:
>> - staging area size
>> - USN journal size
>> FRS is quite difficult to troubleshoot. You can get a block where you
>> have created a failed replica adn are unable to create a new one. Sonar
>> and Ultrasound are two tools that can give you a better idea of what is
>> going on.
>> If you can, I would adopt R2 DFSR anyway,
>> Anthony, http://www.airdesk.co.uk
>>
>>
>> "UMH Tech" <> wrote in message
>> news:...
>>> Anyone have any input on this? We're sill struggling to figure this out.
>>> Should i just bite the bullet and open a support case with MS?
>>>
>>> Thx!
>>>
>>> UMH Tech wrote:
>>>> I have replication working on a few smaller links within a single root
>>>> target. These folders range from 200 megs to 2gb with a few thousand
>>>> files in each.
>>>>
>>>> The problem i'm running into is when i add our main my document
>>>> redirection folder. This folder structure is massive with well over a
>>>> million folders/files (nested of course, its the My Documents redirect
>>>> for about 600 users) totaling about 800GB.
>>>>
>>>> As soon as i enable replication i'll start seeing Event ID 13555 in FRS
>>>> event log "The File Replication Service is in an error state. Files
>>>> will not replicate to or from one or all of the replica sets on this
>>>> computer until the following recovery steps are performed: "
>>>>
>>>> Then nothing replicates. If i remove the links/replication to the My
>>>> Documents shares and restart the FRS service all is back to being well
>>>> again.
>>>>
>>>> Is there some jet DB limit on files/directories that i'm hitting? The
>>>> whole purpose of the DFS setup was to provide fault tolerance to users
>>>> if the server hosting their documents went down, but so far we're not
>>>> doing so well.
>>>>
>>>> Would migrating to R2 or even Server 2008 rectify this problem? Am i
>>>> better off calling MS Support and opening a case?
>>>>
>>>> Thanks!!
>>

Does all of my DC's need to be running R2?

Anthony [MVP] wrote:
> Hi UMH,
> Glad it helped.
> R2 is just a set of additional features (e.g DFSR) that require a schema
> change ( with a price tag to keep the cash flow going before Server 2008
> was released).
> If you are licensed you can easily update to R2.
> http://technet.microsoft.com/en-us/l.../cc772804.aspx. Obviously back
> up everything first, including System State.
> Anthony,
> http://www.airdesk.co.uk
>
>
> "UMH Tech" <> wrote in message
> news:...
>> Hi Anthony,
>>
>> Great information, thank you. I think the problem is the USN journal
>> size.
>>
>> I'd love to go to R2 or 2008 but the existing server that holds all
>> the data currently is a DC and a few other small things. AFAIK
>> there's no upgrade path to R2 that i can do other then wiping it clean
>> and reinstalling fresh.
>>
>>
>>
>> Anthony [MVP] wrote:
>>> UMH,
>>> Here are the guidelines: http://support.microsoft.com/kb/840675
>>> The things I would check out first are:
>>> - staging area size
>>> - USN journal size
>>> FRS is quite difficult to troubleshoot. You can get a block where you
>>> have created a failed replica adn are unable to create a new one.
>>> Sonar and Ultrasound are two tools that can give you a better idea of
>>> what is going on.
>>> If you can, I would adopt R2 DFSR anyway,
>>> Anthony, http://www.airdesk.co.uk
>>>
>>>
>>> "UMH Tech" <> wrote in message
>>> news:...
>>>> Anyone have any input on this? We're sill struggling to figure this
>>>> out. Should i just bite the bullet and open a support case with MS?
>>>>
>>>> Thx!
>>>>
>>>> UMH Tech wrote:
>>>>> I have replication working on a few smaller links within a single
>>>>> root target. These folders range from 200 megs to 2gb with a few
>>>>> thousand files in each.
>>>>>
>>>>> The problem i'm running into is when i add our main my document
>>>>> redirection folder. This folder structure is massive with well
>>>>> over a million folders/files (nested of course, its the My
>>>>> Documents redirect for about 600 users) totaling about 800GB.
>>>>>
>>>>> As soon as i enable replication i'll start seeing Event ID 13555 in
>>>>> FRS event log "The File Replication Service is in an error state.
>>>>> Files will not replicate to or from one or all of the replica sets
>>>>> on this computer until the following recovery steps are performed: "
>>>>>
>>>>> Then nothing replicates. If i remove the links/replication to the
>>>>> My Documents shares and restart the FRS service all is back to
>>>>> being well again.
>>>>>
>>>>> Is there some jet DB limit on files/directories that i'm hitting?
>>>>> The whole purpose of the DFS setup was to provide fault tolerance
>>>>> to users if the server hosting their documents went down, but so
>>>>> far we're not doing so well.
>>>>>
>>>>> Would migrating to R2 or even Server 2008 rectify this problem? Am
>>>>> i better off calling MS Support and opening a case?
>>>>>
>>>>> Thanks!!
>>>

No, just the schema extended, which you need to do on the schema master.
None of the DC's need to "upgrade" to R2.; just the servers which are going
to use R2 features (although in your case that is also a DC), see:
http://technet.microsoft.com/en-us/l.../cc755834.aspx
Anthony
http://www.airdesk.co.uk

"UMH Tech" <> wrote in message
news:#...
> Does all of my DC's need to be running R2?
>
> Anthony [MVP] wrote:
>> Hi UMH,
>> Glad it helped.
>> R2 is just a set of additional features (e.g DFSR) that require a schema
>> change ( with a price tag to keep the cash flow going before Server 2008
>> was released).
>> If you are licensed you can easily update to R2.
>> http://technet.microsoft.com/en-us/l.../cc772804.aspx. Obviously back
>> up everything first, including System State.
>> Anthony,
>> http://www.airdesk.co.uk
>>
>>
>> "UMH Tech" <> wrote in message
>> news:...
>>> Hi Anthony,
>>>
>>> Great information, thank you. I think the problem is the USN journal
>>> size.
>>>
>>> I'd love to go to R2 or 2008 but the existing server that holds all the
>>> data currently is a DC and a few other small things. AFAIK there's no
>>> upgrade path to R2 that i can do other then wiping it clean and
>>> reinstalling fresh.
>>>
>>>
>>>
>>> Anthony [MVP] wrote:
>>>> UMH,
>>>> Here are the guidelines: http://support.microsoft.com/kb/840675
>>>> The things I would check out first are:
>>>> - staging area size
>>>> - USN journal size
>>>> FRS is quite difficult to troubleshoot. You can get a block where you
>>>> have created a failed replica adn are unable to create a new one. Sonar
>>>> and Ultrasound are two tools that can give you a better idea of what is
>>>> going on.
>>>> If you can, I would adopt R2 DFSR anyway,
>>>> Anthony, http://www.airdesk.co.uk
>>>>
>>>>
>>>> "UMH Tech" <> wrote in message
>>>> news:...
>>>>> Anyone have any input on this? We're sill struggling to figure this
>>>>> out. Should i just bite the bullet and open a support case with MS?
>>>>>
>>>>> Thx!
>>>>>
>>>>> UMH Tech wrote:
>>>>>> I have replication working on a few smaller links within a single
>>>>>> root target. These folders range from 200 megs to 2gb with a few
>>>>>> thousand files in each.
>>>>>>
>>>>>> The problem i'm running into is when i add our main my document
>>>>>> redirection folder. This folder structure is massive with well over
>>>>>> a million folders/files (nested of course, its the My Documents
>>>>>> redirect for about 600 users) totaling about 800GB.
>>>>>>
>>>>>> As soon as i enable replication i'll start seeing Event ID 13555 in
>>>>>> FRS event log "The File Replication Service is in an error state.
>>>>>> Files will not replicate to or from one or all of the replica sets on
>>>>>> this computer until the following recovery steps are performed: "
>>>>>>
>>>>>> Then nothing replicates. If i remove the links/replication to the My
>>>>>> Documents shares and restart the FRS service all is back to being
>>>>>> well again.
>>>>>>
>>>>>> Is there some jet DB limit on files/directories that i'm hitting?
>>>>>> The whole purpose of the DFS setup was to provide fault tolerance to
>>>>>> users if the server hosting their documents went down, but so far
>>>>>> we're not doing so well.
>>>>>>
>>>>>> Would migrating to R2 or even Server 2008 rectify this problem? Am i
>>>>>> better off calling MS Support and opening a case?
>>>>>>
>>>>>> Thanks!!
>>>>

Thanks Anthony, If you're ever in Philadelphia I owe you a beer.

Anthony [MVP] wrote:
> No, just the schema extended, which you need to do on the schema master.
> None of the DC's need to "upgrade" to R2.; just the servers which are
> going to use R2 features (although in your case that is also a DC), see:
> http://technet.microsoft.com/en-us/l.../cc755834.aspx
> Anthony
> http://www.airdesk.co.uk
>
> "UMH Tech" <> wrote in message
> news:#...
>> Does all of my DC's need to be running R2?
>>
>> Anthony [MVP] wrote:
>>> Hi UMH,
>>> Glad it helped.
>>> R2 is just a set of additional features (e.g DFSR) that require a
>>> schema change ( with a price tag to keep the cash flow going before
>>> Server 2008 was released).
>>> If you are licensed you can easily update to R2.
>>> http://technet.microsoft.com/en-us/l.../cc772804.aspx. Obviously
>>> back up everything first, including System State.
>>> Anthony,
>>> http://www.airdesk.co.uk
>>>
>>>
>>> "UMH Tech" <> wrote in message
>>> news:...
>>>> Hi Anthony,
>>>>
>>>> Great information, thank you. I think the problem is the USN
>>>> journal size.
>>>>
>>>> I'd love to go to R2 or 2008 but the existing server that holds all
>>>> the data currently is a DC and a few other small things. AFAIK
>>>> there's no upgrade path to R2 that i can do other then wiping it
>>>> clean and reinstalling fresh.
>>>>
>>>>
>>>>
>>>> Anthony [MVP] wrote:
>>>>> UMH,
>>>>> Here are the guidelines: http://support.microsoft.com/kb/840675
>>>>> The things I would check out first are:
>>>>> - staging area size
>>>>> - USN journal size
>>>>> FRS is quite difficult to troubleshoot. You can get a block where
>>>>> you have created a failed replica adn are unable to create a new
>>>>> one. Sonar and Ultrasound are two tools that can give you a better
>>>>> idea of what is going on.
>>>>> If you can, I would adopt R2 DFSR anyway,
>>>>> Anthony, http://www.airdesk.co.uk
>>>>>
>>>>>
>>>>> "UMH Tech" <> wrote in message
>>>>> news:...
>>>>>> Anyone have any input on this? We're sill struggling to figure
>>>>>> this out. Should i just bite the bullet and open a support case
>>>>>> with MS?
>>>>>>
>>>>>> Thx!
>>>>>>
>>>>>> UMH Tech wrote:
>>>>>>> I have replication working on a few smaller links within a single
>>>>>>> root target. These folders range from 200 megs to 2gb with a few
>>>>>>> thousand files in each.
>>>>>>>
>>>>>>> The problem i'm running into is when i add our main my document
>>>>>>> redirection folder. This folder structure is massive with well
>>>>>>> over a million folders/files (nested of course, its the My
>>>>>>> Documents redirect for about 600 users) totaling about 800GB.
>>>>>>>
>>>>>>> As soon as i enable replication i'll start seeing Event ID 13555
>>>>>>> in FRS event log "The File Replication Service is in an error
>>>>>>> state. Files will not replicate to or from one or all of the
>>>>>>> replica sets on this computer until the following recovery steps
>>>>>>> are performed: "
>>>>>>>
>>>>>>> Then nothing replicates. If i remove the links/replication to
>>>>>>> the My Documents shares and restart the FRS service all is back
>>>>>>> to being well again.
>>>>>>>
>>>>>>> Is there some jet DB limit on files/directories that i'm hitting?
>>>>>>> The whole purpose of the DFS setup was to provide fault tolerance
>>>>>>> to users if the server hosting their documents went down, but so
>>>>>>> far we're not doing so well.
>>>>>>>
>>>>>>> Would migrating to R2 or even Server 2008 rectify this problem?
>>>>>>> Am i better off calling MS Support and opening a case?
>>>>>>>
>>>>>>> Thanks!!
>>>>

Hey UMH, when I am next in Philadelphia I will take you up on that!
Good luck,
Anthony

"UMH Tech" <> wrote in message
news:e9by$...
> Thanks Anthony, If you're ever in Philadelphia I owe you a beer.
>
> Anthony [MVP] wrote:
>> No, just the schema extended, which you need to do on the schema master.
>> None of the DC's need to "upgrade" to R2.; just the servers which are
>> going to use R2 features (although in your case that is also a DC), see:
>> http://technet.microsoft.com/en-us/l.../cc755834.aspx
>> Anthony
>> http://www.airdesk.co.uk
>>
>> "UMH Tech" <> wrote in message
>> news:#...
>>> Does all of my DC's need to be running R2?
>>>
>>> Anthony [MVP] wrote:
>>>> Hi UMH,
>>>> Glad it helped.
>>>> R2 is just a set of additional features (e.g DFSR) that require a
>>>> schema change ( with a price tag to keep the cash flow going before
>>>> Server 2008 was released).
>>>> If you are licensed you can easily update to R2.
>>>> http://technet.microsoft.com/en-us/l.../cc772804.aspx. Obviously
>>>> back up everything first, including System State.
>>>> Anthony,
>>>> http://www.airdesk.co.uk
>>>>
>>>>
>>>> "UMH Tech" <> wrote in message
>>>> news:...
>>>>> Hi Anthony,
>>>>>
>>>>> Great information, thank you. I think the problem is the USN journal
>>>>> size.
>>>>>
>>>>> I'd love to go to R2 or 2008 but the existing server that holds all
>>>>> the data currently is a DC and a few other small things. AFAIK
>>>>> there's no upgrade path to R2 that i can do other then wiping it clean
>>>>> and reinstalling fresh.
>>>>>
>>>>>
>>>>>
>>>>> Anthony [MVP] wrote:
>>>>>> UMH,
>>>>>> Here are the guidelines: http://support.microsoft.com/kb/840675
>>>>>> The things I would check out first are:
>>>>>> - staging area size
>>>>>> - USN journal size
>>>>>> FRS is quite difficult to troubleshoot. You can get a block where you
>>>>>> have created a failed replica adn are unable to create a new one.
>>>>>> Sonar and Ultrasound are two tools that can give you a better idea of
>>>>>> what is going on.
>>>>>> If you can, I would adopt R2 DFSR anyway,
>>>>>> Anthony, http://www.airdesk.co.uk
>>>>>>
>>>>>>
>>>>>> "UMH Tech" <> wrote in message
>>>>>> news:...
>>>>>>> Anyone have any input on this? We're sill struggling to figure this
>>>>>>> out. Should i just bite the bullet and open a support case with MS?
>>>>>>>
>>>>>>> Thx!
>>>>>>>
>>>>>>> UMH Tech wrote:
>>>>>>>> I have replication working on a few smaller links within a single
>>>>>>>> root target. These folders range from 200 megs to 2gb with a few
>>>>>>>> thousand files in each.
>>>>>>>>
>>>>>>>> The problem i'm running into is when i add our main my document
>>>>>>>> redirection folder. This folder structure is massive with well
>>>>>>>> over a million folders/files (nested of course, its the My
>>>>>>>> Documents redirect for about 600 users) totaling about 800GB.
>>>>>>>>
>>>>>>>> As soon as i enable replication i'll start seeing Event ID 13555 in
>>>>>>>> FRS event log "The File Replication Service is in an error state.
>>>>>>>> Files will not replicate to or from one or all of the replica sets
>>>>>>>> on this computer until the following recovery steps are performed:
>>>>>>>> "
>>>>>>>>
>>>>>>>> Then nothing replicates. If i remove the links/replication to the
>>>>>>>> My Documents shares and restart the FRS service all is back to
>>>>>>>> being well again.
>>>>>>>>
>>>>>>>> Is there some jet DB limit on files/directories that i'm hitting?
>>>>>>>> The whole purpose of the DFS setup was to provide fault tolerance
>>>>>>>> to users if the server hosting their documents went down, but so
>>>>>>>> far we're not doing so well.
>>>>>>>>
>>>>>>>> Would migrating to R2 or even Server 2008 rectify this problem? Am
>>>>>>>> i better off calling MS Support and opening a case?
>>>>>>>>
>>>>>>>> Thanks!!
>>>>>