Solved

DFSR event ID 1112 caused by Symantec Backup Exec restore

Posted on 2016-08-12
4
121 Views
Last Modified: 2016-08-22
I've been having problems with DFS the last few months. This is the last topic for background:

https://www.experts-exchange.com/questions/28957057/DFSR-not-working-in-one-direction.html

The servers are running Server 2008r2.
In short, replication wasn't working. Didn't know why but got it fixed. However, I noticed the last issue occurred at the same time a restore job was run on Symantec Backup Exec. I suspected that another restore job would cause the issue again.
These are two file servers (A and B) in different sites which are set up to replicate different groups. Only one of these groups is being backup'd up with Symantec Backup Exec. The problematic one.

So today I decided to test what I suspected was causing the issue.
The DFSR has been working fine for the last two weeks. No restores have been made during that time either.
I deleted one of my own folders on the drive and attempted a restore.
The restore failed per Symantec though it did recover all but one file. The last file was unimportant and I could recover it with VSS so not a big deal.
However, there were several Event ID 1112 errors (around 20) logged in DFSR Event Viewer. (DFSR failed a restore request)
5 minutes after those errors finished, a 4110 warning is logged. (DFSR has started processing a database recovery)
6 minutes after this, a 4102 error is generated. (DFSR service has initialized the replication folder)
These all occurred on the Server A, none of these errors are on Server B so of course this was caused by Symantec.

Fortunately, I'm familiar with this issue now so I set up Server A as primary and now the initialization is processing without a problem.

My question is:
What has been set up incorrectly on either DFSR or Symantec Backup Exec?
Something wrong is causing a restore with Symantec to corrupt the database and trigger it to re-initialize.
The 1112 event has this text:
"This could happen if an attempt was made to restore the contents of a read-only replicated folder authoritatively. Read-only replicated folders should only be restored non-authoritatively. Authoritative restores should be performed only on read-write replicated folders."

Is this a permissions issue?
0
Comment
Question by:SeeDk
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 37

Expert Comment

by:Mahesh
ID: 41754906
two things here

Have you deleted replicated folder itself or you have just deleted some file / folders underneath replicated folder?
If you deleted entire replicated folder and restored from backup software, then it would very much possible that DFSR treat this folder as entirely new

If you have just deleted sub folders under replicated folder, After you deleted folder does deletion is replicated to its replicating partner? have you tested that?
0
 

Author Comment

by:SeeDk
ID: 41756335
Hi Mahesh,

1. I only deleted a sub folder underneath the replicated folder.
More specifically, if replicated is "H:\Files", I only deleted "H:\files\dept\user\folder"

2. Yes, the deletion of the sub folder was replicated to the replicating partner.
0
 
LVL 37

Accepted Solution

by:
Mahesh earned 500 total points
ID: 41756632
OK
If deletion is replicated, it means DFSR is working properly

Then ensure while restoring, you will just restore folder and uncheck any hidden files folders such as system volume information\DFSR

Normally backup and restore operations stop / pause DFSR replication temporarily

may be there is issue with VSS and backup exec settings, you need to check with Symantec support
0
 

Author Comment

by:SeeDk
ID: 41765212
Thanks, Mahesh.
The issue is just Symantec as you explained.
The restores only cause the issue when Symantec tries restoring the file back to its original location.
When restoring to a different location, DFS does not have any problems.
0

Featured Post

Why You Need a DevOps Toolchain

IT needs to deliver services with more agility and velocity. IT must roll out application features and innovations faster to keep up with customer demands, which is where a DevOps toolchain steps in. View the infographic to see why you need a DevOps toolchain.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A company’s centralized system that manages user data, security, and distributed resources is often a focus of criminal attention. Active Directory (AD) is no exception. In truth, it’s even more likely to be targeted due to the number of companies …
Determining the an SCCM package name from the Package ID
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question