Hi,
We use pgbackrest 2.34 on RHEL8.4 to backup PGv13 database to AWS S3 buckets , we found after some time successful backup , suddenly got below error:
2022-07-23 10:30:04.743 P00 INFO: archive-push:async command begin 2.38: [/pgdata/pg_wal] --archive-async --archive-push-queue-max=10240MB --compress-type=none --exec-id=813450-3a783f75 --log-level-console=off --log-level-stderr=off --pg1-path=/pgdata --process-max=2 --repo1-path=/pgbackup --repo1-s3-bucket=xxxxxxxxx --repo1-s3-endpoint=s3-fips.us-west-2.amazonaws.com --repo1-s3-key-type=auto --repo1-s3-region=us-west-2 --repo1-type=s3 --spool-path=/pgarchive/pgbackrest --stanza=xxxxxxx
2022-07-23 10:30:04.744 P00 INFO: push 1 WAL file(s) to archive: 00000001000000DB000000A4
2022-07-23 10:30:04.907 P00 ERROR: [103]: unable to find a valid repository:
repo1: [FileMissingError] unable to load info file '/pgbackup/archive/xxxxxx/archive.info' or '/pgbackup/archive/xxxxxx/archive.info.copy':
FileMissingError: unable to open missing file '/pgbackup/archive/xxxxxx/archive.info' for read
FileMissingError: unable to open missing file '/pgbackup/archive/xxxxxx/archive.info.copy' for read
HINT: archive.info cannot be opened but is required to push/get WAL segments.
HINT: is archive_command configured correctly in postgresql.conf?
HINT: has a stanza-create been performed?
HINT: use --no-archive-check to disable archive checks during backup if you have an alternate archiving scheme.
Then we login to check both archive.info and archive.info.copy got disappeared in S3 bucket , we do not have job or command to manually delete that file, and we do not recreate standza either, not sure why suddenly missed the archive.info. without the archive.info, we have to recreate pgbackrest stanza repo again, but all old backup pieces got invalid too.
Could you help figure out how that happened ? we faced this issue several times .
Thanks,
James
This doesn't have anything directly to do with Postgres server or client.
Questions which might help you with troubleshooting the issue:
- Are you certain the file is gone and not just owned by a specific user?
- Was the file a symbolic link or a mount?
- Have you checked logs including history for users that have access to the server?
- Have you checked the S3 bucket? Does it still exist and have the data?
- How was this installed/setup the first time? Do you have a ticket or documentation that might help you with troubleshooting?
Again, this is the wrong forum / list for the question, but, given the information, getting answers to some of these would be my approach. REL support or https://pgbackrest.org/#support (which points to Crunchy Data) may be able to help further.
Best regards,
Dan Smith
On Wed, Aug 3, 2022, 05:23 James Pang (chaolpan) <chaolpan@xxxxxxxxx> wrote:
