Depending on the method of upgrade you choose, you might need additional resources, as explained in the following table. For this comparison, every component is assumed to be installed in High Availability mode with two nodes each, except BMC Atrium Orchestrator which uses 3 nodes. Database instances are for the Enterprise BMC Remedy AR System, Cloud AR System Extensions, BMC Network Automation, and BMC Atrium Web Services.
| | | |
|---|
| Upgrade all BMC Cloud Lifecycle Management components in their current installation environment.
Advantages
- Requires minimal additional hardware and other resources
- You can spread the upgrade across several periods of maintenance time
- There is no need to track data changes during the upgrade process
Disadvantages
Requires a longer period of downtime | | |
| Upgrade BMC Cloud Lifecycle Management components in a separate environment, which becomes the production environment. To see a helpful process flow of a staged environment, see End-to-end-process-for-upgrading-Small-Deployment-staging-strategy.
Advantages
- Minimizes downtime
- The staging environment becomes the production environment, simplifying the go-live process
- You can leverage the upgrade environments of the component products already in place
Disadvantages
- Requires additional hardware
- Requires that you track the data changes and customizations between your production and upgrade environments so you can replicate those changes and customizations in the upgraded environment
| Total = 15 BMC Cloud Lifecycle Management Cloud Database =2 Enterprise-AR = 2 BMC Network Automation = 2 BMC Atrium Web Services = 2 BMC Remedy AR System Midtier = 2 BMC Atrium Orchestrator CDP = 2 BMC Atrium Orchestrator Repository = 3 | Total = 3 BMC Cloud Lifecycle Management Cloud Database = 1 Enterprise-AR = 1 BMC Atrium Web Services = 1 |
Staged-Lite (for High Availability components) | An extension of the staged upgrade, a Staged-Lite upgrade uses one node (a primary node from the production High Availability environment) to form primary nodes of the Staged-Lite environment. The secondary environment becomes the go-live environment after the upgrade has completed. Note that you can opt to create the primary nodes of the Staged-Lite environment anew instead of removing the primary node of production environment, similar to the staged environment method.
Advantages
- Minimizes downtime compared to an in-place upgrade
- Requires fewer additional resources than the full staged upgrade
- The staging environment becomes the production environment, simplifying the go-live process
- You can leverage the upgrade environments of the component products already in place
Disadvantages
- Requires some additional hardware
- Has a longer downtime than a full staged upgrade
- The production environment does not run in a High Availability mode during the upgrade because secondary servers are removed to form the upgrade environment
| Total = 2 When removing the primary node, you need one node each for: BMC Atrium Orchestrator CDP BMC Atrium Orchestrator Repository | Total = 2 When removing the primary node, you need one node each for: BMC Cloud Lifecycle Management Cloud Database Enterprise-AR |
