Re: [Duplicity-talk] Restore files older than the last full backup

[Rodrigo Campos]

On Fri, Nov 13, 2015 at 06:00:02PM +0100, address@hidden wrote:
> On 13.11.2015 17:53, Rodrigo Campos wrote:
> > Hi,
> > 
> > I'm using duplicity 0.6.24 on the server to backup to Amazon S3. To do the
> > backup, I'm using backupninja that runs duplicity like this:
> > 
> >     duplicity cleanup --force --s3-use-new-style --volsize 100
> >     --no-print-statistics --ssh-options '' --encrypt-key <somekey>
> >     --full-if-older-than 30D --extra-clean --archive-dir
> >     /var/cache/backupninja/duplicity s3+http://<some aws bucket>
> > 
> >     duplicity remove-older-than 60D --force --s3-use-new-style --volsize 100
> >     --no-print-statistics --ssh-options '' --encrypt-key <some key>
> >     --full-if-older-than 30D --extra-clean --archive-dir
> >     /var/cache/backupninja/duplicity s3+http://<some aws bucket>
> > 
> >     duplicity  --s3-use-new-style --volsize 100 --no-print-statistics
> >     --ssh-options '' --encrypt-key <some key> --full-if-older-than 30D
> >     --extra-clean --archive-dir /var/cache/backupninja/duplicity  --exclude
> >     '/home/*/.gnupg' --exclude '/root/.gnupg' --exclude
> >     '/var/cache/backupninja/duplicity' 
> >     --include '/var/backups/mysql/sqldump/' --exclude '**' /
> >     s3+http://<aws bucket>
> > 
> > And all works fine, I can list the files and everything using duplicity. 
> > It's
> > great. The thing is when I want to recover a file older than the last full
> > backup (recover from dates after the last full backup works fine). Then, it
> > fails with:
> > 
> >     duplicity restore --file-to-restore <file> --time 2015-10-12 
> > 's3+http://<aws bucket>' /tmp/restore
> >     Local and Remote metadata are synchronized, no sync needed.
> >     Last full backup date: Tue Nov 10 01:20:30 2015
> >     <file> not found in archive, no files restored.
> > 
> > The thing is that the file is in the archive for backups previous than the 
> > last
> > full backup. I thought that the "remove-older-than 60D ..." makes duplicity
> > keep the last 2 full backups (as I'm doing "--full-if-older-than 30D") and 
> > I'd
> > be able to restore those files.
> > 
> > It seems all the duplicity files are there for previous full backups in the
> > amazon S3 bucket, but I found the last full backup has a file named:
> >     duplicity-full-signatures.20151110T042030Z.sigtar.gpg
> > 
> > and previous backups don't. If not for that file, all other files from 
> > previous
> > backups seem to be there.
> > 
> > Oh, and I'm running the restore on duplicity 0.7.05.
> > 
> > Is there something wrong on what I'm doing to backup or try to restore the
> > files? Does anyone have any idea on what to try?
> > 
> > 
> 
> using --extra-clean removes the signatures and essentially the ability to 
> list/selectively restore/increment remote backups.

Oh, great, so if I remove that argument what I've tried will work in the future?

> 
> you should be able to restore everything (w/o parameter --file-to-restore) 
> from a signatureless chain though.

Ohh, that is great! Will try that!




Thanks a lot,
Rodrigo