Expired backups on Google Cloud Storage are not removed
Details
| Detail name | Value |
|---|---|
| Changelog Number | 10530 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 6.1.7, Exasol 6.2.2, Exasol 7.0.alpha1 |
| Fix Versions | Exasol 6.2.9, Exasol 7.0.rc2, Exasol 6.1.13 |
| Resolution Date | 2020-07-31 |
Description
When using Google Cloud Storage as a remote archive volume for database backups, expired backups are not removed correctly.
Workaround
The backups can be removed manually by removing all keys with a given backup ID, e.g. for the backup with ID 1:
DB1/id_1/level_0/node_0/backup_202007011200 DB1/id_1/level_0/node_0/metadata_202007011200 DB1/id_1/level_0/node_0/status_202007011200 DB1/id_1/level_0/node_1/backup_202007011200 DB1/id_1/level_0/node_2/...
Care should be taken with incremental backups, e.g. a level 1 backup depends on the level 0 backup that precedes it, so the level 0 backup should not be removed in then. For this reason, we recommend only deleting old backups if a newer level 0 backup exists. Alternatively, the backups can be preserved until you update to one of the fix versions, then old affected backups can be removed after a new backup with the correct expiration information was written.
Fix
Expired Backups residing on Google Cloud Storage will be removed once they are expired.
