DFS

[weescotty]

Everything I've read about DFS mentions two distinct set of files, with DFS providing (through domain roots on multiple servers) a failover capacity.

Can I do the following -
Two servers, one 2008 the other 2003.
NAS with folders/files.

Create -
Domain root with 'namespace node/root' folders on two servers.
Link the folders from the NAS to each 'namespace node/root' folder.
Map drives from the domainspaces.

I want to use it to provide a failover for drive mapping in the event one of the 2 servers goes offline.
Just haven't seen any mention of a config where there is only a 'single' links source.

No need for replication as the data sources would be the same for each 'namespace node/root'

Workable?

Thanks

 

[58sniper]

DFS provides this out of the box. Each server running DFS maintains a copy of the data, transferring only the blocks of data that change for each file. Each is part of the DFS root. The local client will connect to the closest DFS server. In the event of a failure, the client will connect to the next closest copy of the data. It's by design.

DFS isn't meant to be two paths to the same storage. It's meants to be a resilient path to *A* copy of the data. Eliminates the single point of failure.

Do you have your Tek-Tips.com Swag? I've got mine!

Stop by the new Tek-Tips group at LinkedIn.

 

[weescotty]

Thanks I thought as much

Just trying to come up with a way of automatically dealing with drive mappings (2008 GPO) should the referenced path become unavailable due to a server failure.

Cheers

 

[weescotty]

Duh, what am I thinking about.

With a NAS I can do drive maps direct to the NAS eliminating the need for 'server' based drive maps.
OK the NAS is a single point of failure, but will be brand spanking new, and at least will have dual PSU and NIC's.

 

[58sniper]

In a multi-location environment, a NAS isn't ideal. DFS allows for local site copies of data that is replicated in real-time (or via schedule if you wish). It is completely isolated, so no single point of failure, assuming more than one DC.

Do you have your Tek-Tips.com Swag? I've got mine!

Stop by the new Tek-Tips group at LinkedIn.

 

[weescotty]

Yeah luckily enough although multi location (2), it is a single domain and everything is hosted here.
The remote site (only 5 people) use an IPSEC tunnel to get to the main servers.
The company as a whole isn't large enough to justify the remote office having its own set of data files etc.
Its always been if there is a problem here, they lose the same access as anyone local here.

So thinking just the NAS, drives mapped from CIFS shares on the NAS.
Create a symbolic link to the NAS parent folder on the server that has the backup software on it, and backup the NAS through the symbolic link.
Should avoid the need for a backup agent (not that there is one for a QNAP, is for ReadyNAS) that can be installed on 2008 x64.