Re: [Duplicity-talk] Restart from Last Full Backup

[Alan Gutierrez]

Thank you for the clarification. I'm going to assume that I accidentally re-ran
an old command in my shell history that initated a full backup while working on
my backup scripts. I have verbosity in the logs set to 8, there is to much to
weed through now to find something to copy and paste.

It wouldn't have anything to do with --allow-source-mismatch would it? I added
that to my backup scripts recently. 

I'm going to specify incremental explictly. I see that Duplicity terminates if
it cannot find a full backup if incremental is not specified. If I see it
complain in that fashion when a full backup is available, I'll let you know.

On Mon, Feb 18, 2013 at 10:08:04AM +0100, address@hidden wrote:
> *no*. duplicity only creates fulls if 
> - configured via --full-if-older-than
> or
> - no full can be found
> 
> what did your log output say?
> 
> .ede/duply.net
> 
> On 18.02.2013 09:19, Alan Gutierrez wrote:
> > A follow up to this. I wanted to simply add an occasional incremental 
> > update to
> > a large full backup that I never intended to rerun. I've been running 
> > Duplicity
> > from `cron` for a while now and I see that it went and decided to do a full
> > backup all on its own. Is this Duplicity's correct behavior, to run a full
> > backup every two weeks by default? I know the obvious solution is to specify
> > `incremental`, but I'm curious as to whether or not there is scheduling 
> > built
> > into Duplicity.