Automatic deletion of expired backup files does not always work properly on remote volumes
Details
| Detail name | Value |
|---|---|
| Changelog Number | 7208 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | EXASOL 6.0.0, Exasol 6.1.0, Exasol 6.2.dev2 |
| Fix Versions | Exasol 6.0.14, Exasol 6.1.1 |
| Resolution Date | 2018-12-14 |
Problem Description
The deletion process on remote volumes is controlled by a separate expiration file. The current algorithm deletes all files (backup files + expiration files) in parallel. It may happen that the expiration file of a backup set is deleted too early, and therefore not all nodes can properly delete their backup files.
Workaround
The error does not occur if the extra database parameter -suppressParallelBackupDeletion is set. However, this may slow down expiration of backups stored on Exasol storage volumes.
Keep in mind
Backup files with already missing expiration files are not deleted by this fix, but must be deleted manually. You can detect these incomplete backup sets using the backup view within EXAoperation.
