You can backup your vRealize Orchestrator VMs in no particular order. You can also back up the vRealize Orchestrator elements that you modified.

If vRealize Orchestrator is embedded within the vRealize Automation appliance, perform its backup along with Manager Services for vRealize Automation.

If vRealize Orchestrator is a standalone component, perform its backup before backing up vRealize Automation components in no particular order.

vRealize Orchestrator Backup Order

Each vRealize Orchestrator server instance has unique certificates, and each vCenter Server plug-in instance has a unique ID. The certificates and the unique ID identify the vRealize Orchestrator server and thevCenter Server plug-in. If you do not back up the vRealize Orchestrator elements or export the vRealize Orchestrator configuration for backup purposes, make sure that you change these identifiers.

All components of the vRealize Orchestrator must be backed up together and at the same time including the database components. You must back up the vRealize Orchestrator database and VMs (custom workflows and packages).

You can take full database backups of the database in your environment before a full VM backup. The main purpose is to ensure consistency of the data when you have to restore.

Follow your in-house procedures to back up the vRealize Orchestrator database outside of the vRealize Suite framework.