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

.Net CLR version
If you are unable to create an identical test machine, we recommend that you create
a scaled-down version of your production machine and test any upgrades on it. Be
sure to scale down the workload as well. Although a scaled-down machine deviates
from the real environment, it will enable you to verify that the dependency among
components does not affect SQL server availability after the upgrade.
3. Back up the current machine state
Before performing the upgrade, you should back up the current state of the production
machine. The backup should include the general machine-wide state and the SQL
instance-specific state. The machine-wide state includes the following:
• Registry settings
• Machine name, network settings, accounts
• Shared SQL files and DLL
• Operating system
The SQL instance-specific state includes the following:
• Data (master database, model database, user database)
• Logins
• DTS packages
Before starting the upgrade, verify that you can restore the backup onto your test
machine.
4. Notify users of upgrade start
For a planned upgrade, users should anticipate application down time and prepare
for it. However, notifying users that the upgrade is starting shows that the process is
under control and that the plan is being executed properly.
5. Apply the upgrade
Upgrade the production server as described later in this chapter. Upgrade procedures
are provided for SQL instance upgrades and general machine upgrades such as
operating system service packs.
HP PolyServe Software for Microsoft SQL Server 4.1 administration guide 153