You can back up and restore your vRealize Orchestrator deployment by using vSphere virtual machine (VM) snapshots.
The following procedure is based around backing up and restoring a clustered vRealize Orchestrator deployment. For standalone a vRealize Orchestrator deployment, you take a vSphere snapshot and revert your deployment from it without the additional cluster specific steps outlined in this procedure.
Note: For more information on using
vSphere virtual machine snapshots, see
Take a Snapshot of a Virtual Machine and
Revert a Virtual Machine Snapshot.
Procedure
- Identify the primary node of your vRealize Orchestrator cluster.
- Log in to the vRealize Orchestrator Appliance command line of one of your nodes over SSH as root.
- Find the node with the
primary
role by running the kubectl -n prelude exec postgres-0 command.kubectl -n prelude exec postgres-0 – chpst -u postgres repmgr cluster show --terse --compact
- Find the FQDN address of the primary node by running the kubectl -n prelude get pods command.
kubectl -n prelude get pods -o wide
- Back up your vRealize Orchestrator deployment.
- Log in to the vSphere Client.
- Take snapshots of your vRealize Orchestrator nodes.
When backing up your nodes, you must follow a specific order. First, back up your replica nodes and after that, back up the primary node.Note: Do not take snapshots of your vRealize Orchestrator nodes with the Snapshot the virtual machine’s memory option enabled.
- Restore your vRealize Orchestrator deployment.
- Revert your vRealize Orchestrator nodes from the snapshots you created in step 2.
- Power on the vRealize Orchestrator nodes.
When powering on the nodes, you must follow a specific order. First, power on your primary node and after that, power on your replica nodes.