I have successfully been using failover clusters for Highly Available Virtual Machines and also for SQL Server. I have just recently setup a new 2-node Server 2008 R2 Failover Cluster and have configured it to run File Services.
All components of the cluster are working correctly with the exception of DFS Replication. I have been using DFS and DFSR for several years with no trouble.
I followed the instructions in this posthttp://blogs.technet.com/b/filecab/archive/2009/06/29/deploying-dfs-replication-on-a-windows-failover-cluster-part-iii.aspx and, after adding the cluster to the replication group it came up in WSFC as expected.
The problem happens when I move the file server service to the other node… I then note the following errors in the eventlog of the node I am attempting to failover to:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The DFS Replication service failed to bring the following failover cluster resource online: 'DFSR E:\Software'. The cluster service will retry the operation periodically.
Additional Information:
Replicated Folder Name:
Replicated Folder Path:
Replicated Folder ID: 2FCC0A22-F83C-49E4-9455-C997BE7D27F8
Replicated Folder Resource Name: DFSR E:\Software
Replication Group Name:
Replication Group ID: 471E7714-4033-44A7-9850-54822F2C100B
Staging Folder Path:
Error: 9101 (The registry key was not found)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
As noted, all other components of the cluster (shares, volumes, etc) failover just fine. Only DFSR gives me this problem. If I fail back to the primary node, it picks itself up again.
Any help would be appreciated since I have not been able to find much info on either error 9009 or 9101.