With vRO 7, the Windows install of Orchestrator doesn't exist anymore. This recipe discusses how to move an existing Windows Orchestrator installation to the appliance.
We need an Orchestrator installed on Windows.
Download the same version of the Orchestrator appliance as you have installed in the Windows version. If needed, upgrade the Windows version to the latest possible one.
There are three ways; using the migration tool, repointing to an external database, or exporting/importing the packages.
There is a migration tool that comes with vRO7 that allows you to pack up your vRO5.5 or 6.x install and deploy it into a vRO7. The migration tool works on Windows and Linux. It collects the configuration, the plugins, as well as their configuration certificates, and licensing into a file. Follow these steps to use the migration tool:
https://[vRO7]:8283/vco-controlcenter/api/server/migration-tool
.migration-cli
into the Orchestrator director, for example, C:Program FilesVMwareInfrastructureOrchestratormigration-cliin
.java -version
. If that works, continue, if not, do the following:set PATH=%PATH%;C:Program FilesVMwareInfrastructureOrchestratorUninstall_vCenter Orchestratoruninstall-jrein
CD
to the directory ..Orchestratormigration-cliin
.vro-migrate.bat export
. There may be errors showing about SLF4J; you can ignore those.(..Orchestrator
) you should now find an orchestrator-config-export-VC55-[date].zip
file.
If you have an external database, things are pretty easy. For using the initial internal database, please see the additional steps in the There's more... section of this recipe.
This is the method that will only pull your packages across. This the only easy method to use when you are transitioning between different databases, such as between MS SQL and PostgreSQL:
Moving from the Windows version of Orchestrator to the appliance version isn't such a big thing. The worst-case scenario is using the packaging transfer. The only really important thing is to use the same version of the Windows Orchestrator as the appliance version. You can download a lot of old versions, including 5.5, from www.vmware.com . If you can't find the same version, upgrade your existing vCenter Orchestrator to one you can download.
After you have transferred the data to the appliance, you need to make sure that everything works correctly, and then you can upgrade to vRO7.
When you just run Orchestrator from your Windows vCenter installation and don't configure an external database, then Orchestrator uses the vCenter database and mixes the Orchestrator tables with the vCenter tables. In order to only export the Orchestrator ones, we will use the MS SQL Server Management Studio (free download from www.microsoft.com called Microsoft SQL Server RTM).
To transfer only the Orchestrator database tables from the vCenter MS-SQL to an external SQL, do the following:
[vcenter]VIM_SQLEXP
with Windows Authentication.VIM_VCDB
) and select Tasks | Export Data.
Now you have the Orchestrator database extracted as an external database. You still need to configure a user and rights. Then proceed with the External database section in this recipe.