Manual cleanup of expired Kubernetes backup images from NetBackup 9.1 release

Description:

NetBackup 10.0 can't perform expiration of the snapshots which were created using NetBackup 9.1, as these snapshots are managed via Velero. At the time backup images are expired in NetBackup; NetBackup catalog is automatically cleared but users are expected to delete snapshot on Kubernetes server manually. For each expired backup image, a notification is created in NetBackup consisting of a Snapshot ID which could be used to trigger the snapshot cleanup using Velero.

Follow the instructions to delete a Velero based backup from the cluster

1. Run the following command, to describe a Velero backup:

    $ velero backup describe <backupname>

    Example: $ velero backup describe 10634046-4f4b-11ec-ace3-f70f7453fee2- 1637994435

2. Run the following command, to delete a Velero backup:

     $ velero backup delete <backupname>

     Example: $ velero backup delete 10634046-4f4b-11ec-ace3-f70f7453fee2-1637994435

     Result: $ velero backup delete 10634046-4f4b-11ec-ace3-f70f7453fee2-1637994435

     Are you sure you want to continue (Y/N)? y

Request to delete backup "10634046-4f4b-11ec-ace3-f70f7453fee2-1637994435" submitted   successfully.

Note: Velero backup will be fully deleted after all associated data (disk snapshots, backup files, restores) are removed.

3.  Run the following command, to verify that the Velero backup is deleted:

$ velero get backup <backupname>

Example: $ velero get backup 10634046-4f4b-11ec-ace3-f70f7453fee2-1637994435

Result: An error occurred: backups.velero.io "10634046-4f4b-11ec-ace3-f70f7453fee2-1637994435" not found

Note: Velero performs backup deletion in an asynchronous manner, leading to delay the deletion process of a backup image.