Determining whether to upgrade or migrate from an earlier version

You need to decide carefully whether to upgrade the existing TrueSight Infrastructure Management Server(s) or to migrate them to the latest version of TrueSight Infrastructure Management. The following sections explain the upgrade and migrate planning considerations, process, their advantages and disadvantages that help you to take a suitable decision about migration or upgrade process.

Planning considerations for an upgrade or migration

Consider the following when you plan to upgrade or migrate:

  • Before you migrate or upgrade, review the Assisted Migration Offering (AMIGO) checklist. Open a support case to review your plans and get help from BMC upgrade experts through the AMIGO program. Upgrade or migrate only after the experts confirm that your environment is ready. For more information about the AMIGO program, see AMIGO checklist for TrueSight Operations Management .
  • List the current versions and configurations of the servers, and their associated functionality.
  • List the set of functions that you expect to support during the upgrade or migration process.
  • Identify the data that must be retained and copied after you migrate or upgrade.
  • Identify the data that need not be retained after you migrate or upgrade.
  • How you expect the environment to function after the implementation of Infrastructure Management   11.3.01
  • In all scenarios, BMC recommends that you install the latest version of Integration Services. This means you must allocate hardware resources for the new Integration Services, regardless of whether you upgrade or migrate.
  • Review the Deployment use cases and best practices for Infrastructure Management before planning an upgrade or migration. For details, see  Deployment use cases and best practices for Infrastructure Management .

Important Information

There are significant improvements in the architecture, monitoring configuration and administration capabilities in  Infrastructure Management 11.3.01 . To facilitate these improvements, you must upgrade the BMC PATROL Agent for all scenarios. The PATROL Agent upgrade and change in architecture imparts a significant impact to the overall upgrade/migration processes. BMC has designed a lot of backward compatibility in the solution components where possible to help ease the upgrade/migration processes. However, it is imperative that you fully understand Infrastructure Management 11.3.01 and work though the upgrade/migration processes in a development and QA environment and document the plan for your environment. Every detail must be covered including validation of configuration policies for each KM. For more information, see Presentation Server, Infrastructure Management, and PATROL Agent compatibility matrices and List of Monitoring Solutions and KMs in Infrastructure Management.

Upgrade process

Directly upgrade each TrueSight Infrastructure Management Server to the latest version

  1. Upgrade the existing TrueSight Infrastructure Management Servers and Integration Service nodes by running the upgrade installer and configure them.
  2. Upgrade the existing PATROL Agent nodes nodes by running the upgrade installer and configure them so that they point to the upgraded Infrastructure Management server and Integration Service node.

For more information about the versions from which upgrade is supported, see Supported upgrade paths for Infrastructure Management.

Upgrade pros and cons

The following table identifies the pros and cons of upgrading to the latest version:

ProsCons
  • You do not have to run parallel environments as you do with a migration. Assuming proper sizing, the server(s) already provisioned for the older environment can be leveraged for 11.3.01.
  • You do not have to reconfigure all the settings. 
    NOTE: You must review all the settings. Some settings such as heap will have to be reset. Policies need to be re-created, edited, or created for the first time.

  • After upgrading the TrueSight Infrastructure Management servers, the earlier Integration Service nodes, adapters, and older PATROL Agents continue to function as they did in the earlier TrueSight Infrastructure Management server.

  • Historical data is maintained in the new system because the old system becomes the new system.

  • You can initially upgrade only the server and install new Integration Service nodes, followed by upgrading the agents over time. The TrueSight Infrastructure Management server 11.3.01 interoperates with the older Integration Services and older data flow model.

  • You can move PATROL Agents in logical groups to a new 11.3.01 Integration Service node as the agents are upgraded to a compatible version while handling data for all versions in the new TrueSight Infrastructure Management servers.

  • Additional hardware and resources are generally not required to support an upgrade. However, you must review Infrastructure Management scalability as you plan the upgrade, and allocate enough drive space for the upgrade to run.

  • Incorrect or otherwise undesired configuration will be carried forward to the new 11.3.01 system from the old system.
  • You may potentially experience on-going issues with data gaps in the new 11.3.01 system until all the PATROL Agents are upgraded and communicate through the 9.6 Integration Services.
  • If you are starting with Infrastructure Management 8.5, you must first upgrade to either Infrastructure Management 9.0 SP1 or at least to Infrastructure Management 8.6 SP3 prior to upgrading to 11.0.
  • You must ensure that the latest Service Pack is applied to the current TrueSight Infrastructure Management server(s) prior to the upgrade.
  • Users may experience differences in functionality and content in the same UI because variations may exist depending on the agent versions from which the data is sourced. The following are some examples (not a complete list):
    • Annotated data will be available only for attributes collected by the 9.5 agents. Annotated data for the same attributes will not be available where collected by older agents.
    • There will be differences in the granularity of trended data for attributes. Data from older agents will be less granular, generally one data point every five minutes. Data from the 9.5 agents can be granular to one minute.
    • Some attributes continuing to be collected by older agents may have data gaps while the same attributes collected by the 9.5 agents may not have data gaps.
    • Certain new functionality in TrueSight Infrastructure Management 11.3.01 will not be available for data collected by older agents.

