PostgreSQL dump based backup is filling C: drive up to 100 percent

Hi All,

During the PostgreSQL backup the C: drive is filling up to 100%. The database itself has about 400 GB on drive.

The disk space used on C: is 34 GB when no backups are running. But 150 GB (whole disk) is used during backups.

I need to prevent the C: drive from getting full during the backup.

What fills up the C: drive?

Is it possible to redirect it to another drive/folder?

Any other ideas?

Thank you,

Lubos

Page 1 / 1

My first guess is the Commvault Job Results folder.

Here is the change location instruction:

Hi Lubos,

Please check if the same pg_dump command consumes so much C:\ space when performed outside of Commvault. You will get the command from PostGresBackup.log
If you see -Fc in the command , it is performing a compressed dump, which is not enabled by default. Default format is tar (-Ft). Compressed dump is enabled with registry key sPGCompDump set on client. Staging is must for this type of dump and default staging path is job results directory. To change staging path, sPGStagingDir can be used.

Regards,

Meera

Hi @Meera,

The backup was using C:\Windows\Temp\ as a staging directory and I have found -Ft in the PostGresBackup.log.

I have set the parameters sPGCompDump and sPGStagingDir and started a backup.

The backup is now using new staging location but it seems to run slower than before (with -Ft). I’ll check on Monday and get back.

Regards,

Lubos

Hi Lubos,

For tar dump(-Ft) we do not stage data. It should be postgres behavior, which can be confirmed by doing a manual tar dump with pg_dump utility.

Regards,

Meera

Setting sPGCompDump and sPGStagingDir did not solve the issue as the backup became much slower.

Finally we increased the size of the C: drive.

Hi Lubos,

What is the postgres version?

Regards,

Meera

Hi @Meera,

The postgres version is 12.

Regards,

Lubos

Sign up