Migrate vRO embedded to standalone?

[SteveR123]

Hi, I wonder can anyone point me in the direction of a migration plan/process to move from the embedded vRO included with vRA to a standalone version?

I have successfully configured and completed testing with the vRA solution using the embedded vRO. Most of the blueprints have been configured with workflows etc but I would like to move to a standalone vRO instance as it is the recommended option for production environments.

Any help would be much appreciated as always.

Thanks in advance

Steve

[cdecanini_ · Accepted solution]

You can use the right click / synchronize to copy the embedded Orchestrator content to stand alone vCO.

You need to check you have all the plug-ins you had on the embedded installed on stand alone, install missing plug-ins. For their configuration recent plug-ins use resource elements you can synchronize as well. For older versions exporting the configuration from web configure / import it in stand alone.

[SteveR123]

Thanks for this response. I'm using vCO 6.01 but it sounds like an export of the config and import in the new appliance would be the simplest option? Saves me having to identify every workflow that might be being used?

Is it just a matter of updating the vCO server from within vCAC config or how do my blueprints know about the change?

Thanks again!

[cdecanini_]

The config export / import only handle the vRO & some legacy plug-ins configuration. If you do not have a lot of pl

The workflows / actions / resources / configuration elements are vCO content and these can be exported imported via packages to the file system or synchronized directly between the 2 servers.

The vCO content have unique IDs meaning vRA will find them once you will point vRA to the stand alone vRO server.