Data differences is be retained for historical data after the agents are upgraded. These differences exist in the same Operations Console and it will not be readily apparent to users why the differences occur. This may result in confusion and excessive support calls unless the users are well trained to be aware of the differences.

Upgrade risks

The following are risks related to upgrades from all versions except where otherwise specified:

  • Poor perception of the new solution. The significant change between older versions and Infrastructure Management 9.6 results in a variation of the functionality, capability, and behavior which is likely to cause confusion for users. Users may also perceive issues in TrueSight Infrastructure Management 11.3.01 that are actually related to data collected before the upgrade and/or before upgrading agents.
  • Improper decisions. Visualization might be confusing to users considering old versions of KMs compared to 11.3.01 KM versions being displayed, as upgraded and new TrueSight Infrastructure Management 11.3.01 policy-controlled agents join the TrueSight Infrastructure Management 11.3.01. This can result in improper decisions.
  • There might be altered event behavior associated with event management cell Knowledge Base configuration differences that were not accounted for.
  • Downtime associated with upgrading the TrueSight Infrastructure Management server(s), especially if upgrading from version 8.5, due to multiple iterations in the upgrade process.

Migration process

Migrate process migrates from the old TrueSight Infrastructure Management Servers and install the latest version servers and Integration Services, upgrading the agents, transferring the agents to the new server(s), and then decommissioning the old servers.

  1. Install and configure the latest version of TrueSight Infrastructure Management Servers and Integration Service nodes.
  2. Configure the PATROL Agent to connect to the new TrueSight Infrastructure Management environment when you upgrade the agents.

Migration pros and cons

The following table identifies the pros and cons of migrating to the latest version:

ProsCons
  • Potentially incorrect or otherwise undesired configuration is not carried forward in the new TrueSight Infrastructure Management system from the old system.

  • There are no historical or on-going issues with data gaps in the new TrueSight Infrastructure Management system.

  • A migration eliminates any user confusion related to functionality and data differences between data collected from older agents versus newer PATROL Agents all being displayed in the same UI. It is simpler to keep like functionality segregated between systems; that is, TrueSight Infrastructure Management server 11.3.01 with Integration Services 11.3.01 and newer PATROL Agents, while keeping the earlier servers with earlier Integration Services and earlier PATROL Agents. 

  • Provides a platform for a complete and clean rework of monitoring configuration without the worry of older data collection configuration challenges having to be handled going forward.

  • You can avoid “intermediate” upgrades. If the existing TrueSight Infrastructure Management server(s) are of a version that is not supported for a direct upgrade to the latest version, you have to upgrade them first to an upgradable version. This mainly applies to version 8.6; however, you also need to consider service packs for versions 9.0, 9.5, and 9.6.

  • There is little or no downtime associated with a migration.

  • You have to run parallel environments for a period of time until the migration is complete.

  • Historical data is not maintained in the new system. However, it is available in the old system until the old system is decommissioned.

  • There is work involved in defining configuration settings including user preferences, graph views, and so on in the new TrueSight Infrastructure Management server(s). An upgrade preserves those settings.

  • The migration method involves installing new TrueSight Infrastructure Management server(s), not upgrading the old TrueSight Infrastructure Management server(s). The ability to use earlier Integration Service nodes (versions 9.5 and 9.0 with the appropriate levels of service packs) is not supported out-of-the-box with a fresh, new installation of the TrueSight Infrastructure Management server. The earlier Integration Services are supported out-of-the-box only when the TrueSight Infrastructure Management server is upgraded. (With custom configuration after installation, older Integration Services can be supported in a TrueSight Infrastructure Management 11.3.01 environment. However, BMC does not recommend this in a migration unless you are forced to use older PATROL Agents that require older Integration Services for an extended period of time.)

  • You must have the additional hardware and resources required for TrueSight Infrastructure Management 11.3.01 to support a migration.

