duplicity should use a different directory for every backup

Good ideas? Share with us!

duplicity should use a different directory for every backup

Postby on4aa » 19 Jul 2010, 23:47

Duplicity should use a different directory for *every* backup.

Really, this is such a mess... so many backup volumes in one folder.
Even ls *.manifest takes ages to complete over ssh.

duplicity-full.yyyymmddThhmmssZ folders should be made for every backup containing only volumes to that backup.

Furthermore, I would like to have one single central duplicity log file to see what backups went wrong and for what reason. Now. one has to manually search for signature files.

In case of an adverse backup event, an alert message on the login page and/or alert e-mail would also be desirable.
on4aa
 
Posts: 14
Joined: 18 Nov 2009, 21:37

Re: duplicity should use a different directory for every bac

Postby on4aa » 27 Jul 2010, 21:58

on4aa wrote:Furthermore, I would like to have one single central duplicity log file to see what backups went wrong and for what reason. Now. one has to manually search for signature files.


I am still learning under the hood here:

I found out that duplicity writes its log files under
/var/log/backup/admin/name_of_your_scheme
on4aa
 
Posts: 14
Joined: 18 Nov 2009, 21:37


Return to Bubba Two Feature Requests

Who is online

Users browsing this forum: No registered users and 0 guests

cron