Thread: pg_dump is filling C: drive up to 100 percent

> On Sep 1, 2022, at 21:41, Meera Nair <mnair@commvault.com> wrote:
> Archival hangs. Is this expected?
> postgres=# select pg_start_backup('test', true, false);
> pg_start_backup
> -----------------
> 1/F9000060
> (1 row)
>
> postgres=# select pg_stop_backup('f');
> NOTICE:  base backup done, waiting for required WAL segments to be archived
> WARNING:  still waiting for all required WAL segments to be archived (60 seconds elapsed)
> HINT:  Check that your archive_command is executing properly.  You can safely cancel this backup, but the database
backupwill not be usable without all the WAL segments. 
> WARNING:  still waiting for all required WAL segments to be archived (120 seconds elapsed)
> HINT:  Check that your archive_command is executing properly.  You can safely cancel this backup, but the database
backupwill not be usable without all the WAL segments. 

This generally means the command being run by archive_command is failing.  Check the PostgreSQL logs (if you are using
CSVlogs, check the *.log file rather than the *.csv file). 

Hi Christophe,

If pg_stop_backup is executed in master OR if standby server is restarted, I can see the archiving completing fine.
Only issue is while manually executing the pg_stop_backup in standby

Regards,
Meera

-----Original Message-----
From: Christophe Pettus <xof@thebuild.com>
Sent: Friday, September 2, 2022 7:43 PM
To: Meera Nair <mnair@commvault.com>
Cc: pgsql-general@lists.postgresql.org; Punit Pranesh Koujalgi <pkoujalgi@commvault.com>
Subject: Re: Unable to archive logs in standby server

External email. Inspect before opening.



> On Sep 1, 2022, at 21:41, Meera Nair <mnair@commvault.com> wrote:
> Archival hangs. Is this expected?
> postgres=# select pg_start_backup('test', true, false);
> pg_start_backup
> -----------------
> 1/F9000060
> (1 row)
>
> postgres=# select pg_stop_backup('f');
> NOTICE:  base backup done, waiting for required WAL segments to be
> archived
> WARNING:  still waiting for all required WAL segments to be archived
> (60 seconds elapsed)
> HINT:  Check that your archive_command is executing properly.  You can safely cancel this backup, but the database
backupwill not be usable without all the WAL segments. 
> WARNING:  still waiting for all required WAL segments to be archived
> (120 seconds elapsed)
> HINT:  Check that your archive_command is executing properly.  You can safely cancel this backup, but the database
backupwill not be usable without all the WAL segments. 

This generally means the command being run by archive_command is failing.  Check the PostgreSQL logs (if you are using
CSVlogs, check the *.log file rather than the *.csv file). 

At Tue, 30 Aug 2022 05:22:56 +0000, Meera Nair <mnair@commvault.com> wrote in 
> Hi Guillaume/team,
> 
> I set archive_mode = always in master and standby.
> Archival to standby WAL directory completed when
> 
>   *   standby server was restarted
>   *   pg_stop_backup was executed in master
> 
> But archival hangs when pg_stop_backup is executed in standby.
> Could someone help to get this working?

https://www.postgresql.org/docs/12/continuous-archiving.html

> In the same connection as before, issue the command:
> 
> SELECT * FROM pg_stop_backup(false, true);
> 
> This terminates backup mode. On a primary, it also performs an
> automatic switch to the next WAL segment. On a standby, it is not
> possible to automatically switch WAL segments, so you may wish to run
> pg_switch_wal on the primary to perform a manual switch. The reason
> for the switch is to arrange for the last WAL segment file written
> during the backup interval to be ready to archive.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center

Hi Kyotaro,

This helped, thanks.

Regards,
Meera

-----Original Message-----
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Sent: Monday, September 5, 2022 7:31 AM
To: Meera Nair <mnair@commvault.com>
Cc: guillaume@lelarge.info; pgsql-general@lists.postgresql.org; Punit Pranesh Koujalgi <pkoujalgi@commvault.com>
Subject: Re: Unable to archive logs in standby server

External email. Inspect before opening.



At Tue, 30 Aug 2022 05:22:56 +0000, Meera Nair <mnair@commvault.com> wrote in
> Hi Guillaume/team,
>
> I set archive_mode = always in master and standby.
> Archival to standby WAL directory completed when
>
>   *   standby server was restarted
>   *   pg_stop_backup was executed in master
>
> But archival hangs when pg_stop_backup is executed in standby.
> Could someone help to get this working?


https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.postgresql.org%2Fdocs%2F12%2Fcontinuous-archiving.html&data=05%7C01%7Cmnair%40commvault.com%7C240c3d6f31074e32206c08da8ee277fe%7C40ed1e38a16e46229d7c45161b6969d5%7C0%7C0%7C637979400603662396%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=UHsS8ZG1Vll0z8p3ce6WPfm3IniqVYMtOPfin3Lahbg%3D&reserved=0

> In the same connection as before, issue the command:
>
> SELECT * FROM pg_stop_backup(false, true);
>
> This terminates backup mode. On a primary, it also performs an
> automatic switch to the next WAL segment. On a standby, it is not
> possible to automatically switch WAL segments, so you may wish to run
> pg_switch_wal on the primary to perform a manual switch. The reason
> for the switch is to arrange for the last WAL segment file written
> during the backup interval to be ready to archive.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center