Migration risks

The following are risks identified with migrating instead of upgrading:

  • The requirement to run parallel systems can result in confusion due to users having to view trends in multiple systems.
  • A migration can extend the time required to get to TrueSight Infrastructure Management version 11.3.01. A complete migration requires complete configuration of the 11.3.01 environment including TrueSight Infrastructure Management policies, and upgrading PATROL Agents before they can be integrated in the new environment. This can extend the time required to complete the project so that all agents report into the new 11.3.01 environment. 

Note

This risk exists for all scenarios when you consider “full ITrueSight Infrastructure Management 11.3.01 functionality”. However, with an upgrade, existing older PATROL Agents report into TrueSight Infrastructure Management 11.3.01 immediately after the upgrade, even though “full TrueSight Infrastructure Management 11.3.01 functionality” is not in place for them.

Migration versus upgrade decision chart

The following chart provides a general framework around deciding whether to migrate or upgrade. Not all factors that drive this decision can be anticipated; therefore, a particular environment and its specific requirements may necessitate some deviation in the decision process.

Answer each question below with either Yes or No. Do not answer with both Yes and No. In general, the Upgrade or Migrate column with the most Yes answers is the best choice, assuming there are no “show stopper” items that are not answered in the respective column.


Requirement

Upgrade

Migrate

Are hardware resources available for a separate, new TrueSight Infrastructure Management Server?

No

Yes

Do you have to maintain the old and new data in one system and one UI?

Yes

No

Are you changing the database platform (SAP SQL Anywhere to Oracle or Oracle to SAP SQL Anywhere)?

No

Yes

Is it acceptable to carry old data and configuration forward in the new system?

Yes

No

Will users be able to manage differences in functionality in a single UI depending on the source agent versions?

No

Yes

If an upgrade requires phased upgrades, can your environment afford the required down time?

Yes

No

Will users be able to handle workflow and visualization in multiple separate parallel systems until the project is complete?

No

Yes

Is it a requirement to maintain current monitoring configuration including graphs, views, and so on without having to re-enter anything?

Yes

No

Is zero down time a major issue?

No

Yes

Are service models implemented in the current system and integrated with BMC IT Service Management and monitoring such that leveraging a separate system for Probable Cause Analysis is technically unacceptable? 

Yes

No

Is it acceptable to manage separate parallel environments?

No

Yes

Is it a requirement to maintain historical data in the same system with new data?

Yes

No

Does the monitoring data collection and configuration need a complete rework in order to be valuable?  (In other words, does the current environment provide little value?)

No

Yes

Is project timing a major issue making it difficult or impossible to complete a migration, keeping in mind that a lot of reconfiguration may be required?

Yes

No

Best practices, caveats, and limitations

This section covers basic upgrade and migration methods identified as best practices. The information here does not cover all the Infrastructure Management components. For example, BMC TrueSight Operations Management Reporting is not included. This section also does not include all possible technical options; however, major options are covered. Although Infrastructure Management is very flexible and can be implemented in multiple ways, this section follows best practice recommendations. 

