CloudHub to CloudHub 2.0 Migration Completion
After completing the VPC upgrade and application migration phases, complete the CloudHub to CloudHub 2.0 migration process and release associated entitlements within the recommended time frame:
Mark Upgrade as Complete
| Marking the upgrade as complete is an irreversible action. This action deletes the original VPC, stopped DLBs, and all CloudHub 1.0 applications marked as upgraded. All traffic then flows through the CloudHub 2.0 private space. |
Marking the upgrade as complete finishes the entire VPC upgrade process. Go to the Upgrade tab and click Mark Upgrade Complete.
After you mark the upgrade complete, CloudHub 2.0 replaces all CloudHub resources and CloudHub assets become immutable. Perform any required changes on CloudHub 2.0.
Entitlements for VPCs, Private Spaces, and Network Connections (VPNs/TGW)
After you complete the VPC upgrade and bring over any existing TGW and VPN network connections, your old and new infrastructure count separately against your usage. Therefore, if your organization uses all purchased quota, your usage can exceed the allowed quota until you move all your applications to CloudHub 2.0 and decommission your old VPC.
Work with your account representative to plan for additional entitlements, and decommission your CloudHub infrastructure (VPCs and associated DLBs) within six months after the upgrade to avoid interruptions when trying to create or edit VPCs, private spaces, or network connections.
| Deleting the upgraded VPC after all applications and their associated DLBs are removed doesn’t affect your CloudHub 2.0 Private Spaces or CloudHub 2.0 applications. |