cowhowUTA
Enthusiast
Enthusiast

Migration Method

I am standing up a new vRA 7.6 stack to replace a battered and bruised vRA 7.4 stack.  The 7.4 deployment is a distributed deployment with three appliances and two each of Agent, DEM, and IaaS servers along with an external MS SQL server.  The new 7.6 deployment is a minimal deployment with a single appliance, single DEM/Agent/IaaS web server, and external SQL server. 

The issue is since the old environment is unstable and prone to randomly breaking I'm reluctant to do an automated migration of content and configuration.  In light of that, is performing a manual item at a time migration the only option?  Would there be a specific order to do this?

Thanks for any advice you can give.

Tags (1)
0 Kudos
4 Replies
daphnissov
Immortal
Immortal

What types of things would you want to migrate? Unless you like pain, avoid at all costs moving deployments over.

0 Kudos
cowhowUTA
Enthusiast
Enthusiast

We have vRO workflows configured as well as custom forms in addition to catalogs and such.  I know the forms are an easy export.  I'd love to use the built in migration tool, but I'm unsure of the results I'd get.

What's up with the deployments?  We have a fair number that would need importing.

0 Kudos
daphnissov
Immortal
Immortal

vRO artifacts are pretty easy, but you also need any EBS subscriptions as applicable. Custom forms, too, but there are APIs for that. I have not used that vRA migration tool, but when it comes to deployments those aren't coming over just like they were in 7.4. When you remove deployments from management and import them, it's a 1:1 mapping of machine to deployment. So it's a real ugly process.

0 Kudos
cowhowUTA
Enthusiast
Enthusiast

Yikes.  Yeah,k that sounds like a PITA for sure.  Thanks for the heads up.

0 Kudos