Information Technology Reference
In-Depth Information
So you can create a domain-based DFS-N root target on each node of a failover cluster using
the local storage of each node. In the event of a node failure in the cluster, the DFS-N is still
available. You can also create DFS-N roots on nonclustered servers to provide the same level
of fault tolerance.
In a domain with a single domain controller, the unavailability of that domain control-
ler also renders the DFS-N in the domain unavailable. To avoid a single point of failure
for your DFS-N, you must ensure that there are at least two domain controllers for each
domain that has a DFS-N root.
Stand-alone DFS-N fault tolerance
To ensure the availability of a stand-alone DFS root, you create the root on the shared cluster
storage of a clustered file server by using the Cluster Administrator console. In the event of a
failure of any node in the cluster, the DFS-N continues to be fully available as long as a single
node of the cluster is available.
A stand-alone DFS-N is not dependent on Active Directory, so there is no specific
requirement for domain controllers with a stand-alone DFS-N. If the cluster that hosts the
stand-alone DFS-N is available, the DFS-N is available.
Windows Server 2012 R2 adds the capability to clone a DFS-R database to speed up initial
synchronization time dramatically. You use preseeded files and an export/import process to
quickly set up replication and synchronize the databases. Cloning a DFS-R database can be
done only by using Windows PowerShell.
To clone a DFS database, first create the replication group and folders by following these
steps:
Create and populate the folder that will be the source folder.
1.
Create a replication group with New-DfsReplicationGroup.
2.
Add a DFS replicated folder with New-DfsReplicatedFolder.
3.
Add the source server as a DFS-R member server with Add-DfsrMember.
4.
5.
Set the source server as the PrimaryMember with Set-DfsrMembership.
After the replication folder is successfully initialized, a DFS-R event 4112 is issued, and you
can export a clone of the database.
