Hi Everyone,
I'm currently going through the process of "rebalancing" the storage in a DFSR Hub Server environment that I manage. This is due to increase of size for certain replication groups, and we shift several RG's around in order to ensure the drives on
the DFSR Hub Servers do not run out of space.
As all Hub servers reside in the Same Data Center/LAN, no preseeding of data is done.
We use the following process:
- Identify alternate DFSR Hub Server which has a drive/Volume with sufficient space;
- Create a new member in the replication group
- create connections between the current hub server and new hub server
- create the appropriate folders on the new hub server and storage
- update replication group
- update staging location and size to seperate volume
- dfsrdiag pollad on both hub servers
- Replication starts
One thing that i recently noticed was that sometimes when we follow this process, when running a backlog report both ways (I.e. from the Source Hub Server ---> Destination Hub Server and vice versa), the Destination Hub Server starts to slowly build up a backlog, which is usually predominantly folders... (i.e Destinataion Hub Server ---> Source Hub Server is showing a backlog of folders/files to send back)
The reason i find this strange is that the replication to the destination hub server is clean (i.e. not preseeding is done, so I don't understand how it could start to generate a backlog report).
Has anyone else ever experienced this? Is this normal?
Thanks in Advance!