Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 5654

2003 to 2008r2 mscs file server migration

$
0
0

Hi All,

I am in the process of migrating a 2 node 2003 file server cluster to 2008r2 and ultimately to 2012.

Where I run into problems is with the shared folders. With the 2003 cluster we have many shares – over 100 - with many scripts and a few applications that depend on connecting to those shares using the UNC \\clustername\share name. I have built up a test 2008r2 cluster and ran the cluster migration wizard only to find that I can no longer use the Cluster name to connect to the shares. What we have in the production 2003 cluster are 7 resource groups. The default cluster group has the following resources, IP address, Cluster name and Quorum. The remaining 6 resource groups each have a physical disk, network name, IP address and the shares residing on the disk within that group. Once the migration wizard is completed on the 2008r2 cluster, I see new file servers under services and applications with the same name as the network name resource in the 2003 cluster.

What I was hoping to do was to run the wizard, offline the old cluster then rename and set the IP’s of the new cluster with the old name and IP’s then have the users connect using the same UNC as they did with the old cluster. This doesn’t look like it’s going to work as none of the shares appear to be available using the 2008r2 cluster name. I’m thinking I could migrate the settings and shares then create a new file server with the same name as the old cluster name then move all the share resources to the file server but I’m not even sure how to do that or if that would work.

I’m probably missing some information at the moment to get the answer I need but in short what I’m looking to do is…

  1. Upgrade the cluster from 2003 to 2008r2 using new server hardware but the same storage.
  2. Because of the scripts and applications that depend on connecting using the \\clustername\sharename convention from 2003, I need to find a way migrate the shares and continue to somehow use the old cluster name as a single point of access (CAP I’m assuming) for all users to connect to all the shares.

Microsoft has a step by step guide on the migration process (if you want to call it step by step)https://technet.microsoft.com/en-us/library/cc754481(v=ws.10).aspx) but I can’t seem to find much documentation on my scenario.

Thanks very much in advance,

John


Viewing all articles
Browse latest Browse all 5654

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>