Backup failed but datastore space still occupied

[proxwolfe]

Hi,

I just ran a new backup via PBS backup client which - for reasons I still have to investigate - failed.

2021-10-08T12:36:23+02:00: starting new backup on datastore 'tx13303enc': "host/nextcloud/2021-10-08T10:36:23Z"
2021-10-08T12:36:23+02:00: created new dynamic index 1 ("host/nextcloud/2021-10-08T10:36:23Z/catalog.pcat1.didx")
2021-10-08T12:36:23+02:00: created new dynamic index 2 ("host/nextcloud/2021-10-08T10:36:23Z/nextclouddisk.pxar.didx")
2021-10-08T13:00:25+02:00: backup failed: connection error: error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac:../ssl/record/ssl3_record.c:676:
2021-10-08T13:00:25+02:00: removing failed backup
2021-10-08T13:00:25+02:00: POST /dynamic_chunk: 400 Bad Request: error reading a body from connection: broken pipe
2021-10-08T13:00:25+02:00: TASK ERROR: connection error: error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac:../ssl/record/ssl3_record.c:676:

The log entry above states that the failed backup is being removed.

However, the datastore is still occupied by (some part of) the backup (that is easy to tell because it would have been the first backup to this datastore.)

How can I purge the failed backup from the datastore?

(Any ideas what went wrong with the backup itself are also welcome...)

Thanks!

 

[dietmar]

The garbage collection process will cleanup stale data.