Re: [Duplicity-talk] decryption failure in duplicity replicate

[zga9uhnq4g]

On 2021-08-25 02:14, edgar.soldin-at-web.de |duplicity-talk| wrote:
> On 25.08.2021 10:51, Jeffrey Walton via Duplicity-talk wrote:
> > On Tue, Aug 24, 2021 at 3:35 AM zga9uhnq4g--- via Duplicity-talk
> SNIP
> > This may be helpful to use in your script. I use it to trigger a full
> > backup every three months to help keep backup sets manageable. I think
> > it would have helped you since you would have a full backup to use
> > from July 1.
> >
> > day=$(date +%d)
> > if [ "${day}" = "01" ];
> > then
> >      month=$(date +%m)
> >      case ${month} in
> >          01|04|07|10)
> >            full_backup=full
> >            ;;
> >          *)
> >            ;;
> >      esac
> > fi
> >
> > ...
> >
> > if ! duplicity ${full_backup} <other params ...> ;
> > then
> >      echo "Failed to backup"
> >      exit 1
> > fi
> hey Jeff,
>
> how is that different form duplicity's
> "
> --full-if-older-than time
> Perform a full backup if an incremental backup is requested, but the latest 
> full backup in the collection is older than the given time. See the TIME 
> FORMATS section for more information.
> "
> parameter?
>
> ..ede

Yeah, I added --full-if-older-than time 1M on 2021-02-09, after I 
realized my backup chain had 57 incremental backup sets, so I do have 6 
more recent full backups.  I discovered the problem in the first full 
backup when I tried to replicate all the backup sets to Google Drive 
which has more space.  I'm trying to fix it because I'd still like to 
replicate everything if I can.  I'm only using duplicity to backup 
"important" stuff offsite (I also use rdiff-backup for onsite backups), 
so I want to keep a year or two of old backups.

BTW, I'm thinking of changing to --full-if-older-than time 1W once I get 
the backup replicated to Google Drive or Box so that --remove-older-than 
will remove more often (it can't remove a full until it can remove all 
the increments that depend on it) .

    - Peter