C
Chris Turner
Hi,
Situation:
I have a Win2K file server that hosts data in multiple
user shares on it's d: partition which is running out of
space. We bought another disk to add as another partition,
f:.
The goal here is to migrate the user's shared data on d:
to f:, freeing up space on d:, with minimal/no disruption
to the users.
DFS seems to offer a solution to this problem. The idea is
to replicate the data from d: across to another share on
f: & then 'switch off' the d: share - hey presto!
Problem:
I realise I would have to implement the use of the DFS
tree rather than direct shares to be able to take
advantage of its failover functionality. This would not be
a problem, but in testing the idea, I cannot see a way
to 'switch off' the old linked share on d: in the DFS so
that users stop saving data to it & automatically move
over to the new linked share on f:.
I've tried using the 'take replica offline/online' flag in
the DFS manager, but this does not seem to force users
over to the replica share as I was expecting & data is
still saved to the old share.
Any ideas on how to do this/what I'm doing wrong?
Situation:
I have a Win2K file server that hosts data in multiple
user shares on it's d: partition which is running out of
space. We bought another disk to add as another partition,
f:.
The goal here is to migrate the user's shared data on d:
to f:, freeing up space on d:, with minimal/no disruption
to the users.
DFS seems to offer a solution to this problem. The idea is
to replicate the data from d: across to another share on
f: & then 'switch off' the d: share - hey presto!
Problem:
I realise I would have to implement the use of the DFS
tree rather than direct shares to be able to take
advantage of its failover functionality. This would not be
a problem, but in testing the idea, I cannot see a way
to 'switch off' the old linked share on d: in the DFS so
that users stop saving data to it & automatically move
over to the new linked share on f:.
I've tried using the 'take replica offline/online' flag in
the DFS manager, but this does not seem to force users
over to the replica share as I was expecting & data is
still saved to the old share.
Any ideas on how to do this/what I'm doing wrong?