Hi all, welcome to a new vRA Post! This time we will discuss about new functionality added to vRA in vRA 8.2 version. This time is vRA migration!
So, let’s start!
Migration Assistant Configuration
First step in the migration process is the configuration of the vRA 7.5/7.6 source environment.
To configure this we must go to Migration Assistant > Source Instances
There we will configure the vRA7 source environment, as we can see in the following picture.
After the validation we can choose what tenants are we going to asses and migrate, we have the option to asses also the embedded vRO environment.
Well, this is all for the source configuration. At the end of the configuration a assessment will start for the selected tenants.
We will see here that the focus for the migration is based on the Business Groups we have in the source environment. In my case I have for the tenant “New Tenant”, a Business Group called “NewTenant” (I know, this is not a creative name 😊 )
After the assessment ends we can see the results clicking in the Business Group
In my case, as we can see, I’m ready to migrate but I have some warnings. Let’s start digging.
The warnings that appear are related to Blueprints I have in my source environment…
If we go deeper, we can see that I have two Blueprints:
One of the Blueprints is the one having the warnings
So, lets analyze the results
We can see here that the warning I’m having is because a custom property I have in my BP (VirtualMachine.Admin.ThinProvision), this warning is because in vRA 8 this custom property doesn’t work to force the thin provision property when cloning VMs. Instead of using this property I will need to use provisioningType property.
As all is OK we can proceed with the migration. To continue we will select the Business Group to migrate and click Migrate
After choosing to reassess the business group previous to the migration, the migration process will start
After some minutes, the migration will finish and we can now see each migrated object.
The following vRA objects were migrated
- Business Groups
Regarding Blueprints, we can see that my two Blueprints were migrated with their properties including the Lease Policy config. One note here, we can see here the name changed in the product
- Blueprint (vRA 7) >> Cloud Template (vRA 8)
Regarding Business Groups, the following object are created in vRA 8
- Project. This is where the Business Group Configuration are migrated.
- Content Entitlement Blueprint. Here we can see our migrated Blueprints, with their properties like Deployment limits.
- Content Source Blueprint. This step is necessary for all Blueprints and is the one that allows us to share the Blueprint to be used by the Project.
In this point we can see that a vSphere endpoint is created in vRA 8. We can see another name changed here
- Endpoint (vRA 7 ) >> Cloud Account (vRA 8 )
Regarding reservation, all components that belongs to the reservations are migrated. The following object are created as part of the migration process:
- Cloud Zone
- IP Range
- Network Profile
- Storage Profile
But where are my deployments?? Well, this is a different migration step that I will cover in another entry! So… stay tuned 😊