lds

ok cosmetic errors have disappeared :) thanks

it may be because the rotation was not done correctly due to problems linked to the duplicity version by forcing two fulls I was able to return to a normal state

it seems that the fulls are no longer triggered I had to force the full backup with duply local full my conf MAX_FULL_BACKUPS=2 MAX_AGE=4W MAX_FULLBKP_AGE=2W DUPL_PARAMS="$DUPL_PARAMS --s3-endpoint-url http://xxxxxx --s3-region-name xxxx --full-if-older-than $MAX_FULLBKP_AGE"

it seems that the fulls are no longer triggered I had to force the full backup with duply local full

Hello ede It seems correct to me despite cosmetic errors on fetch duply local fetch etc/hosts /tmp/hosts Start duply v2.5.0dev, time is 2023-09-21 16:55:46. Using profile '/root/.duply/local'. Using installed duplicity version 2.1.1, gpg 2.2.19 (Home: /root/.gnupg), awk 'mawk 1.3.4 20200120', grep 'grep (GNU grep) 3.4', bash '5.0.17(1)-release (x86_64-pc-linux-gnu)'. Checking TEMP_DIR '/tmp' is a folder and writable (OK) Test - En/Decryption skipped. (GPG='disabled') --- Start running command FETCH...

ouhh big problems in 2.x duplicity duply local fetch etc/passwd /tmp/file CommandLineError: Invalid or missing action command and cannot be implied from the given arguments. ['--file-to-restore', 'etc/passwd', 'boto3+s3://xxxxxxxx', '/tmp/file'] --file-to-restore is deprecated in 2.1.0 and 'action' is mandatory (restore) this duplicity command works: duplicity restore --name test --no-encryption --verbosity 4 --s3-region-name=xxxx --s3-endpoint-url https://xxxxxxxxxx --restore-time now --path-to-restore...