Upgrade sequence
When you launch the BMC Cloud Lifecycle Management installer to upgrade the products in the solution, host names are displayed for each product.
The sequences in the tables include products from both the Control Tier and Workload Tier. In an upgrade scenario, the emphasis is more on the upgrade order instead of on available products within a tier.
Before you begin
Before you start upgrading the products, make sure that you review the
attachment (Microsoft Excel spreadsheet). Because not all products are available in each of the deployment types, the upgrade order that you must follow depends on the deployment type that you chose.Upgrade sequence for Single VM RDS
You can upgrade the Single VM RDS Linux 3.1 SP1 deployment to 4.0. This procedure is fully documented end-to-end at Upgrading-Small-Deployment-In-Place-method.
Upgrade sequence for POC deployments
The POC deployment model is no longer supported in version 4.0; POC is replaced by the single VM Compact Deployment model. To upgrade your 3.x POC deployment, follow the upgrade sequence for small, medium, and large deployments.
Upgrade sequence for Small, Medium, and Large deployments
The upgrade order listed in the following table applies to the Small, Medium, and Large deployment types. To learn more about which deployment type works best for your requirements, see Deployment architecture. This sequence applies to all upgrade methods: in-place, staged, and staged-lite.
Sequence | Product | Order of tasks for upgrade |
---|---|---|
1 | BMC Server Automation – File Server | No manual tasks required for this product. Directly upgrade to 4.0 using the installer planner. |
2 | BMC Server Automation – Application Server & Console |
|
3 | BMC Server Automation – (MAS) |
|
4 | (Optional) PXE server |
|
5 | (Optional) BMC Server Automation – Advanced Repeater | No manual tasks required for this product. Directly upgrade to 4.0 using the installer planner. |
6 | BMC Atrium Orchestrator – Configuration Distribution Peer | Perform the following steps for BMC Atrium Orchestrator – Configuration Distribution Peer when upgrading BMC Cloud Lifecycle Management:
|
7 | Atrium Orchestrator – Configuration Distribution Peer for High Availability (HA) |
|
8 | BMC AR System & BMC Remedy IT Service Management Suite – Primary (Enterprise-AR) |
|
9 | BMC Remedy AR System Cloud Database – Primary (Cloud-AR) |
|
10 | BMC AR System & BMC Remedy IT Service Management Suite – Secondary |
|
11 | BMC Remedy AR System Cloud Database – Secondary |
|
12 | BMC Remedy Mid Tier | No manual tasks required for this product. Directly upgrade to 4.0 using the installer planner.. |
13 | BMC Atrium Core – Web Registry Components | No manual tasks required for this product. Directly upgrade to 4.0 using the installer planner.. |
14 | BMC Network Automation | Note: Upgrading the BMC Network Automation server in an HA environment is not supported by the installer planner. Therefore, you must perform the upgrade using the BMC Network Automation product installer.
|
15 | (Optional) BMC Network Automation – Device Agent | No manual tasks required for this product. Directly upgrade to 4.0 using the installer planner. |
16 | Cloud Database Extensions | No manual tasks required for this product. Directly upgrade to 4.0 using the installer planner. |
17 | Cloud Platform Manager | If you have installed Cloud Platform Manager in an HA environment, you need to upgrade only the Cloud Platform Manager – Primary server. |
18 | Cloud Portal AR Extensions – Primary | Upgrade the following Cloud Portal AR Extensions components in this order using the installer planner:
|
19 | Cloud Portal AR Extensions – Secondary | No manual tasks required for this product. Directly upgrade to 4.0 using the installer planner. |
Where to go next