If you happen to have an existing vRSLCM 2.x and vIDM 3.3.0 in your environment then you will need the vRealize Easy Installer to migrate your existing vRSLCM 2.x instance to vRSLCM 8.0.
Once your migration to vRSLCM 8.0 is completed you can upgrade your vIDM instance to 3.3.1 since its a requirement before you can install vRealize Automation 8.0 with vRealize Lifecycle Manager 8.0
Again as a reminder vRealize Automation 8.0 is installed, configured, managed and upgraded only through vRealize Suite Lifecycle Manager 8.0
Now as for requirements you will need :
- A new Hostname, IP Address and a DNS record for the new vRSLCM 8.0 appliance that the vRealize Easy Installer will be creating.
- To make sure that the password for the sshuser on the existing vIDM appliance is not expired.
- To enable root access for SSH on the existing vIDM appliance following VMware KB 2047626
- To Download the install and upgrade binaries for vRealize Suite 2019
- To Make sure you have enough storage on the new vRSLCM 8.0 appliance.
Migration Workflow
Please note that the installation process in the video after hitting submit is fast forwarded.
NOTE (vIDM Upgrade Support ) :
- Green-field vRealize Suite Lifecycle Manager 8.0 supports only 3.3.1 version of VMware Identity Manager to be installed or imported.
- Older versions (2.9.2, 3.2.0, 3.2.0.1 & 3.3.0) of VMware Identity Manager will be supported only for existing vRealize Suite Lifecycle Manager instances that are being migrated to vRealize Suite Lifecycle Manager 8.0.
- Upgrade support from older VMware Identity Manger to latest is only available if they conform to vRealize Suite Lifecycle Manager supported form-factor.
- Versions prior to vRealize Suite Lifecycle Manager 8.0 allowed only single instance of VMware Identity Manager to be deployed with embedded connector and embedded postgresql database.
- Upgrade for VMware Identity Manager within vRealize Suite Lifecycle Manager 8.0 to latest versions will only be supported if it conforms to the above mentioned form-factor.
Else the upgrade has to be performed outside vRealize Suite Lifecycle Manager and Once upgraded, it can any-time be re-imported by triggering Inventory Sync in vRealize Suite Lifecycle Manager 8.0
The End, Eh!
Helpful Links You Might Need
Resetting the admin@localhost password in vRealize Suite Lifecycle Manager
VMwareLab 
What to do with old vRSLCM 2.1 appliance? Remove it from environment or keep it?
LikeLike
I would remove it ofcourse as there is no need for it
LikeLike
Thanks, I am asking because its not so clear in documentation and its not part of process of migration, like power off and remove old appliance. At least power off will be good.
LikeLike
Of course yes I had mine powered off for a few days Until I made sure everything is working as expected and then when Ahead and deleted it
LikeLike
Hello Do you find that it is better to do a clean install instead of a migration or upgrade?
LikeLike
Hi Tony interesting question .. While both approaches work it really depends on the number of environments you have which you would have to import individually in addition to having to configure VIDM in the new instance of LCM 8.0 . migration is faster that way even though we are still deploying a new appliance since its side by side migration but again new installation is much cleaner even though it will take you more time as you onboard your existing environments to the new LCM instance. i did the migration and for me its working with no issues at the moment in using LCM 8.0 .
another thing is with the migration that gets you to think about that you might as well do a clean instance since the migration also doesn’t migrate any of the product binaries or the content they you may have already captured under content management .
the good thing is at end of the day you have options . hope this help!
LikeLike
One more question… Will migration or upgrade replace all the windows servers that were part of the old build? So we have a sql server, IIS webserver, and agent server as part of current build.
LikeLike
not sure i follow.are your talking about vRA 7.x to vRA 8.x migration ? if not can you please elaborate
LikeLike
It is a 7.x to 8.x migration. Our 7.x LCM / VRA environment has a Windows: MS SQL db, a IIS webserver, a agent server, but I have decided to build new from scratch since its not completely in Production. Thanks!!
LikeLike
For vRA 7.x to vRA 8.x migration, that will be supported in vRA 8.1 where you will have access to a migration tool that Will allow to do a side by side migration . Currently the vRA 8 architecture doesn’t use MS SQL or any of the components/services that ran perviously on windows . vRA 8 today consist of 1 or 3 appliances running K8S. Hope this help
LikeLike
Hello,
Will this work for environments using clustered vIDM? Just to give you a quick overview. I have an environment with LCM 2.1 connected to a vIDM 3.2.0 cluster (3 nodes) with an external SQL database. Will the migration work if we’re talking about a vIDM cluster going into 3.3.1? From my understanding, and I’m quite possibly wrong, the supported path refers to a single node vIDM with embedded postgres db.
Thanks!
LikeLike
upgrade for VMware Identity Manager within vRealize Suite Lifecycle Manager 8.0 to latest versions will only be supported if it conforms to the above mentioned form-factor. and the fact you have a vIDM cluster with an external SQL makes it a none-form-factor.
so based on that the upgrade of your vIDM will have to be done outside of LCM first. then it can be imported to LCM.
LikeLike