- Pivotal Cloud Foundry® all versions
- vSphere hardware or clusters all versions
At some point throughout the course of operating a Pivotal Cloud Foundry platform, the need will arise to upgrade the underlying vSphere hardware or clusters. Upgrades like this come in many forms, but here are a few common examples:
- Adding a new vSphere cluster and availability zone in Ops Manager.
- Migrating from one cluster of ESXi servers to a completely different cluster of ESXi servers.
- Migrating from one vCenter server to a new vCenter server.
- Moving from one set of availability zones in Ops Manager to a new set of availability zones.
- Migrating virtual or physical networks, IP or other network changes.
- Renaming vSphere Datacenter, Cluster or Resource Pools
- Grouping Clusters in vSphere into folders
- Moving VMs from a resource pool to a top-level cluster or from a top-level cluster to a resource pool
It is important to understand that planning and executing migrations of this nature requires careful planning to avoid downtime or data loss.
Migrations of this scope and nature need to be carefully planned and executed to avoid causing problems or outages. Migrations may also need to be performed during off hours or during the scheduled maintenance window as it may not be possible to perform such migrations without downtime. Every migration, environment, and situation are different from one another, though.
Customers who need to perform migrations or changes to the underlying IaaS should contact their account representative, platform architect, and Pivotal Support before the migration so that Pivotal can engage and assist with planning the migration.
Planning and executing a migration requires consideration of several factors depending on the nature of the change and the underlying IaaS. Pivotal strongly recommends that you engage your Platform Architect for the system review in all such cases to ensure a successful migration and to avoid extended downtime or data loss.