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:
| Workaround: Restart the OpenStack service and reinitiate the backup. |
OpenStack backups complete with the Partially Successful status. | Ensure that the |
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. |
OpenStack restore to other node for different volume type fails with the following error because volume type for instance on source node was not available on destination node: Volume type with name <volume type> could not be found | Workaround:
|
OpenStack restore job fails with the following error: tar did not find all the files to be restored When the volume attach operation results in failure, the following error message is added in the tar logs: Failed to Attach Volume while doing restore obj In this scenario the instance will get recovered without data. | Delete the new recovered instance as it does not have any data associated with it. Contact OpenStack Administrator to check the health of OpenStack system and understand the reason why the attach volume operation resulted in failure. |
If two OpenStack backup jobs start simultaneously and try to backup the same instance, then the second backup job of the same instance might fail while creating snapshot of the Instance. The following error message is seen in the logs: Cannot 'createImage' instance while it is in task_state image_pending_upload | One of the backup jobs is successful and the data is protected. Run the failed job again to ensure that it is successful. |
OpenStack VM backup fails | If your NetBackup master or media server is on version 8.3 and the NetBackup backup host (NetBackup media server or client) is on version 8.3.0.1, the OpenStack VM backup fails. Workaround: Ensure that the NetBackup version is 8.3.0.1 on the master server, media server, and the client. |