Skip to main content
Question

PostgreSQL lack of space for WAL

  • October 27, 2026
  • 1 reply
  • 8 views

Forum|alt.badge.img+7

Hi,

When running an Incremental database backup for PostgreSQL, Commvault waits for the archive_command to complete successfully. If the storage resource designated for archive WAL files is not large enough to hold all generated archive files, the backup process hangs/freezes while waiting for their archiving to finish.

Is it possible to configure Commvault so that it processes/backs up all currently available archived WAL files first and then waits for the remaining ones to be transferred?

Alternatively, does Commvault plan to introduce such a feature, or is this already on the product roadmap?

Regards,

Lukasz

1 reply

Meera
Vaulter
Forum|alt.badge.img+9
  • Vaulter
  • October 27, 2026

Hi Lukasz,

https://documentation.commvault.com/11.42/software/serverless_log_backups.html

serverless log backup feature provides capability to archive logs to MA library location. It avoids such delay in backup of logs and no space is required locally to archive logs. 

 

https://documentation.commvault.com/11.42/software/optimizing_postgresql_log_backups.html#enable-serverless-log-backup

 

When this feature is enabled, archive_command is modified to copy the logs to library location in the MediaAgent associated with the instance. Whenever a log is ready to archive, it gets copied to the library location. 

To append to the archive_command, instead of overwriting the existing command (for example: incase of replication setup), set the bPreserveArchiveCommandWithDumpSweep additional setting under PostGres to 1.

 

Regards,

Meera