We have a postgresql database that is backed up nightly from a cron job with a following command:
su postgres -c "pg_dump our_database | gzip > /home/smb/shared/database_backup.bak.gz"
recently we had a disk failure that started with a few bad sectors and during that time pg_dump exited with the following errors
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: catalog is missing 17 attribute(s) from relid 20158
pd_dump: The command was: LOCK TABLE public.obvez IN ACCESS SHARE MODE
Now, since it was in cron job, nobody noticed error messages, the backup was interrupted but it wasn't zero sized, everything seemed ok and the error went unnoticed until final disk failure when we realized we didn't have backup.
We managed to restore data from an older backup but now I would like to know what would be the proper way to check if pg_dump finished its job with success or not?
I write the outcome into a logfile, and at the end of the cronjob, I send the content of the logfile to my e-mail address. That way, I'll know when something went wrong.
su postgres "pg_dump our_database 2>> $LOG_FILE | gzip > /home/smb/shared/database_backup.bak.gz"
cat $LOG_FILE | mailx $MAINTAINERS -s "Postgresql backup"
ADDENDUM: if you want to send the e-mail only if anything went wrong, you can check the return code of pg_dump:
LOG_FILE=/tmp/pgdump.err
if ! pg_dump -U backupuser "our_database" 2> $LOG_FILE
then
cat $LOG_FILE | mailx 'youremailaddress' -s "Postgresql backup failure!"
fi
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With