Missing warnings for inconsistent expiry dates for remote backups
Details
| Detail name | Value |
|---|---|
| Changelog Number | 16419 |
| Type | Improvement |
| Status | Resolved |
| Fix Versions | Exasol 8.12.0, Exasol 7.1.19 |
| Resolution Date | 2023-03-13 |
Background
Backups can be created with set expiration dates, after which the backup is no longer valid.
Description
If a level 1 backup has an expiration date that is set after the expiration date of the level 0 backup which it is based on, the level 1 backup cannot be used. The reason for this is that the base backup is expired and therefore no longer valid. In general, an incremental backup should not have an expiration time that is longer than the base backup.
In these cases, there is no warning or message to the user informing them about this misconfiguration.
Improvement
A warning is logged when there are inconsistent expiration dates between incremental backups and the level 0 backup.
