I'm not talking about moving shares from one node to another in the same cluster; I'm talking about moving them to a completely new cluster. Sorry, maybe "...new cluster node..." appeared to read as "new node on the cluster" when I actually meant "node on the new cluster".
To reiterate...
OLD: 1 file/print cluster with 2 nodes = 2 boxes
NEW: 1 print server cluster with 2 nodes + 1 file server cluster with 2 nodes = 4 boxes
Just my estimate RE: downtime.
There are maybe 10-20 shares, a name, an IP address -- basic stuff. I don't think the rest of your questions are relevant since I want to go to a new cluster.
Ideally I'm looking for some kind of MS migration tool. Is anybody aware of such a tool -- MS or 3rd party? If not, perhaps a quicker or more "sound" method than that which I have outlined?
Main Topics
Browse All Topics





by: SystmProgPosted on 2008-03-25 at 06:24:57ID: 21201637
Why do you say Shares will take at least 10-30 minutes to migrate? This is your assumption or you have tried in a test lab? As I understand, it should take more than 10 seconds to migrate the shares from one node to another.
How many resources are created? Do they all depend on each other? Have you tried breaking their dependencies and creating the separate groups and then moving them to those created groups. This way you could trnasfer resources group by group rather than transferring all the resources at a time.
Let us know.
SP