WAL(Write Ahead Log)¶
archive_mode is enabled in order to create incremental database backup, which is triggered by the users.
archive_command is configured as well for continuous WAL archiving, the WAL files in pg_wal subdirectory are copied to
That is going to be a problem if the WAL segment files in the archive folder keep increasing, especially in the busy system, several TBs of WALs can be piled up in archive destination(part of the data volume), which will lead to the database service unavailable.
In the PostgreSQL manager of trove-guestagent, there is a periodic task aiming at cleaning up the archive folder, when it’s running, it checks the size of the archive folder, if the size is greater than half of the data volume size, in the archive folder:
If there is no
.backupfile, it means the database has never been backed up before, all the WAL segment files except for the latest one are removed.
If there are
.backupfiles, remove all the files older than the backup file. Check the size again, if the size condition is still met, all the WAL segment files except for the latest one are removed.
When creating the incremental backup, trove will check if the parent backup file still exists in the archive folder, the backup creation will fail if that’s not found. The user is able to see the error message in the instance detail and has to create full backup instead.
Another option is to archive WAL files to Swift(in the user’s account), e.g. using WAL-G or other 3rd party tools, but that will incur charges for the object storage usage which is not optimal. We leave it to the users to decide when and how the backups should be created.