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

DFSR event ID 1112 caused by Symantec Backup Exec restore

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
SeeDk
Asked:
SeeDk
  • 2
  • 2
1 Solution
 
MaheshArchitectCommented:
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
 
SeeDkAuthor Commented:
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
 
MaheshArchitectCommented:
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
 
SeeDkAuthor Commented:
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
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

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

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