Information Technology Reference
In-Depth Information
After preseeding with Robocopy is complete, you can import the cloned database and
XML configuration with the following command (again H: is the target volume and \dfsrclone
is the target path):
Import-DfsrClone -Volume H: -Path "H:\dfsrclone"
When Get-DfsrCloneState returns Ready, or when the DFS-R event log shows an Event
4104 (one event per replicated folder), you can complete configuring the replication by
adding the target server to the replication group and setting its membership state with this:
$DfsrSourceComputerName = "<sourceserver>"
$DfsrDestinationComputerName = "<destinationserver>"
$DfsrReplicationGroupName = "<DFS-R Group>"
$DfsrReplicatedFolderName = "<DFS-R Folder>"
$DfsrReplicatedFolderPath = "<DFS-R Folder Path>"
Add-DfsrMember -GroupName $DfsrReplicationGroupName `
-ComputerName $DfsrDestinationComputerName
Add-DfsrConnection -GroupName $DfsrReplicationGroupName `
-SourceComputerName $DfsrSourceComputerName `
-DestinationComputerName $DfsrDestinationComputerName
Set-DfsrMembership -GroupName $DfsrReplicationGroupName `
-FolderName $DfsrReplicatedFolderName `
-ContentPath $DfsrReplicatedFolderPath `
-ComputerName $DfsrDestinationComputerName
Use the Get-DfsrPreservedFiles cmdlet to discover any files that had conflicts during the
database cloning, and use the *-DfsrPropagationTest cmdlets to validate replication.
You can use the database cloning technique to speed up recovery from a corrupted DFS-R
database on a server. This corruption can be caused by hardware issues, such as an abrupt
power loss. Rather than wait for the slow process of an automatic nonauthoritative recovery
to complete, you can clone the primary database, as described previously, and use it to
recover the corrupted database. You won't need to preseed the replicated folder, so you can
skip that step, but you should remove the memberships of the problem server to prevent
DFS-R from attempting to rebuild the database until the cloning is complete.
If the only DFS-R memberships for the server are on the same volume as the corrupted
database, use Windows PowerShell to remove the member with this:
Remove-DfsrMember -GroupName <dfsrgroup> -ComputerName <dfsrservername>
