How do I migrate from MSCS to SFWHA?
Hi, I'm in the middle of a proposal and the customer ask us to describe the way (step by step) to migrate their MSCS (2003) to SFWHA (VCS)? do you know if Symantec has a procedure? Any recommendation? The customer requires minimal impact and smooth process?
Thanks for your help.
Gonzalo Gomez
Hi Gonzalo,
The switch to SFW-HA is dependent on what is being clustered.
Fileshares may not be too much problem depending on how they are clustered is MSCS. NTFS permissions will be not be changed by upgrading the physical disks to dynamic. Depending on how share level permissions are being handled there might be some extra steps involed. For the most part, I would guess that these are user home directories and the permissions are handled at the NTFS level and the share permissions are open to everyone FULL_CONTROL. In this case the disks would need to be upgraded to dynamic and the fileshare configuration wizard is SFW-HA would need to be run to create the Fileshare service group(s). The process is very simple and straight forward. However, with 3000 shares there are bound to be some that are not user home shares and would need more attention.
SQL is a MSCS aware application and installs differently in MSCS than in SFW-HA. Because of this SQL will need to be reinstalled to work with SFW-HA. The only tricky part with this is that each SQL instance needs to have its master database installed to a temporary drive that has the same path as what was used during production. Then it is a matter of stopping SQL, upgrading the production disks to dynamic, swapping what drive is in the mount path to SQL and running the SFW-HA SQL configuration wizard to create the service group for SQL. Since the master database is swapped to the production database, SQL will mount all user databases as normal.
Oracle is not installed differently in MSCS that I"m aware of. Swtichting the disk to dynamic and running the SFW-HA Oracle configuration wizard should be all that is needed.
I'm not familiar with the HP applicatoin that they are using. I'm not sure how it works. This would require some investigation to be 100%. In general, I would guess that this application is controlled in MSCS with a basic generic service type resource. If this is the case, then in SFW I would create a basic Fileshare service group, remove the fileshare resource and replace it with GenericService resource to control the HP service. Multiple GenericService resources maybe needed depending on the makeup of the HP services. A RegRep resource might also be needed.
These are very basic and highlevel overview of what needs to be done. Each cluster should be examined and a plan made for how best to migrate that cluster and its resources. There might be special considerations needed for each cluster or for only a few of them.
From your PDFs, it looks like your customer will continue using mirrored volumes between the sites and not VVR or hardware replication. If they have redundant links (with low latency) for heartbeats they might want to use Replication Data Clusters. If the links do not meet the needs for heartbeats then a GCO configuration would work.
Thanks,
Wally