PostgreSQL lack of space for WAL

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

Hi,

I've already informed the customer about serverless log backup, but they claim it’s not a suitable solution for them.

They need confirmation on whether there are any other options available for this use case.

In the meantime, the customer found a workaround using wal_compression, but it isn't mentioned in the Commvault documentation. Could you please confirm if this is supported by Commvault?

Regards,

Łukasz

Hi Lukasz, 

Please see this - https://documentation.commvault.com/2024e/commcell-console/faq_05.html#do-we-support-compression-for-transaction-logs

Just curious—is there a particular reason why serverless log backups is not suitable for them?

Regards,

Meera