Re: [Duplicity-talk] some questions (--remove-than-older, --cleanup, --archive-dir)

[Antony]

Ken,

Since my server is at my ISP, and local bandwidth is quite big, I
guess, the only thing I can do is setup a linux box capable of
receiving duplicity backup at office.

Thanks Ken. Appreciated your help. :-)

Rgds,
Antony

On Nov 6, 2007 4:17 AM, Kenneth Loafman <address@hidden> wrote:
> You got hit by the classic Catch-22 of backups.  You can't "delete older
> than" because the incremental backups require the full backup to supply
> the original file.  Incremental backups store the changes to the
> original file, not the entire file.
>
> As to the size of the backup... Don't go for a huge backup in one pass.
> Split it up into multiple steps, each step only a few hours long.  That
> way, when one fails, it can be restarted easily.
>
> ...Ken
>
>
> Antony wrote:
> > Hi Ken, thanks for your reply..
> >
> > I tried the cleanup.. it worked well..
> > And I also tried the remove-older-than .. but I got this error:
> >
> > Which can't be deleted because newer sets depend on them.
> > No old backup sets found, nothing deleted.
> >
> > Does this mean I have to make full backup first before deleting old
> > ones? Cause I really can't, it took me 2 full days to make my first
> > full backup :(
> >
> > rgds,
> > Antony
> >
> > On Nov 6, 2007 2:28 AM, Kenneth Loafman <address@hidden> wrote:
> >> Antony wrote:
> >>> Hi all,
> >>>
> >>> I'm trying to figure how how to make --remove-older-than and --cleanup
> >>> option works... duplicity is complaining about an incomplete backup set.
> >>>
> >>> this is my current duplicity command on debian etch...
> >>>
> >>> duplicity --allow-source-mismatch --remove-older-than 2M --cleanup
> >>> --encrypt-key="xxxxx" [source] [target]
> >>>
> >>> After searching this list I found out that --remove-older-than and
> >>> --cleanup should be on a separate command.. but I don't know should I
> >>> use [source] [target] here .. or just [target] ?
> >> Both commands require --force to allow them to actually delete.  You
> >> only need the [target] spec for these commands.
> >>
> >>> I started the backup job without --archive-dir, now after reading about
> >>> it, I'd like to use it.. can I just put --archive-dir to the command
> >>> right now?
> >> On the next full backup you can start using it.
> >>
> >>> I'm guessing this is what my final backup commands should be:
> >>> duplicity --allow-source-mismatch --archive-dir [dir]
> >>> --encrypt-key="xxxxxx" [source] [target]
> >>> duplicity --allow-source-mismatch --remove-older-than 2M
> >>> --encrypt-key="xxxxxx" [target]
> >>> duplicity --allow-source-mismatch --cleanup --encrypt-key="xxxxxx"
> >>> [source] [target]
> >>>
> >>> also:
> >>> duplicity told me that I need to put --allow-source-mismatch, I did
> >>> change the target url once.. is there a way to remove this?
> >> Target url does not matter.  What must have changed was the source url.
> >>  Source mismatch means you are trying to store two different sources in
> >> the same target.
> >>
> >>> Is it ok to run cleanup all the time or just when there is an incomplete
> >>> backup set ?
> >> I run cleanup and remove-older-than before each backup to keep things
> >> clean.  Helps to save space if you're tight.
> >>
> >>> I hope it's correct to put all the questions here than to send out more
> >>> than one postings. Thanks a lot for your time.
> >> No problem, hope it helps.
> >>
> >> ...Ken
> >>
> >>
> >>
> >> _______________________________________________
> >> Duplicity-talk mailing list
> >> address@hidden
> >> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
> >>
> >>
> >
> >
> > _______________________________________________
> > Duplicity-talk mailing list
> > address@hidden
> > http://lists.nongnu.org/mailman/listinfo/duplicity-talk
> >
>
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
>