Restoring DFSR (Distributed File System Replication) Data with Backup Exec

 

In Backup Exec, Windows Server DFSR data is protected by using  the Microsoft DFS Replication Service Writer. For configurations that use DFSR, you can protect the replicated data by running a Shadow Copy Components Distributed File System Replication backup of the replicated data on any server that is hosting the replicated data. DFSR information is backed up and restored by selecting Shadow Components - User Data - Distributed File System Replication selections.

By default DFSR data is restored back to the original location assuming the DFSR "Replicated Folder" was not removed from the DFS Management Console or DFSR information was not removed from Active Directory.
With the Default Restore options checked, the DFSR data will be restored back to the "replicated folder" Preexisting folder (\DfsrPrivate\Preexisting). This will prevent the data being restored from unintentionally being replicated out to other members of the DFSR replication group.

 

After DFSR data is restored a DFS Replication Event will inform you to move the data from the DfsrPrivate\Preexisting folder to the replicated folder if replication to other DFSR replication members is desired.


DFS Replication Events after a restore:


Event Type: Information
Event Source: DFSR
Event Category: None
Event ID: 4104

Description:
The DFS Replication service successfully finished initial replication on the replicated folder at local path D:\corp\home\users.

Any local pre-existing content in this replicated folder that did not exist on the primary member for Users_Home has been moved to the hidden system folder DfsrPrivate\Preexisting under the replicated folder root.

Content in the DfsrPrivate\Preexisting folder will not be replicated to other members of the replication group, and will not be deleted by the DFS Replication service during any automatic clean-up. If you would like this content to be replicated to other members, please move the content into the replicated folder outside the DfsrPrivate folder.

Replicated Folder Name: Users_Home


 

If it is desired for the DFSR data to be restored back to the original "replicated folder" and not to DfsrPrivate\Preexisting folder then an authoritative DFSR restore must be performed.
 

In the restore job properties under Advanced Setting check the box " Mark this server as primary arbitrator for replication when restoring folders managed by the File Replication Service or when restoring SYSVOL in system state".

 

This authoritative restore will restore the data back to the original "replicated folder" and replicate this restored data out to other DFSR replication members.  A series of DFS Replication Events will occur on the server where the restore is being performed and DFSR replication member servers.
 

DFS Replication events (Target server):

Event Type: Information
Event Source: DFSR
Event Category: None
Event ID: 4106

Description:
The DFS Replication service detected that an authoritative restore was performed on the replicated folder at local path D:\corp\home\users and is processing the restore. Replication has been paused until the restore completes.

Additional Information:
Replicated Folder Name: Users_Home
Replicated Folder ID: 5A11FE16-B411-47FD-B2F5-91F061112147
Replication Group Name: CorpReplicationGroup
Replication Group ID: CC316971-DD82-4D98-BD6C-92FE1BC3FB3B
Member ID: 3906ACAA-7E8F-47A0-B3AF-17C5DB5E1345

-------------------------------------------------------------------------------------------------------------------------------

Event Type: Information
Event Source: DFSR
Event Category: None
Event ID: 4108

Description:
The DFS Replication service successfully processed an authoritative restore for the replicated folder at local path D:\corp\home\users.

Additional Information:
Replicated Folder Name: Users_Home
Replicated Folder ID: 5A11FE16-B411-47FD-B2F5-91F061112147
Replication Group Name: CorpReplicationGroup
Replication Group ID: CC316971-DD82-4D98-BD6C-92FE1BC3FB3B
Member ID: 3906ACAA-7E8F-47A0-B3AF-17C5DB5E1345

-------------------------------------------------------------------------------------------------------------------------------


 

If an authoritative restore is performed DFSR will determine if the data being restore will replicate out and overwrite existing files on DFSR replication members through a (winning/losing) conflict resolution process.
 

The losing file or file version will be moved to the DfsrPrivate\ConflictAndDeleted folder.



DFS Replication Events (Replication Members)


Event Type: Information
Event Source: DFSR
Event Category: None
Event ID: 4412

Computer: BRANCH-SERVER
Description:
The DFS Replication service detected that a file was changed on multiple servers. A conflict resolution algorithm was used to determine the winning file. The losing file was moved to the Conflict and Deleted folder.

Additional Information:
Original File Path: D:\Users_Home\DOCS
New Name in Conflict Folder: DOCS-{0C9542D1-F31D-49D8-B57E-9247A4E862DA}-v1153
Replicated Folder Root: D:\Users_Home\DOCS
File ID: {0C9542D1-F31D-49D8-B57E-9247A4E862DA}-v241
Replicated Folder Name: D:\Users_Home
Replicated Folder ID: 5A11FE16-B411-47FD-B2F5-91F061112147
Replication Group Name: CorpReplicationGroup
Replication Group ID: CC316971-DD82-4D98-BD6C-92FE1BC3FB3B
Member ID: 3D394569-C7EF-4EF5-AE45-4D9CE5F48AA0





DFSR Redirection:


In Backup Exec  DFSR restore Redirection is possible, BUT only to a file system on a Windows  server with an active DFSR VSS writer present.  DFSR backup sets can be redirected to a drive/folder and then moved to DFS "replication folders" or another location if desired. The original DFSR structure does not have to exist to redirect restore DFSR backups sets to a file system.