Deployment migration is a three-step process that involves migrating infrastructure deployment components, migrating XaaS deployment components, and customizing migrated deployments.
Migrate Infrastructure Deployment Components
VMware Aria Automation provisions Infrastructure components on Cloud providers. Migrating infrastructure components uses the VMware Aria Automation 8 Onboarding feature and consists of two parts:
- Resource Tagging
- Migrating vRealize Automation 7 endpoints creates VMware Aria Automation 8 Cloud Accounts and triggers data collection against the Cloud providers the legacy endpoints represent. Migration uses the source deployments to locate and tag matching resources in VMware Aria Automation 8 with the necessary data to onboard them for VMware Aria Automation 8 management.
- Resource Onboarding
- Migration creates an onboarding plan (one per business group) and a specific onboarding rule to link the relevant tagged resources to the plan and reconstruct the deployment/component hierarchy as it exists vRealize Automation 7. Once the plan is complete, the Migration Assistant uses it to migrate source deployments.
Migrate XaaS Deployment Components
The Migration Assistant manages XaaS components separately from Infrastructure:
- If your deployments only contain XaaS components, the Migration Assistant migrates the deployment and all its XaaS components.
- If your deployment contains both Infrastructure and XaaS components, the Migration Assistant identifies the target deployment that was created during onboarding and moves all the XaaS components to it.
Nota: If attempted, rerunning the onboarding plan created by the Migration Assistant retries onboarding for the infrastructure components only. It does not re-trigger migration for XaaS deployment components or deployment customizations.
Customize Migrated Deployments
This last step fine tunes the migrated deployments by applying these customizations in this order:
- Set the deployment name and description. Unlike vRealize Automation 7, VMware Aria Automation 8 does not allow deployments with identical names. During migration, the Migration Assistant enforces unique names when migrating deployment containers.
- Set the deployment lease.
- Replicate deployment request history in Cloud Assembly.
- Set deployment owner.
VMware Aria Automation 8 Migration Assistant includes these additional deployment considerations.
- During deployment migration, the compute processing consumes project placement quota. Ensure you have enough placement quota before migrating your deployments by navigating to . Each cloud zone is shown with its limits.
- After migrating deployments, the deployments are active in both your source environment and VMware Aria Automation 8 environment. To prevent the machine from accidentally being deleted or destroyed, remove the user from your vRealize Automation 7 business group and modify the deployment's lease to never expire in your source environment.
- If you migrate your source infrastructure and attempt to migrate your deployments, the deployment migration might fail. If your deployment migration fails, rerun the onboarding plan. Learn more about Onboarding Plans.
