Migrate VRO configuration into v13

[WestieDave]

We have a VRO instance on v12 currently and have been unable to upgrade it due a configuration for the database user that appears to have broken the standard automated update process from proceeding through to completion. We did log this originally with Support (Case #07908764), but the outcome was not resolved unfortunately.

So, we are therefore looking at building a new v13 instance and ideally would prefer the option to migrate the configuration into this rather than having to rebuild it from scratch.

Has anyone out there done anything similar and/or is there a configuration only migration option available?

Thanks.

[Mildur]

Hi Dave,

We did log this originally with Support (Case #07908764), but the outcome was not resolved unfortunately.

I can see that the case was closed because the upgrade was postponed from your side. If you still experience the discussed issue, I recommend opening a new case.

Regarding the upgrade to v13 and the configuration database:
You cannot deploy a new v13 Orchestrator and connect it directly to the old v12 database. There is also no configuration backup/restore option in the product.

The supported migration path to another machine is documented in our Help Center. For the migration, the new instance must first be installed with the same build as your original VRO server.

After the migration is completed, you can upgrade to v13.

Best,
Fabian

[WestieDave]

Hi Fabian,

The original problem was the upgrade failed with a permission error. The support staff said it was because the account with DB access was not the account used to create the DB (original install). But even though the install was attempted with the original account replaced, it still failed with a different error.

So, if we were to opt for a new v12 instance and then restore backups/config into it, would you then anticipate that the above issue would not carry across?

Thanks.