Planning your Operations Manager 2007 Upgrade
適用於: Operations Manager 2007 R2, Operations Manager 2007 SP1
Upgrading an installation of Microsoft System Center Operations Manager 2007 is a multistep process. Before you can upgrade your monitoring environment, you need to understand exactly what you are upgrading, the pre-upgrade steps, and the implications for your day-to-day operations.
If your current Operations Manager 2007 installation is at the SP1 (6278) level, you can upgrade directly to the R2 version. The following diagram shows all the supported upgrade paths for Operations Manager 2007.
.gif "2396f496-4313-463c-8f5d-5eecef31fbcb")
If you are currently using Microsoft SQL Server 2005 and want to upgrade to SQL Server 2008, you need to take several steps to ensure that Operations Manager 2007 R2 will work with the newer version of SQL Server. For information, see Upgrading SQL Server 2005 to SQL Server 2008.
The following topics outline the pre-upgrade and upgrade tasks and their orders.
Pre-upgrade Tasks
The following table shows the tasks you need to complete before you upgrade your Operations Manager 2007 installation. This table provides the following information:
Task to complete
Whether this task results in the service being completely unavailable
Whether this task interferes with the service
Risk (to the stability of your data and monitoring environment)
Mitigation (of downtime, interference, or risk)
Step-by-step information for each of the pre-upgrade tasks is available in the Preparing to Upgrade Operations Manager 2007 topic.
| Task | Downtime | Interference | Risk | Mitigation |
|---|---|---|---|---|
Back up database |
No |
No |
Low |
|
Back up encryption key |
No |
No |
Low |
|
Export unsealed management packs |
No |
No |
Low |
|
Remove agents from pending |
No |
No |
Low |
|
Increase space available for data and log files on OperationsManager database. Not required if the database free space available exceeds 50%. Transaction logs should be 50% of the total size of the OperationsManager database |
No |
No |
Low |
|
Remove agents from computers with stand-alone Operations consoles |
No |
No |
Low |
|
Disable notification subscriptions |
No |
No notifications are sent during the upgrade. |
Low |
After upgrade, check for any alerts that were missed. |
Disable Connectors |
Yes. Event states and alerts are not synchronized with EMC Smarts. |
Yes. Event states and alerts are not synchronized with EMC Smarts. |
Low |
Verify with EMC that events and alerts are cached. |
Upgrade agents |
Yes, if you upgrade 300 agents or more at one time |
Yes, agents can be down for approximately and hour and no monitoring information will be gathered during this time. |
Medium |
Do not upgrade more than 299 agents at one time |
Upgrade Order
The following table shows the Operations Manager components to upgrade in the order in which they should be upgraded. This table provides the following information:
Component
Whether upgrading this component results in the service being completely unavailable
Whether upgrading this component interferes with the service
Risk (to the stability of your data and monitoring environment)
Mitigation (of downtime, interference, or risk)
In an environment composed of connected management groups, first upgrade the Operations Manager 2007 components in the top tier and then upgrade the components in bottom tier.
Step-by-step procedures for completing each of the upgrade tasks are available in either the Upgrading from Operations Manager 2007 SP1 to R2 or Operations Manager 2007 SP1 升級指南 topics.
| Component | Downtime | Interference | Risk | Mitigation |
|---|---|---|---|---|
Root management server |
Yes. The SDK and Console will be unavailable. |
Yes. The management group will be unavailable. Data will not be lost—agents and management servers will queue the data. |
Medium |
Read all upgrade and troubleshooting documentation before you start. Make sure you follow the exact instructions. If possible, have a Cluster SME or Operations Manager SME perform this task. |
Reporting (Run on the SSRS server, this will automatically upgrade the data warehouse) |
Yes. Reporting and the data warehouse will be unavailable. |
Yes. All reports will be unavailable, but data will not be lost. Agents and management servers will queue the data until the service is available. |
Medium |
Read all upgrade and troubleshooting documentation before you start. |
Stand-alone Operations consoles |
No |
No |
||
Management servers |
Yes. Agent will not be able to communicate with the management server until after upgrade completes. |
Yes, but no data will be lost. Agents will queue the data. |
Low |
Read all upgrade and troubleshooting documentation before you start. |
Gateway servers |
No |
No |
Low |
Read all upgrade and troubleshooting documentation before you start. |
Agents |
Yes |
Yes. The computer will not be monitored until the upgrade is complete. |
Low |
Read all upgrade and troubleshooting documentation before you start. |
Web console |
No |
No |
Low |
Read all upgrade and troubleshooting documentation before you start. |