INF: Clustered SQL 7.0 Servers and Rolling Operating System Upgrades or Updated MDAC Installations

ID: Q239473

The information in this article applies to:
  • Windows 2000, version 1.0
  • Microsoft SQL Server, Enterprise Edition, version 7.0

SUMMARY

When performing operating system upgrades, Windows NT 4.0 Enterprise Edition to Windows 2000 Advanced Server, with clustered SQL 7.0 servers, or when a new Microsoft Data Access Components (MDAC) version is installed to a clustered SQL Server, SQL requires rebinding to the virtual SQL DLL files.

After acquiring the utility from SQL Product Support Services and executing the self extracting zip file, 70rebind.exe, the application creates and extracts the contents to the default directory of c:\70rebind. After stopping the appropriate services as referenced in

Q219264 INF: Order of Installation for SQL Server 7.0 Clustering Setup
you can re-establish the correct file bindings.

Specific instructions dealing with implementing a rolling OS upgrade to Windows 2000 Advanced server are listed below.

NOTE: If you have Microsoft SQL Server clustering installed and have removed Microsoft SQL Server clustering using the Failover Cluster Wizard before performing the upgrade, use of this utility is not necessary. All proper bindings occur when you re-cluster SQL.

Using the 70rebind.exe Utility for Performing Windows 2000 Rolling Upgrades or MDAC version Upgrades to Clustered SQL Servers

    Please note the directory where you extracted the 70rebind utility to if other than the default c:\70rebind location.

  1. If the Active/Passive cluster model is being used pause the node not actively in use. If using the Active/Active cluster model choose one of the nodes and pause the cluster service on that node.


  2. Move all cluster resources from the paused node to be upgraded to the active node.


  3. Perform the OS upgrade to the paused node.


  4. Once the upgrade is complete right-click My Computer and select Manage.


    1. Expand the Services and Applications section.


    2. Select Services.


    3. Stop the Network Connections service, which also stops the cluster service.


  5. Go to a command prompt.


    1. Go to the directory containing the rebind utility, c:\rebind by default.


    2. Modify the Command window properties so that the screen buffer height = 500.


    3. Execute the rebind utility.


    4. Scroll up and verify that all files were rebound.


  6. Restart the Cluster Service and Network Connections Service.


  7. Close the Command window and delete the c:\rebind directory and contents from this node.


  8. From the node with the Cluster resources go to the Cluster Administrator and move all resources to the node where you have already performed the OS upgrade.


  9. After all of the resources are online again on the node with the new OS installed, pause the cluster service on the node that still needs upgrading.


    10. NOTE: The Microsoft Design-Time Control (DTC) is a resource that is installed and used by SQL 7.0 for database replication. For instructions on how to upgrade this resource to work with a Windows 2000 Server Cluster, view the section titled "Upgrading the MS DTC Resource" in the Microsoft Windows 2000 Release Notes that can be found in the root directory of the Windows 2000 media in the Readme.doc file.

  10. Perform the OS upgrade to the paused node.


  11. Once the upgrade is complete right-click My Computer and choose Manage.


    1. Expand the Services and Applications section.


    2. Select Services.


    3. Stop the Network Connections service, which also stops the cluster service.


  12. Go to a command prompt.


    1. Go to the directory containing the rebind utility, c:\rebind by default.


    2. Modify the Command window properties so that the screen buffer height = 500.


    3. Execute the rebind utility.


    4. Scroll up and verify that all files were rebound.


  13. Restart the Cluster Service and Network Connections Service.


  14. Close the Command window and delete rebind utilities from this node.


  15. Test cluster failover and SQL functionality.



MORE INFORMATION

When performing an upgrade of your operating system, the procedure is:

  1. Remove Microsoft SQL Server clustering, using the Failover Cluster Wizard. Make a note of all the resource names, IP addresses, network names in use and all of the cluster specific information for Microsoft SQL Server before removing Microsoft SQL Server Clustering components.


  2. Perform the operating system upgrade.


  3. Reinstall Microsoft SQL Server clustering by re-running the SQL Cluster Wizard.


REFERENCES

For a step-by-step guide to installing Microsoft SQL Server 7.0 Enterprise Edition on Microsoft Cluster Server (MSCS), see:
http://support.microsoft.com/support/sql/content/70papers/70clstr.asp
For possible changes or updates to the order of installation, refer to:
Q219264 INF: Order of Installation for SQL Server 7.0 Clustering Setup

For a Frequently Asked Questions (FAQ) list for MSCS, see:
http://www.microsoft.com/HWTEST/sysdocsPC98/cluster.htm
http://www.microsoft.com/HWTEST/sysdocs/cluster_deploy.htm

Additional query words: win 2k w2k win2k win2000 2000 clstr clustering uncluster AS Adv EE Ent Ed OS rolling upgrade MDAC

Keywords : kbsetup kbClustServ100 kbClustServ110 kbSQLServ650 kbSQLServ700 kbDSupport
Version : :1.0; winnt:7.0
Platform : winnt
Issue type : kbhowto kbinfo


Last Reviewed: February 1, 2000
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.