Error 9036
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: DFS 2008 R2 Replication issue Event ID 5014: error: 9036 (Paused for backup or restore) Windows Server > event id 5014 dfsr server 2012 File Services and Storage Question 0 Sign in to vote We have the
Event Id 5014 Error 9033
basic hub and spokes setup where we have 10+ branch offices replicating their data to our hub dfs server which
Dfs Error 5002
is backed up nightly. All of the branch office DFS servers all have this SAME event at 4:01 am, the time that the backup is initiated at the hub location. They resume replication successfully.
The Dfs Replication Service Is Stopping Communication With Partner Error 1726
1 of the servers at one of the branch offices has the same warning event id 5014 with the 9036 error, but does NOT resume replication FULLY. The Hub can send to the branch, but the branch can not replicate to the hub. On the troubled branch office server, here's the error I see in the dfs log at the time of the backups... error:9027(0x2343) InConnection::ReceivevvUp inconnection.cpp:3843 the dfs replication service is stopping communication with partner error 5014 1776 C A failure was reported by the remote partner Josh Monday, February 27, 2012 2:40 PM Reply | Quote Answers 0 Sign in to vote Andre, What we had to end up doing is setup a scheduled task on the branch office DFS server to restart the DFS replication service in the mornings after the DFS backup finishes. There was no other resolution that I found. Thanks, Josh Marked as answer by iconoclast88 Thursday, October 17, 2013 11:54 AM Thursday, October 17, 2013 11:53 AM Reply | Quote All replies 0 Sign in to vote Hi Josh, I have a suggestion for your current situation. You can setup the replication schedule to stop replication from such as 4:00am to 6:00am, waiting for the backup to be finished. Then the backup process will not affect the replication process. For your current issue, I would like to know if specific files could not be replicated from branch office to hub or all files. You can create a file like txt file to test. Also please test if restart/rejoin the server in branch office to the replication group will help on it.TechNet Subscriber Support in forum |If you have any
Mentions744 Products Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT TECHNOLOGY IN THIS DISCUSSION Join the Community! Creating your account only takes a few minutes. Join Now I've been banging my head against the wall with this issue for error: 9033 (the request was cancelled by a shutdown) the better part of two weeks now; here's hoping you guys can help me fix this. error id 9036 paused for backup or restore I have a two-server domain that I am working with. Both servers are running Server 2008 R2 SP1, at full 2008 functional level. DFS-R dfs error 5014 is set to replicate a shared folder between the two, as well as the SysVol volumes on both servers. APP01 is one of the servers, DC01 is the one giving me problems. My problem is this: every night at ~9:45 https://social.technet.microsoft.com/Forums/office/en-US/bcc469d7-c4af-4b59-9888-dee268ce6384/dfs-2008-r2-replication-issue-event-id-5014-error-9036-paused-for-backup-or-restore?forum=winserverfiles I get the following error for each replication group on DC01: The DFS Replication service is stopping communication with partner APP01 for replication group shared due to an error. The service will retry the connection periodically. Additional Information: Error: 9036 (Paused for backup or restore) Connection ID: D96F4693-34A8-44C4-9C6C-9F68C92CDF2B Replication Group ID: 60691732-94A1-4662-9FB1-CBF358E81B1E On my shared public folder, replication starts again with no issues. However, the SysVol folder does not start properly. Any changes to SysVol on DC01 are https://community.spiceworks.com/topic/241234-dfs-replication-crashes-every-night-during-backup propagated outbound, but it does not read any changes from APP01 inbound until I have restarted the DFS-R service. When I do, everything starts working again. I have applied several hotfixes - including one pertaining to backups that so perfectly described my problem I was SURE it would work - as well as a half dozen other fixes I've found online, and I'm at my wits end. A quick dcdiag on DC01 gives me no errors except for DFSEvents - which reports the issues I've already described. Some things I've read online suggest that a backup might be causing this, but my backups do not run until 11PM. I am getting the following error as well, although I'm not sure it is related: The description for Event ID 3041 from source MSSQL$MICROSOFT##SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: BACKUP LOG SUSDB The specified resource type cannot be found in the image file If you guys have any advice at all, I would appreciate it. This has been going on for a while, and I have no idea when it started happening, but it's d