Due to some ... we have a vRA 7.6 environment that was deleted and only the primary vRA VA can now be restored.
I only need 1 thing, save all workflows and actions from vRO.
I have repaired the vRA cluster (removed secondary node), changed hostname from the loadbalancer-name to the va-name, repaired messaging (rabbitmq), xeonon is running, orchestrator seems to be running (in the vami and with service vco-server status).
Under the Services tab, only 4 services become registered:
component-registry
licensing-service
plugin-service
sts-service
All others stay without any status.
When I try to connect to vRO, the vco control center at 8283, or anything like that, it fails.
Does anyone have an idea how I can get the vRO content out of this one VA?
Finally I got vRO up.
It turned out that the SSL certificate was expired in the time between power-down and the restore, which caused another chalenge that I did not expect.
Steps followed:
- replace loadbalancer ip in DNS to point directly to the only vra va
- remove secondary node from vra cluster
- repair rabbit-mq
- replace vra va certificate
- make vRO trust the new certificate again
After that, vRO came up and I was able to export all.
Most services are fixed now, but the most important vco is still not registered. (while service vco-server status says running) In the vco/app-server/server.log it is complaining about the certificate, where it is still mentioning the loadbalancer name for SSO (which is gone and I had changed to the name of this machine).
And also in the vami under vra/sso it says Certificate for (lb-name) doesnt match common name of the certificate subject (machine-name).
There is a GIT repo in /var/lib/vco/app-server/temp/ccTempDir/stagingAreas, try to get the content and restore to a working vRO
That path stops at /var/lib/vco/app-server/temp/ccTempDir
Nothing under there.
Finally I got vRO up.
It turned out that the SSL certificate was expired in the time between power-down and the restore, which caused another chalenge that I did not expect.
Steps followed:
- replace loadbalancer ip in DNS to point directly to the only vra va
- remove secondary node from vra cluster
- repair rabbit-mq
- replace vra va certificate
- make vRO trust the new certificate again
After that, vRO came up and I was able to export all.