RHV Plugin: Limitations

Enterprise

Bacula Enterprise Only

This solution is only available for Bacula Enterprise. For subscription inquiries, please reach out to sales@baculasystems.com.

The following chapter describes the limitations of the RHV Plugin.

The plugin currently does not support the following features:

• The backup snapshot method is not compatible with RHVM4.1.

• Virtual Machines in Suspended status cannot be backed up. This is oVirt/RHV limitation as do a snapshot is not allowed with that state.

• The Incremental/Differential backup is only compatible with snapshot backups.

• The Incremental/Differential backup is compatible with RHV Plugin version >= 4.0.0.

• The proxy backup is compatible only with Bacula Enterprise version >= 12.4.0.

• Virtual Full backups.

• Using an external OAuth / SSO service different from the one provided directly by RHV.

• Stop or Resume incomplete Jobs. For this to be possible with the guarantee of consistent backups, snapshots of virtual disks and cloned VMs would need to be kept.

• Optimized backup with thin disks. The Ovirt API doesn’t provide any information about thin disk usage, except with thin disks located in iSCSI storage.

• Restores from a backup sequences based on a Full and Differential and/or Incremental snapshots of VMs that contain at least one disk in a Block Based Storage Domain are possible only with RHV versions 4.4.5 or newer.

• The restart command has limitations with plugins, as it initiates the Job from scratch rather than continuing it. Bacula determines whether a Job is restarted or continued, but using the restart command will result in a new Job.

See also

Previous articles:

• RHV Plugin: Scope

• RHV Plugin: Features

• RHV Plugin: Architecture

• RHV Plugin: Backup and Restore Strategies

• RHV Plugin: Installation

• RHV Plugin: Configuration

• RHV Plugin: Operations

Next articles:

• RHV Plugin: Troubleshooting

• RHV Single Item Restore

Go back to: RHV Plugin.