Conectare
 
Pagina de pornireBibliotecăInformațiiFişiere de descărcatSuportComunitateForumuri
Resurse pentru profesionişti IT >
> 
> 
Server 2008 R2 DFS replication

Unanswered Server 2008 R2 DFS replication

  • 23 mai 2012 19:27
     
     
    Sign in pentru a vota
    1

    I set up a DFS namespace and replication between two file servers but I can't get files to replicate. When I run a health report I am getting the following error for one of the servers - DFS Replication cannot replicate files in the replicated folders listed above because the staging folder at {staging folder path} cannot be opened.

    I've verified the settings multiple times and everything looks good. That staging area folder path does exist and SYSTEM and (local) Administrators have full control. Both servers are enabled as members of the replication group. Both connections are enabled. The sending and receiving member look good. The schedule is set for 24x7. There's nothing currently in the folders besides a few small text files. There's plenty of drive space.

    Any help would be appreciated.

     

Toate mesajele

  • 24 mai 2012 04:32
     
     
    Sign in pentru a vota
    0

    Hello, 

    Here is good article to explain more about replication issues.

    I recommend you read it once and act accordingly.

    http://blogs.technet.com/b/askds/archive/2007/10/05/top-10-common-causes-of-slow-replication-with-dfsr.aspx

    Regards, Ravikumar P

     
  • 24 mai 2012 14:29
     
     
    Sign in pentru a vota
    0

    These folders cannot be replicated because the service is unable to create
    staging files. This can happen when:

    • The DFS Replication service does not have sufficient rights to the
      specified staging directory.
    • The path of the staging directory does not exist.
    • The configured path of the staging directory is not
      local.
    User Action

    Verify that the staging folder path is local (not a UNC or network path),
    exists, and that the service has access to it. The local system account and
    Administrators group must have Read and Write access to the directory.

    You can verify the staging path by viewing the DFS Replication management
    properties for the replicated folder or by using the Dfsradmin command line tool
    to list the properties of membership of a replicated folder.

    http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2.3790.1830&EvtID=4212&EvtSrc=DFSR&LCID=1033

    MCTS - Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. http://mariusene.wordpress.com/

     
  • 26 mai 2012 22:30
     
     
    Sign in pentru a vota
    0

    Thanks guys. I have read the articles posted and have checked settings, permissions, and a host of other things but still can't figure out why DFS replication is giving this error.

    Any other suggestions would be greatly appreciated.

     
  • 28 mai 2012 09:25
    Moderator
     
     
    Sign in pentru a vota
    0

    Hi,

    You could have a try to move the staging folder to another place so see the result. If there is any different error occurs, please let us know.

    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

     
  • 29 mai 2012 17:39
     
     
    Sign in pentru a vota
    0

    I already tried moving the staging folder - the error changes to show the new folder path but still gives the same - DFS Replication cannot replicate files in the replicated folders listed above because the staging folder at {staging folder path} cannot be opened, error.

    Edit - to add some more info - the servers are at different physical locations replicating across a site-to-site VPN tunnel. They are also in separate timezones with one being an hour behind the other (their times and timezone settings are correct for their respective locations).


    • Editat de Alceryes 29 mai 2012 17:47
    • Editat de Alceryes 29 mai 2012 17:47 more info
    •  
     
  • 30 mai 2012 09:13
    Moderator
     
     
    Sign in pentru a vota
    0

    Could you have a try to build a new replication group for testing? Please check if same issue still exists on new one.

    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

     
  • 30 mai 2012 14:37
     
     
    Sign in pentru a vota
    0

    Shaon,

    I already tried that (several times). Do you have any other suggestions?

     
  • 30 mai 2012 18:05
     
     
    Sign in pentru a vota
    0

    I'm stuck in the same situation as the OP. Alceryes, have you tried examining the DFSR debug log under %systemroot%\debug ?

    For me at least, the problem seems to be related to a failure to "delete old staging directory," which doesn't make any sense to me since this is a new install and the error recurs regardless of where the staging directory is. What it's trying to delete and why it can't are beyond me... anyone run into this before??

    20120530 13:56:00.251  244 CSMG  3689 [WARN] ContentSetManager::DeleteStageFolder (Ignored) Failed to delete old staging directory. Error:
    +    [Error:87(0x57) NtfsFileSystem::GetFileInfo ntfsfilesystem.cpp:2538 244 W The parameter is incorrect.]
    +    [Error:87(0x57) FileUtil::OpenByReferenceNumber fileutil.cpp:189 244 W The parameter is incorrect.]
    20120530 13:56:00.266  244 EVNT  1185 EventLog::Report Logging eventId:4212 parameterCount:7
    20120530 13:56:00.266  244 EVNT  1205 EventLog::Report         eventId:4212 parameter1:F1B74B7D-8ACA-4577-9558-7CB77383FBBD
    20120530 13:56:00.266  244 EVNT  1205 EventLog::Report         eventId:4212 parameter2:D:\DFSData\Data
    20120530 13:56:00.266  244 EVNT  1205 EventLog::Report         eventId:4212 parameter3:D:\Staging\ContentSet{F1B74B7D-8ACA-4577-9558-7CB77383FBBD}-{BF874174-E2E8-4810-819F-4A01212514AE}
    20120530 13:56:00.266  244 EVNT  1205 EventLog::Report         eventId:4212 parameter4:Data
    20120530 13:56:00.266  244 EVNT  1205 EventLog::Report         eventId:4212 parameter5:DOMAIN.local\repl\data
    20120530 13:56:00.266  244 EVNT  1205 EventLog::Report         eventId:4212 parameter6:6246E2B8-9477-480D-8A62-5A2F00F3458C
    20120530 13:56:00.266  244 EVNT  1205 EventLog::Report         eventId:4212 parameter7:BF874174-E2E8-4810-819F-4A01212514AE
    20120530 13:56:00.266  244 CSMG  7408 [ERROR] ContentSetManager::Initialize Failed to initialize ContentSetManager csId:{F1B74B7D-8ACA-4577-9558-7CB77383FBBD} csName:Data Error:[Error:9025(0x2341) ContentSetManager::Initialize contentsetmanager.cpp:7234 244 C The staging area is unusable]

    Rick Passero, MCSA:Security, MCSE:Security, CompTIA Security+

     
  • 30 mai 2012 19:28
     
     
    Sign in pentru a vota
    0

    Yes, I've got the same error in my debug log.

    So how do we clear out this 'old' data???

     
  • 17 decembrie 2012 23:21
     
     
    Sign in pentru a vota
    0
    Did anyone ever solve this?
     
  • 28 februarie 2013 00:42
     
     
    Sign in pentru a vota
    0

    Hi,

    I'm seeing the same issues. I already have a replicated folder on the server that is working just fine. The "Administrators" and "System" group both have full access to the staging folder. I also note that the timestamp on the staging folder keeps updating.

    Any assistance appreciated!