• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 97
  • Last Modified:

Dfsr Issue

This morning I discovered one of our DFS file server drives was out of space. I found a 17GB directory that I deleted but now the event log is telling me it cannot clear enough space in staging to replicated this change to our other DFS file server and that the world could possibly end if it can't auto fix this issue. Is there a safe way for me to just remove this from the staging folder and manually delete the folder on our other DFS server? Thanks
0
Shamil Mohamed
Asked:
Shamil Mohamed
2 Solutions
 
arnoldCommented:
Did stop/restart dfs/dfsr services?
What was the 17gb directory that you deleted?

Possibly by now, replication resumed.

Making sure you have both shares on each backed up just in case.

Running a report with each as the reference will/could shed light on the discrepancy.
0
 
Manjunath SulladTechnical ConsultantCommented:
Currently what is the replication status ? Is replication is working fine or you are getting error during replication ?

If replication is not happening due to low disk space,

Delete files from the Conflict and Deleted folder, or increase the quota of the Conflict and Deleted folder for the appropriate replicated folder(s).


Refer : https://technet.microsoft.com/en-us/library/ff633417(v=ws.10).aspx
0
 
Md. MojahidCommented:
Hope you have not gone thru http://blogs.technet.com/b/askds/archive/2011/07/13/how-to-determine-the-minimum-staging-area-dfsr-needs-for-a-replicated-folder.aspx

This article says,

The staging area quota must be as large as the 32 largest files in the Replicated Folder. Initial Replication will make much more use of the staging area than day-to-day replication. Setting the staging area higher than the minimum during initial replication is strongly encouraged if you have the drive space available.

Following is the Powershell script given to calculate size of 32 largest files in c:\temp directory.

###################

$big32 = Get-ChildItem c:\temp -recurse | Sort-Object length -descending | select-object -first 32 | measure-object -property length –sum
 
$big32.sum /1gb
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now