Manually deleting the \dfsrprivate\conflictanddeleted content

Discussion in 'File Systems' started by J Ford, Dec 31, 2007.

  1. J Ford

    J Ford Guest

    I have 2 DFS (R2) servers being used to replicate Citrix profiles. This is
    working well. However, I do have what I would consider to be an abnormally
    large amount of files in the ConflictAndDeleted folder for the directories
    being replicated. Granted, TS profiles can contain a lot of both regular and
    hidden files---especially in our case because we use Reuters Bridge which
    contains 1250, albeit not too large, 'user preferences-related' files or so
    in and of itself---but I'm talking about 208MB, 26000+ objects in

    Users will never need to 'retrieve' files from here, and we're using VSS
    snapshots on the replicated folders anyway, so I'd like to just 'start over'
    with the Conflictanddeleted count (have a theory of my own, for our
    particular environment, as it grew so seemingly large in only a couple of
    weeks). This way, I'd get a 'baseline' of sorts and be able to watch it from
    scratch if the content was just completely cleared out.

    So my question is, what's the best way to 'delete' the 'ConflictAndDeleted'
    folder's entire contents, and do I need to 'delete' its content on both
    servers involved in replication?
    J Ford, Dec 31, 2007
    1. Advertisements

  2. J Ford

    Rudolf Meier Guest


    Every server contains it's own specific files in this folder, so yes, you
    have to delete it on every server. As far as I know it's safe to delete it,
    but still not officially recommended. But you can set the maximum size of
    those folders to a smaller size using the DFS-snapin.

    Rudolf Meier, Jan 3, 2008
    1. Advertisements

  3. J Ford

    J Ford Guest

    Yeah, thanks---I know the default quota is 660MB (interesting number they
    chose), and know how the 60%/90% thresholds work, etc. I actually increased
    the quota from 660MB to 5GB because disk space definitely isn't an issue.

    But I guess that manifest .xml file is just plain going to become a beast.
    Perhaps it's just better to leave the default quota alone as I move forward
    with other namespace folders, and implement VSS on the data volumes involved
    (since VSS is supported for DFS folder targets), and retrieve file versions
    'point in time' instead of digging through that beast.
    J Ford, Jan 3, 2008
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.