Prerequisites to planning an upgrade or migration

Prerequisites to planning

For a successful upgrade or migration, review the Deployment-use-cases-and-best-practices-for-Infrastructure-Management before planning and attempting an upgrade or migration. As you review this information, it is imperative that you consider the following:

• The current environment and related functionality
• Existing functionality you expect to maintain during the implementation of Infrastructure Management 11.0
• Existing data that must be moved forward into Infrastructure Management 11.0
• Existing data that is not required to move forward into Infrastructure Management (that is, old data that may not be valuable)
• How you expect the environment to function after the implementation of Infrastructure Management 11.0

Best practices, caveats, and limitations

This section covers basic upgrade and migration methods identified as best practices. The information here does not cover all 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.0 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.0 PATROL Agents, you must fully leverage the new architecture and its capabilities. Plan for this and have the Infrastructure Management 11.0 infrastructure in place as part of the upgrade or migration so that you are not forcing the 11.0 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.0 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.0 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.
• A 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 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 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.0 beta version (pre-GA releases) to the Infrastructure Management 11.0 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.0 PATROL Agents. (However they will work and have been tested.)  Use the new architecture capabilities in Infrastructure Management 11.0. The only exception to this recommendation is if you are upgrading the PATROL Agents first, before implementing the 11.0 Infrastructure Management Server(s) and 11.0 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.0 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.0 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.0.
  • 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.0, you must configure them to send events directly to the 11.0 Integration Service process.
  • Decommission all instances of Bii4P3, Bii4P7, and the Notification Servers after all the PATROL Agents are upgraded to 11.0.
• 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.