Re: [Duplicity-talk] Six monthly roiling backups

[Ghozlane Toumi]

I'd advise against this kind of strategy.

basically 6 month in the row, you'd have to restore the full backup + 8784 differentials. I hope you have the time and bandwith to do that...

and to answer your next question yes a single corrupt diff would render restoration "a bit more" than hazardous

as for backup cleanup, look for remove-older-than and  remove-all-inc-of-but-n-full  options in the fine manual.

Ghozlane

On Tue, Jun 14, 2016 at 2:07 PM, Ben Edwards via Duplicity-talk <address@hidden> wrote:

Hi, ime new here and have setup a duplicity backup for a owncloud server.  so far I have done a full backup and an ruining incremental backups every 30 minutes.  I guess whatever I do I will at some point have to have two full backups but would like to avid even this if possible.  

So I guess I need to do a full every six months.  I think then I need to tell duplicity to delete anything over 6 months old.  Or is there a better way of doing it.  I am backing up onto a NAS (we have two buildings on the LAN so  we are off siting a couple of doors down).  The owncloud is sized as 1TB and the backup drive is 3TB (all RAID 1).

I am a little worry about what happens if one of the incrementals gets corrupted. Will the verify command tell me?  If it is corrupted will I loose everything or is there a way of recovering some of the backup? 

Any help with command like captions would be great.  I think I can tell duplicity to delete everything older than 6 months on the incremental backup command line but will have to schedule the full backups with cron.  Will duplicity delete the incremental and full backups for me?

Regards,

Ben

--

Ben Edwards, Video Editor and Cameraman
web:www.nkytwig.com mobile:07773 02 44 82 skype:funkytwig twitter:@funkytwig
iContact Community Video | Bristol Community Channel

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk