The 'Ad Hoc Backup' workflow is implemented as a script within vRO as follows:
- The vRO script asks Protector to check that the 'VRO Ad Hoc Dataflow' is inactive, indicating that it is not currently performing a backup.
- The vRO script activates the 'VRO Ad Hoc Dataflow' within Protector.
- The vRO script checks that the policy classification assigned to the 'VRO Ad Hoc Dataflow' within Protector selects the 'Protector Ad Hoc' tag.
- If any VMware object is already tagged with the 'Protector Ad Hoc' tag, the vRO script will abort the workflow.
- The vRO script tags the selected VM with the 'Protector Ad Hoc' tag.
- The vRO script triggers the Protector operations on the 'VRO Ad Hoc Dataflow'.
- The vRO script deactivates the 'VRO Ad Hoc Dataflow' within Protector once the backup is complete.
- The vRO script removes the 'Protector Ad Hoc' tag from the selected VM.
Note: This sequence is designed to support data flows that perform block storage snapshots and host based batch backups to a repository. If you intend to trigger more complex data flows, be aware of the effect that data flow activation and deactivation may have on any block replication operations.