If your not aware already, Windows Server 2012 R2 releases some enhancements with the DFS-R Technology. One of them is the ability to export the DFS-R database from System Volume Information and then import the database onto a remote server. This is aimed at significantly reducing the amount of time it takes to pre-stage data for DFS-R Replication (something which can take weeks when you have terabytes of data with lots of small files!)
This new feature is documented on the following TechNet article:
http://technet.microsoft.com/library/dn482443.aspx
I followed these instructions exactly and I get the following error on the destination server. This error generates approximately 3 hours after running the Import-Dfsrclone cmdlet. During the import the dfsr.exe process is very busy with lots of CPU/disk activity generated which can be observed using Resource Monitor. After approximately 3 hours the following error is generated:
Import-DfsrClone : Could not import the database clone. Error code: 0x00001774
I have many customers running DFS-R Replication on 2012 R2 and have tried this procedure at 3 different customers thus far. Every time I have attempted this procedure it has failed and I have had to revert to the old method of pre-staging the DFS-R database over the slow WAN link resulting in the process taking weeks to complete.
Has anyone else had problems with this process? Next time it happens I may log a PSS case with Microsoft and see what they have to say.
Kind Regards,
Clint Boessen MVP - Exchange Server, MCSE, MCITPx6, Dip Network Engineering
Perth, Western Australia
Blog: http://clintboessen.blogspot.com
Employer: http://www.avantgardetechnologies.com.au
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.