postgresql DB backup doesnt't work

[martindemko]

Currently, the process doesn't work because the main backup.py script expects the existence of a python binary, which doesn't exist in our instances. Only python2* and python3* exist. As a result of this, only transaction logs are stored but without the necessary base backup.
As the correction of our situation, I suggest adding a new ansible task to check the existence of python followed by the creation of the python link in the negative response.

[martenson]

with #95 in place we should test the backup again

[martindemko]

Sure, I will rerun ansible playbook on QA1 first.

[martindemko]

The Postgresql backup machinery is still not working. Missing Python binary wasn't the only problem. There is something wrong with the ansible templating in here resulting in:

#Ansible: PostgreSQL Backup
0 1 * * * postgres python '~postgres/backups'/bin/backup.py  --rsync-backup-opts '\-rptg' --keep 30  --backup --clean-archive /data/galaxy/backups

and the problem is that '~postgres/backups' can't expand itself. The quotes are hardcoded in galaxyproject.postgresql role here. We could either rewrite the whole backup command (it's postgresql_backup_command variable) or find out a way how to specify postgres homedir correctly, so the quotes will not ruin it.

[martindemko]

According to this line it should work. We need to check the version of the role and sources, if they match.

[martindemko]

I think that this line is what causes the whole problem. I would like to test my hypothesis on QA1, is it available @martenson?

[martenson]

@martindemko yep