Distributed File System help.

[boomam]

Hi.

Ive been setting up the shares for our new network and took the decision to use DFS.

As such, ive created some namespaces on our storage server called Home, Profiles & Drives. With each of those 3 namespaces having 'shortcuts' to UNC paths/shared folders for them.

So for example:

\\Domain\Home\Intake02\

 

I was under the impression that if, in DFS, i goto the properties of that shortcut that i could change where its pointed to, thus allowing seemless moving of files around the network to the clients.

However, this doesnt appear to be possible?

 

This is on Storage Server 2003 btw.

 

Ideas?

 

Thanks in advance all. .

 

##EDIT##

Ive just been reading on technet about DFS and 'think' i hve a slightly better understanding of it.

Alot of the articles mention that i can have multiple targets for one folder, thus allowing whichever of those identical targets is quicker to access, be accessed by the client.

So, going on that: Am i correct in thinking that, lets say hypothetically, in the future, i setup another server with DFS, have it replicate off the first namespace/s, add another target in the relevent folder that has the original data in it, then delete the first target off the first server, that it will basically do what i originally thought DFS is for?

 

Thanks again btw. .

Edited August 3, 2008 by boomam

[powdarrmonkey]

If you want DFS to copy things for you, you need to configure replication between the targets.

[box_l]

and afaik, you will need 2k3 r2 if you want replication.

 

if you dont have another 2k3 storage server, that is.

 

BoX

[powdarrmonkey]

You only need R2 if you want it to use the flashy new transfer protocol. Original 2K3 will still replicate, just less efficiently.

[srochford]

In DFS management, you've got 2 bits - one for namespace and the other for replication.

 

I'm guessing you're trying to do something like this: Put the home folders on (say) server1 now but in a year's time you're going to replace that server with server2 but don't want to change everything that references server1.

 

In this case, you don't need to worry about replication; just set up the namespace "home" to point to the share "home" on server1. In a year's time, copy all the files from server1 to server2 (robocopy or other tool can be used to do this, preserving permissions etc) and then add a new namespace server - server2. Once that's done, you can remove server1 from the namespace and unshare home on it.

[box_l]

ahhh!

 

in the windows storage server management mmc

 

it makes a fuss cos its looking for the new flashy version.

 

i switched to the other mmc and all seems good.

 

BoX