stouts / stouts.backup Goto Github PK

EDITED: In my fork of Stouts.backup it allows turning --no-compression option on: apparently, in duplicity 0.6 there's a nasty bug in this:
https://serverfault.com/questions/726525/cannot-restore-duplicity-backup

If the restore fails due to an error,
for example the backup directory being empty because no backup has been run yet,
the customized version of duply returns 0.

This seems to be because of the run_script $CONFDIR/restore; line, which always runs the script,
even if the restore command above it fails.

Hi,

I found your playbook very useful.

However, I have a problem using two different playbooks with different profiles on the same server. The last used playbook delete the first backup configuration.

Is there a way of using two independents playbook on the same server?

Thanks,

Hi,

It seems that installing duplicity on Ubuntu for a PPA using backup_duplicity_ppa has been dropped since version 3.4.1 ( https://github.com/Stouts/Stouts.backup/blob/3.4.1/tasks/install.deb.yml#L5 ). So I am wondering if this a mistake? or if moving forward I should install the PPA first before using this role.

Thank your for your help

Seems to be this is not specified in readme, or even defaults.yml

When I try to use params to initialize the environment variables for SWIFT:

- name: myprofile
  max_full_backups: 5
  full_max_age: 1W
  schedule: 0 6 * * *
  source: /home/project/backup
  target: swift://myprofile
  params:
    - "SWIFT_USERNAME=--username--"
    - "SWIFT_PASSWORD=--password--"
    - "SWIFT_AUTHURL=https://auth.cloud.ovh.net/v2.0"
    - "SWIFT_TENANTNAME=-tenantname-"
    - "SWIFT_AUTHVERSION=2"

I have the exception

Container creation failed: ClientException No tenant specified

I have a need right now to backup to s3 and this looks to work fine, but I also want to start backing up to my server at home which would be via ssh keys, can this tool backup to multiple targets? What would that playbook config look like if so?

Any solutions?

example: port 5555

I have a need to do the following when a backup fails

• send an email to myself
• create a pagerduty incident, either via the REST API or via email

I am wondering if this playbook has any type of notifications system for failed backups.

I need to put my app into maintenance mode before the backup happens, and then pull it out of maintenance mode afterwards.

I'd also like to backup both the db and directory, one after the other, in the same cron job, rather than at separate times.

Are these things possible with Stouts.backup?

Guessing this line should just be "mongo://" but I don't work with Mongo enough.

https://github.com/Stouts/Stouts.backup/blob/master/templates/restore_mongo.j2

DBNAME={{item.source.split('mysql://')[-1]}}

Hi,
#19 notes that /usr/local/bin might not exist, and 941ed6e notes this as fixed, but https://github.com/Stouts/Stouts.backup/blob/develop/templates/cron.j2#L7 still references the /usr/local/bin path which is causing my jobs to fail.

I've corrected this manually in my local copy with success, and I'd be happy to submit a PR, but given that these templates are generated with Ansible I don't want to break something by manually editing them.

Let me know if I can help by submitting a PR!

It would be great to have ability to use options file with credentials or run mysql/mysqldump without credentials options if credentials already set in my.cnf file.
See https://dev.mysql.com/doc/refman/5.7/en/password-security-user.html

Hello,

I noticed that you support the following for passing parameters to the /etc/duply/postgres/pre backup bash script

# Posgresql
backup_postgres_user: postgres
backup_postgres_host: ""

Do you support passing a password argument for the database into this script as well?
I would prefer to not have to set a trust within a pg_hba.conf file for whichever user is being used for backup access.

Is this something that needs to be set as an environment variable, or passed within the backup_profile[:source] ?

Got this error on fresh ubuntu 14.04 installation

TASK [Stouts.backup : backup-configure | Install duply] ************************
fatal: [95.213.235.x]: FAILED! => {"changed": true, "failed": true, "msg": "Destination directory /usr/local/bin does not exist"}
        to retry, use: --limit @dbservers.retry