4.1.0 HP PolyServe Software for Microsoft SQL Server administration guide (T5392-96074, October 2010)

Maintenance mode is required for update operations
Before installing a service pack or hotfix on a virtual SQL or SSAS instance, the
Virtual SQL Server (or Virtual SSAS) associated with the instance must be moved to
maintenance mode.
NOTE:
Be sure to put any virtualized SQL or SSAS instances into maintenance mode before
attempting to patch the active node. You can patch any passive backup nodes without
putting the Virtual SQL or SSAS Server into maintenance mode.
For SQL updates, if another Virtual SQL Server (with different instances) is active on
the node and is enabled for MSDTC, you will also need to move that Virtual SQL
Server to maintenance mode before you install the service pack or hotfix on the
instance that you are attempting to patch. If the MSDTC-enabled Virtual SQL Server
is not in maintenance mode, the service pack installation will fail.
Update considerations for SQL Server 2008
Extract zip files
Some hotfixes are provided in zip files. Be sure to extract the contacts of the file and
review the README before starting the installation.
Service pack and hotfix names
The installation procedure expects the names of SQL Server service packs and hotfixes
to follow the standardized naming schema defined in the following Microsoft
Knowledge Base article.
http://support.microsoft.com/kb/822499
The installation will fail if the name of a service pack or hotfix has been changed
and it no longer matches the schema.
Use of a hidden administrative share
During its initialization phase, the SQL Server 2008 setup program uses a hidden
administrative share as the location for a tempfolder. If the setup program attempts
Update SQL Server instances62