The following lists contains best practices to follow when upgrading to Infrastructure Management.

  • Do not upgrade all agents en masse. Work in blocks or groups of agents.
  • Do not try to use Bii4Px with 9.6 PATROL Agents for extended periods of time.
  • Do not use Bii4Px with Notification Servers. Instead, implement the 11.3.01 PATROL Agent on the Notification Servers and leverage the new architecture until you are able to upgrade the entire environment. This assumes that you are already using Notification Servers.
  • As you upgrade to 11.3.01 PATROL Agents, you must fully leverage the new architecture and its capabilities. Plan for this and have the Infrastructure Management 11.3.01 infrastructure in place as part of the upgrade or migration so that you are not forcing the 11.3.01 PATROL Agents to function in the older architecture. 
  • If the scheduled down time is configured for auto-synchronized devices that are monitored by agents prior to 9.5, or for groups having auto-synchronized instances, data is not recorded during the down time period for the associated auto-synchronized instances. If the scheduled down time is in the future and the upgrade is completed before the scheduled down time period starts (including upgrading the PATROL Agents), then instances monitored by the related PATROL Agents are converted to streamed instances and the scheduled down time will not be applicable to the related devices anymore.
  • You must manually create corresponding blackouts for scheduled down time settings that were previously created manually in the older system.
  • You must manually take a backup of the custom Cell before the TrueSight Infrastructure Management server upgrade process starts. This avoids data loss when a new Cell is created during the upgrade process. 
  • If Infrastructure Management is integrated with BMC Remedy IT Service Management Change Management, the Change Management settings need to be deleted and recreated in IT Service Management so that the corresponding blackouts are created automatically in Infrastructure Management.
  • An 11.3.01 Integration Service can be used with non-PATROL data adapters and native collectors. Adapters used to collect non-PATROL data are included in Infrastructure Management and supported with 11.3.01 Integration Services. These include BMC Portal and other data adapters.
  • Be sure to review Network ports for Infrastructure Management. Some ports are no longer used or are used differently due to architecture changes.
  • TrueSight Infrastructure Management server upgrade fails to install if extra event management components have been installed on the existing Infrastructure Management Server. No extra event management cells, adapters or any other non TrueSight Infrastructure Management server components must be installed on a Infrastructure Management Server other than a PATROL Agent for local/external monitoring.
  • The TrueSight Infrastructure Management server upgrade process writes a lot of data and creates directories in the existing TrueSight Infrastructure Management server installation directory. Make sure you allocate extra disk space for the upgrade. Allocate at least the amount required for a new installation.
  • On Linux systems, if the existing Infrastructure Management Server installation directory is a mount point, you may have problems associated with the upgrade process when attempting to rename directories. Allocate a directory for the existing environment that is not a mount point.
  • Ensure that all host names and host aliases are resolved in DNS before attempting an upgrade or a migration. In some environments where the existing event management cell HA configuration leverages virtual host names instead of physical host names, the installer does not recognize the virtual or alias host names.
  • You cannot upgrade the Infrastructure Management 11.3.01 beta version (pre-GA releases) to the Infrastructure Management 11.3.01 GA version. You must install a new server and Integration Service nodes, or upgrade an older release that is supported with upgrades.
  • Do not attempt to connect PATROL Agents prior to 9.5 to an Integration Service.
  • If possible, avoid using Bii4P3 or Bii4P7 with 11.3.01 PATROL Agents. (However they will work and have been tested.)  Use the new architecture capabilities in Infrastructure Management 11.3.01. The only exception to this recommendation is if you are upgrading the PATROL Agents first, before implementing the 11.3.01 Infrastructure Management Server(s) and 11.3.01 Integration Service host(s). Even in that scenario, it is better to forward events directly to an event management cell and avoid using Bii4P3 or Bii4P7 if possible.
  • You must move to the 11.3.01 architecture and processes as completely as possible and avoid a mix-match of old/new technology. Avoid configuring the new technology to support the old technology; otherwise you will not move away from the old and realize the benefits of the new. There may be some overlap during the upgrade and migration processes, but this must be reduced as much as possible. Note the following.
    • A PATROL Agent prior to version 9.5 cannot send events directly to the 11.3.01 Integration Service process.
    • A PATROL Agent prior to version 9.0 cannot send events directly to an event management cell. If you have 9.0 agents, you must already be sending events to a cell until you upgrade the agents to 11.3.01.
    • If you have PATROL Agents prior to version 9.0 and you are not using a PATROL Notification Server, continue leveraging Bii4Px and the first tier cell that the events flow into, until you upgrade the agents to 9.6.
    • As you upgrade all the PATROL Agents to 11.3.01, you must configure them to send events directly to the 11.3.01 Integration Service process.
    • Decommission all instances of Bii4P3, Bii4P7, and the Notification Servers after all the PATROL Agents are upgraded to 11.3.01.
  • You cannot upgrade a Infrastructure Management Server with a SAP SQL Anywhere database to a Infrastructure Management Server with an Oracle database or the other way round. There is also no way to migrate a Infrastructure Management SAP SQL Anywhere database to an Oracle instance or the other way around.
  • Upgrading an HA-configured Infrastructure Management Server environment requires a two-part upgrade: one on the primary node and the other on the secondary node.

Where to go from here

You can choose to upgrade or migrate TrueSight Infrastructure Management after reviewing the upgrade and migrate considerations:

Was this page helpful? Yes No Submitting... Thank you

Comments