New question #133863 on Duplicity: https://answers.launchpad.net/duplicity/+question/133863
Hi, I am backupping a 50GB worth of data on a remote server through a 2 Mbits line. The full backup takes me roughly 4 days, an incremental backup about 15 minutes. I have my settings set to: /usr/bin/duplicity --name backup1 --encrypt-key masked--sign-key masked--verbosity 6 --full-if-older-than 1M --asynchronous-upload --ssh-askpass /home scp://[email protected]/backup/ now my big concern is that while a full-backup is triggered after one month, my incrementals would not be uploaded during the 4 days it takes to upload the full backup. If I simply start another process, another full-backup would be triggered. I am looking for a best practise to prevent my backups having a 4 day "hole" every month. Thank you for your help -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
