"David K" <> wrote in message
news:...
> Sybex's 70-215 2nd ed book on page 388-389 states how only
> domain-based Dfs roots can have root-level Dfs shared folders.
That's not true -- only the Domain DFS can have ROOT REPLICAS,
but Stand-alone have have (must have) as share at the root level.
With Stand-alone you cannot replicate the ROOT to another server.
> I don't understand what a root-level Dfs shared folder is. Is it
> talking about replicating the single root folder, or replicating the
> entire Dfs structure, or all the first-level folders (meaning all of
> the folders since only a single level is allowed in stand-alone Dfs
> roots), or what?
You may be confusing Shares, with Directories, with DFS Root/Links.
(Please do yourself a favor and avoid the very imprecise word "folder"
when trying to sort this out -- yes I know lots of people use it but it is
DESIGNED to mask the differences, for users, between the various
physical implementations.)
Ok, a Share is on a single server and represents a network offering
(sharing)
of a directory tree (aka folder).
A Directory is on a disk drive (or some substitute) and represents a volume
tree (or subtree) of directories, subdirectories, and files.
A DFS root (or link) comprises one or more shares and thereby points to the
directories offered by those shares -- and so must be replicated if
there is more
than ONE share for the ROOT, or more than one share for a particular
LINK.
Note: Root and each Link are different and distinct (see below.)
DFS root is the TOP of a particular DFS hierarchy and has:
At least one share (or in JUST the Domain case, perhaps more than one
share)
Optional Links, i.e., Link1
DFS roots appear to act much like Shares, by offering the resources at the
top
directory level of the root share(s) AND all files and subdirectories
below.
DFS links appear AS IF they are subdirectories under the "root" but each
has it's
OWN set of (one or more) shares
When a DFS Root or Share has more than one "share" for THE root, or any
PARTICULAR LINK, that set is usually called a "Replica set."
So it looks like this:
DFS Root --> points to one or more (Domain-only) servers with the REAL
shares
Real-Share Directories appear here
with share root level files
And subdirectories
and files
etc.
Link (optional) --> Points to one or more servers with the REAL
shares
(looks like a subdirectory to users)
Real-Share Directories appear here
with share root level files
And subdirectories
and files
etc.
> And why is it Dfs instead of DFS?
Stupid Sybex. Everyone I know writes DFS
The rules:
Domain based DFS can have:
Root replicas
Automatic replication
Better fault-tolerance since the DFS INFO (not the data) is stored
in AD
The rules:
Stand-alone or Server based DFS can have:
NO Root replicas
NO Automatic replication (at the link level)
less fault-tolerance since the DFS INFO (not the data) is stored
on ROOT server in the Registry
--
Herb Martin
|
Similar Threads
