[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] .Cache & duplicity collection-status

From: edgar . soldin
Subject: Re: [Duplicity-talk] .Cache & duplicity collection-status
Date: Mon, 12 Jul 2021 15:29:02 +0200
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1

On 12.07.2021 14:53, Сергей Цаболов via Duplicity-talk wrote:
> I mean: cron job for duplicity incremental run every day
> 10 21 * * * duplicity incremental --no-encryption  
> *--exclude=/root/.cache/duplicity* --exclude=/run --exclude=/dev 
> --exclude=/proc --exclude=/sys --exclude=/mnt --exclude=/media --exclude=/tmp 
> --exclude=/var/spool --exclude=/var/cache --exclude=/var/tmp 
> --exclude=/swap.img / file:///srv/duplicity/
> Available space in disk take once in 2021/07/10,  next day not enough space 
> for cached files because disk is full 100%.
> And second cron job once in the week can't finished :
> 30 4 * * sun duplicity full --no-encryption  --exclude=/run --exclude=/srv 
> --exclude=/dev --exclude=/proc --exclude=/sys --exclude=/mnt --exclude=/media 
> --exclude=/tmp --exclude=/var/spool --exclude=/var/cache --exclude=/var/tmp 
> --exclude=/swap.img / file:///srv/duplicity/

i notice you are not excluding mount point '/srv' where your backup is ending 
up! duplicity is not sticking to file system boundaries but backs up everything 
below the mount point you are giving it. this is backing up the backup location 
as well.

also the second run lacks the */root/.cache/duplicity* exclusion.

list your backups content 'duplicity list-current-files [options] [--time time] 
target_url' to make sure that you do include *archive dir* or *backup target*!

also. if you are not planning to backup *encrypted* and to *remote*, you might 
consider using another application as these are the main reasons to use 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]