tags 572721 - moreinfo
thanks

Olivier Berger <[email protected]> writes:

>
> Will double check by issueing a backupninja backup trying to add some
> verbosity.
>

I've checked in order to confirm, and here's a copy of logs of duplicity
launched through backupninja, after having removed ~/.cache/duplicity.

I launched backupninja --run /etc/backup.d/90.dup and got these logs :

Debug: check_perms /etc/backup.d
Debug: perms: drwxrwx---
Debug: gperm: rwx
Debug: wperm: ---
Debug: check_perms /etc/backup.d/90.dup
Debug: perms: -rw-------
Debug: gperm: ---
Debug: wperm: ---
Info: >>>> starting action /etc/backup.d/90.dup (because of --now)
Debug: yes
Debug: ssh  -o PasswordAuthentication=no machine -l backup 'echo -n 1'
Debug: Connected to machine as backup successfully
Debug: Data will be encrypted using symmetric encryption.
Debug: Data won't be signed.
Debug:  duplicity cleanup --force --extra-clean --verbosity 5 
--no-print-statistics --scp-command 'scp ' --sftp-command 'sftp ' 
--full-if-older-than 30D 
scp://bac...@machine//mnt/backups/dupbackups/laptop_slash

 (... Here, you may notice some tweaks I've made to make sure the archive
 dir won't be filled : --force and --extra-clean.
 Now : duplicity tells it quite well : it will use
 /root/.cache/duplicity/b52dc54e5d6855e59f330cb93cc7096a to store
 archives of previous backups )

Debug: Using archive dir: 
/root/.cache/duplicity/b52dc54e5d6855e59f330cb93cc7096a Using backup name: 
b52dc54e5d6855e59f330cb93cc7096a Import of duplicity.backends.botobackend 
Succeeded Import of duplicity.backends.localbackend Succeeded Import of 
duplicity.backends.hsibackend Succeeded Import of duplicity.backends.ftpbackend 
Succeeded Import of duplicity.backends.sshbackend Succeeded Import of 
duplicity.backends.webdavbackend Succeeded Import of 
duplicity.backends.imapbackend Succeeded Import of 
duplicity.backends.tahoebackend Succeeded Import of 
duplicity.backends.rsyncbackend Succeeded Import of 
duplicity.backends.cloudfilesbackend Succeeded Import of 
duplicity.backends.giobackend Succeeded Main action: cleanup 
================================================================================
 duplicity 0.6.06 (October 29, 2009) Args: /usr/bin/duplicity cleanup --force 
--extra-clean --verbosity 5 --no-print-statistics --scp-command scp 
--sftp-command sftp --full-if-older-than 30D 
scp://bac...@machine//mnt/backups/dupbackups/laptop_slash Linux inf-8657 
2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 /usr/bin/python 2.5.5 
(r255:77872, Feb 1 2010, 19:53:42) [GCC 4.4.3] 
================================================================================
 Running 'sftp -oServerAliveInterval=15 -oServerAliveCountMax=1 bac...@machine' 
(attempt #1) sftp command: 'mkdir /mnt/backups/dupbackups/laptop_slash' sftp 
command: 'cd /mnt/backups/dupbackups/laptop_slash' sftp command: 'ls -1' 
Synchronizing remote metadata to local cache... 

 (... here the copying with sftp of distant backup files to local
 archive dir )

Copying duplicity-full-signatures.20100304T170659Z.sigtar to local cache. Using 
temporary directory /tmp/duplicity-8x99TH-tempdir Running 'sftp 
-oServerAliveInterval=15 -oServerAliveCountMax=1 bac...@machine' (attempt #1) 
sftp command: 'get 
/mnt/backups/dupbackups/laptop_slash/duplicity-full-signatures.20100304T170659Z.sigtar.gpg
 /tmp/duplicity-8x99TH-tempdir/mktemp-knuNXY-1' Deleting 
/tmp/duplicity-8x99TH-tempdir/mktemp-knuNXY-1 Copying 
duplicity-full.20100104T094512Z.manifest to local cache. Running 'sftp 
-oServerAliveInterval=15 -oServerAliveCountMax=1 bac...@machine' (attempt #1) 
sftp command: 'get 
/mnt/backups/dupbackups/laptop_slash/duplicity-full.20100104T094512Z.manifest.gpg
 /tmp/duplicity-8x99TH-tempdir/mktemp-p6O2h3-2' Deleting 
/tmp/duplicity-8x99TH-tempdir/mktemp-p6O2h3-2 Copying 
duplicity-full.20100304T170659Z.manifest to local cache. Running 'sftp 
-oServerAliveInterval=15 -oServerAliveCountMax=1 bac...@machine' (attempt #1) 
sftp command: 'get 
/mnt/backups/dupbackups/laptop_slash/duplicity-full.20100304T170659Z.manifest.gpg
 /tmp/duplicity-8x99TH-tempdir/mktemp-dOFTol-3' Deleting 
/tmp/duplicity-8x99TH-tempdir/mktemp-dOFTol-3 Copying 
duplicity-inc.20100104T094512Z.to.20100104T200008Z.manifest to local cache. 
Running 'sftp -oServerAliveInterval=15 -oServerAliveCountMax=1 bac...@machine' 
(attempt #1) sftp command: 'get 
/mnt/backups/dupbackups/laptop_slash/duplicity-inc.20100104T094512Z.to.20100104T200008Z.manifest.gpg
 /tmp/duplicity-8x99TH-tempdir/mktemp-RwSMXG-4' Deleting 
/tmp/duplicity-8x99TH-tempdir/mktemp-RwSMXG-4 

And so on, and so forth.

I've only copied, bellow, the invocation traces of duplicity : no --archive-dir 
added,
but it will continue using it...

================================================================================
duplicity 0.6.06 (October 29, 2009) Args: /usr/bin/duplicity
remove-older-than 60D --force --verbosity 5 --no-print-statistics
--scp-command scp --sftp-command sftp --full-if-older-than 30D
scp://bac...@machine//mnt/backups/dupbackups/laptop_slash Linux inf-8657
2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686
/usr/bin/python 2.5.5 (r255:77872, Feb 1 2010, 19:53:42) [GCC 4.4.3]
================================================================================
 

================================================================================
duplicity 0.6.06 (October 29, 2009) Args: /usr/bin/duplicity --verbosity
5 --no-print-statistics --scp-command scp --sftp-command sftp
--full-if-older-than 30D --exclude /proc --exclude /sys --exclude /mnt
--exclude /home --exclude /tmp --exclude /var/lib/libvirt --exclude
/var/lib/postgresql --exclude /media --exclude /root/.cache/duplicity
--include /bin /boot /cdrom /dev /etc /home /initrd.img /initrd.img.old
/lib /lost+found /media /mnt /opt /proc /root /sbin /selinux /srv /sys
/tmp /usr /var /vmlinuz /vmlinuz.old --exclude backupninja.log home.txt
installed_packages list.txt python-subvertpy_0.7.2-1+b1_i386.deb recup
rhythmbox.patch /
scp://bac...@machine//mnt/backups/dupbackups/laptop_slash Linux inf-8657
2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686
/usr/bin/python 2.5.5 (r255:77872, Feb 1 2010, 19:53:42) [GCC 4.4.3]
================================================================================

So I'm pretty sure duplicity now uses this archive dir
systematically... hence the need for the adequate options like
--extra-clean to make sure its cache doesn't fill up.

Hope this helps.

Best regards
-- 
Olivier BERGER 
(OpenPGP: 1024D/B4C5F37F)
http://www.olivierberger.com/weblog/



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to