Re: [Duplicity-talk] How to prevent .cache from filling up root partition?

[edgar . soldin]

the archive dir as it is called has nothing to do with the temp space needed. 
use the '--archive-dir' parameter to point duplicity to a different, but secure 
location with enough space if needed.
the manpage holds some info about the archive dir. look for the above mentioned 
parameter's explanation.
 http://duplicity.nongnu.org/duplicity.1.html

..ede/duply.net


On 29.09.2015 05:18, Kevin Carr wrote:
> I have created .cache as a link to a drive with a lot of space in the past
> as a quick way around this.
> 
> On Mon, Sep 28, 2015, 10:07 PM Scott Classen <address@hidden> wrote:
> 
>> Hello,
>>
>> I'm having problems getting duply to perform the initial full backup to
>> Amazon S3
>>
>> My source directory is ~4TB
>>
>> These are the versions of everything I'm running:
>>
>> duply version 1.10.1
>> Using installed duplicity version 0.7.05, python 2.6.6, gpg 2.0.14 (Home:
>> ~/.gnupg), awk 'GNU Awk 3.1.7', grep 'grep (GNU grep) 2.20', bash
>> '4.1.2(1)-release (x86_64-redhat-linux-gnu)'.
>>
>>
>> I think the main problem is that duply/duplicity is writing a ton of stuff
>> to .cache which is filling up the root partition and crashing the computer.
>> I've set TEMP_DIR=/home-old/duplicity which has a large partition (~2TB
>> available space) that I can use for temporary files. Is there any way to
>> get .cache to use TEMP_DIR?
>>
>>
>> Here is the --preview output:
>>
>> # duply home backup --preview
>> Start duply v1.10.1, time is 2015-09-28 16:33:13.
>> Using profile '/etc/duply/home'.
>> Using installed duplicity version 0.7.05, python 2.6.6, gpg 2.0.14 (Home:
>> ~/.gnupg), awk 'GNU Awk 3.1.7', grep 'grep (GNU grep) 2.20', bash
>> '4.1.2(1)-release (x86_64-redhat-linux-gnu)'.
>> Autoset found secret key of first GPG_KEY entry '' for signing.
>> -- Run cmd -- Checking TEMP_DIR '/home-old/duplicity' is a folder --
>> test -d /home-old/duplicity 2>&1
>> -- Run cmd -- Checking TEMP_DIR '/home-old/duplicity' is writable --
>> test -w /home-old/duplicity 2>&1
>> -- Run cmd -- Test - Encrypt to '' & Sign with '' --
>> echo xxxxx | gpg --sign --default-key --passphrase-fd 0 --batch -r
>> --status-fd 1 -o /home-old/duplicity/duply.32699.1443483193_ENC -e
>> /usr/bin/duply 2>&1
>> -- Run cmd -- Test - Decrypt --
>> echo stan_ley123 | gpg --passphrase-fd 0 --batch -o
>> /home-old/duplicity/duply.32699.1443483193_DEC -d
>> /home-old/duplicity/duply.32699.1443483193_ENC 2>&1
>> -- Run cmd -- Test - Compare --
>> test "$(cat '/usr/bin/duply')" = "$(cat
>> '/home-old/duplicity/duply.32699.1443483193_DEC')" 2>&1
>> Cleanup - Delete '/home-old/duplicity/duply.32699.1443483193_*'(FAILED)
>>
>> --- Start running command PRE at 16:33:13.421 ---
>> . /etc/duply/home/pre
>> --- Finished state OK at 16:33:13.450 - Runtime 00:00:00.029 ---
>>
>> --- Start running command BKP at 16:33:13.475 ---
>> TMPDIR='/home-old/duplicity' PASSPHRASE=xxxxxxxx
>> FTP_PASSWORD='xxxxxxxxxxxxx' duplicity --name duply_home --encrypt-key
>> xxxxxx --sign-key xxxxx --verbosity '4' --s3-use-rrs --exclude-filelist
>> '/etc/duply/home/exclude' '/home' 's3://
>> address@hidden/xxxxxxxxxx'
>> --- Finished state OK at 16:33:13.561 - Runtime 00:00:00.086 ---
>>
>> --- Start running command POST at 16:33:13.587 ---
>> . /etc/duply/home/post
>> --- Finished state OK at 16:33:13.617 - Runtime 00:00:00.030 ---
>>
>>
>> Thanks,
>> Scott
>>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>
> 
> 
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>