4.0.0 HP PolyServe Software for Microsoft SQL Server Administration Guide (T5392-96056, March 2010)

Upgrade procedure
To perform the upgrade, complete these steps:
1. Move the Virtual SQL Server (VSQL) associated with the instance to maintenance mode. Select
the Virtual SQL Server on the PolyServe Management Console, right-click, and select Maintain.
2. If the instance being upgraded is disabled on any backup nodes, select the instance on the
PolyServe Management Console, right-click, and select Enable before proceeding.
3. Upgrade the SQL instance on the backup node.
4. Repeat steps 2 and 3 for each backup Virtual SQL Instance.
5. Upgrade the instance on the primary node.
6. Return the Virtual SQL Server to operational mode. Select the Virtual SQL Server associated with
the instance on the PolyServe Management Console, right-click, and select Operate.
Multiple instance upgrades
You may want to perform a multiple-instance upgrade on consolidated servers that hold many instances.
These servers typically use one of the configurations described earlier and the same general procedures
can be used. However, you should be aware of the following:
• A manual upgrade will probably necessitate a reboot, which will affect all of the instances on the
server. To avoid this, we recommend that you use an unattended install, which does not require
a reboot.
• Because the instances have a shared location, during the upgrade there can be more than one
version of SQL Server on the machine.
General machine upgrades
This procedure applies to the following types of upgrades:
• Operating system, include service packs and hotfixes
• Firmware
• Third-party software
These upgrades may require a reboot; however, you can minimize machine downtime by perform a
rolling upgrade. In this scenario, you will need to fail over the Virtual SQL Server from the primary
node, and then upgrade that node while the Virtual SQL Server resides on the backup node. Clients
will see a small downtime from two failovers (a failover to the backup node before the upgrade, and
a failback after the upgrade) instead of a full upgrade downtime as in a non-clustered environment.
The procedure first upgrades the backup node and then upgrades the primary.
Upgrade the Backup Node
Complete these steps:
1. Ensure that all virtual SQL servers are active on their primary nodes.
2. Disable hosting on the backup node.
3. Apply the upgrade (for example, a service pack).
4. Enable hosting on the backup node.
Upgrade production SQL Servers132