Veritas NetBackup™ for OpenStack Administrator's Guide

Last Published:
Product(s): NetBackup (8.3.0.1, 8.3, 8.2)

Known limitations for OpenStack protection using NetBackup

The following table lists the known limitations for OpenStack protection using NetBackup:

Table: Known limitations

Limitation

Workaround

NetBackup does not clean up the OpenStack volumes if the backup operation fails while downloading the volume. The OpenStack dashboard displays that the volume has an error state.

For OpenStack, NetBackup deletes a volume only if the volume has a state other than error.

Workaround:

To delete a volume that has the error state, contact the OpenStack Administrator to delete the volumes manually.

OpenStack backup job fails with error 6619 in the following scenarios:

  • The OpenStack services go down during the backup.

  • The OpenStack is not responding or is slow in response.

  • Connection is reset during the backup.

Workaround:

Restart the OpenStack service and reinitiate the backup.

OpenStack backups complete with the Partially Successful status.

Ensure that the /tmp folder is mounted with the noexec flag to resume successful backups.

NetBackup does not clean up the temporary objects (volumes, volume snapshots and image) if the backup operation fails due to storage unit getting full.

OpenStack administrator must delete temporary objects (volume, volume snapshot and image) manually from the system.

OpenStack backup job fails if backup host has incorrect or empty hostname. In this scenario NetBackup does not clean up the temporary objects (volumes, volume snapshots and image).

OpenStack administrator must delete temporary objects (volume, volume snapshot and image) manually from the system.

If openstack_read_timeout value is greater than or equal to client read timeout in NetBackup host properties, then backup will fail with error "(13) file read failed".

OpenStack administrator must delete temporary objects (volume, volume snapshot and image) manually from the system.