File Replication Service Staging Area Full

[ctjohnson]

Hi-
I get the following message on all my domain controllers on a regular basis now. I've followed the instructions to raise the size of the staging area hundreds of megs on each, but it only solves the problem for a day. Is there some kind of way to purge the staging area? The size of the whole sysvol, including the staging area, is only like 200mb. What could be causing this?!?

The File Replication Service paused because the staging area is full. Replication will resume if staging space becomes available or if the staging space limit is increased.

The current value of the staging space limit is 675840 KB.

To change the staging space limit, run regedt32.

Click on Start, Run and type regedt32.

Click on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM, CurrentControlSet, Services, NtFrs, Parameters, and the value "Staging Space Limit in KB".

 

[Jpoandl]

I'm having the same problem...still looking into it. I'll let you know if I find a way.

Check your replication partners...one might be hung up. Joseph L. Poandl
MCSE 2000

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.esavio.com

 

[FrauW]

Although a year later...does anyone have an answer to this? I also increased the size of my staging area per the recommendation from Event Viewer, the system regulated itself and now my replication works again. However I anticipate I will have the same problem when the staging area gets full again. Is there any way to set up the system so that it purges itself automatically based on the space it needs to replicate? All tips welcome. ;-D

 

[Jpoandl]

Hello again..

Yeah, I also increased the size of my staging area (I did this on all servers using the staging area. In my case, the staging area was becoming full due to DFS replication. So, on all servers that were part of the replication topology, I increased the staging size. I made them all uniform in size.)

It is my understanding that replication works like this:

-Data comes into the Staging area (you will notice GUID looking files. These files are look wierd due to the mechanisms of the File Replication Service.)

-The data is processed and then exported to the proper location on the server. (Either Sysvol info or DFS replication data.)


If the data enters the staging area FASTER then the processing and exporting of the data is happening, your staging area may become full. Another reason your staging area may become full is if replication partners are failing.

In general, data will enter your staging areas faster then data is sent out and removed from the staging area. You can think of this staging area as a buffer. You may need to increase the size of the staging area if the amount of data being replicated is LARGE.

I've actually made my staging area larger then the amount of data I am replicating. This way, I know my staging area will never become full. I have plenty of disk space so this was an easy choice for me.

I haven't had any problems with the staging area after I made the size bigger.

If you are noticing that data is not being removed from the staging area, then you have a more complication problem.

-hope this helps..

Joseph L. Poandl
MCSE 2000

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[FrauW]

Hey, thanks for the quick answer. I will watch how the staging area grows. FYI... I only made the staging area on 2 of the 4 dcs uniform. With DFS I only have the data partition replicating between two servers. The other 2 DCs are only replicating the profiles folder so I thought that it didn't matter if their staging area remained the default size. If you still think I should make the staging area on all 4 the same give me a shout. Otherwise, I'll assume that it's OK as is. Thanks ;-)