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

[Jeffrey Walton]

On Wed, Aug 25, 2021 at 5:14 AM <edgar.soldin@web.de> 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
>
> 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?

We wanted to ensure we had a full backup every three months on the
first of the month. The easiest path to the goal was the 'full'
option. Otherwise, the day of the full backup is a moving target.

Jeff