Re: [Duplicity-talk] Having to specify incrementals

[Elvar]

On 3/29/2013 11:49 AM, address@hidden wrote:
> On 29.03.2013 17:31, Elvar wrote:
> > Hello,
> >
> > I recently started using Duplicity to perform offsite backups for a linux 
> > server of ours. When I performed  a simulated disaster recovery scenario I 
> > found that the only data I had been able restore was data from the initial full 
> > backup. It doesn't appear that Duplicity was automatically doing incrementals 
> > despite the data growing. Below is the command I'm using...
> >
> > FTP_PASSWORD='somepass' PASSPHRASE='somepass' duplicity /mnt 
> > ftps://address@hidden
> >
> > Shouldn't that automatically assume incrementals if the full had already been 
> > done?
> yes. what's the output of collection-status?
>
> ..ede/duply.net

After having manually ran an incremental or two, here is the current status.

Import of duplicity.backends.giobackend Failed: No module named gio
Import of duplicity.backends.sshbackend Failed: No module named paramiko
LFTP version is 4.3.3
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Thu Mar 28 17:03:26 2013
Collection Status
-----------------
Connecting with backend: FTPSBackend
Archive dir: /root/.cache/duplicity/cb471964ea71f51bdbff729d2a8e763e

Found 0 secondary backup chains.

Found primary backup chain with matching signature chain:
-------------------------
Chain start time: Thu Mar 28 17:03:26 2013
Chain end time: Fri Mar 29 11:23:11 2013
Number of contained backup sets: 6
Total number of contained volumes: 61
 Type of backup set:                            Time:      Num volumes:
                Full         Thu Mar 28 17:03:26 2013 50
         Incremental         Thu Mar 28 19:24:47 2013                 1
         Incremental         Fri Mar 29 09:23:59 2013                 1
         Incremental         Fri Mar 29 09:33:08 2013                 1
         Incremental         Fri Mar 29 10:12:58 2013                 1
         Incremental         Fri Mar 29 11:23:11 2013                 7
-------------------------
No orphaned or incomplete backup sets found.


Thanks!