Hi all, I currently have a project to move a clustered file share resource from an older two node server 2003 file share cluster, to a newer Windows 2008 R2 file share cluster. My problem is that they don't want to incur any downtime for the move, as other application services are dependent on some of the files in this share. I have the two shares in sync already, and what I thought I would do is this: Lets say the file share network name is \\files.xyz.com On all the servers that access this file share I would put in a host file that points that name to the current ip of the server. Then on the old 2003 cluster I'd change the network name to something like filesold.xyz.com, and on the new cluster id add in the name files.xyz.com to the new share. I'd then check dns and wins and make sure there going to the new server, and test on one node by removing the host file, flushing dns, and the trying the share.
My issue is that as soon as I change the network name on the old clustered share network name resource, the clients all are no longer able to access via that name (even with the hosts file). IT says duplicate name on the network. Access to the files via ip works fine, but the apps call it via a netbios name. Any suggestions on how to do this? I thought there was a way to add a name into the registry that a server would continue to respond to, but this being a cluster, I don't know how to get that to work. Any help is much appreciated. -Greg ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
