BackupPC-users

Re: [BackupPC-users] BackupPC v4 and rsync for localhost

2017-06-15 09:54:33
Subject: Re: [BackupPC-users] BackupPC v4 and rsync for localhost
From: Michael Stowe <mstowe AT chicago.us.mensa DOT org>
To: "General list for user discussion, questions and support" <backuppc-users AT lists.sourceforge DOT net>
Date: Thu, 15 Jun 2017 08:53:25 -0500

On 2017-06-15 03:25, Daniel Berteaud wrote:

Hi there.

Using BackupPC since v2, I used to be able to BackupPC the host itself (the one running BackupPC) using rsync by simply modifying $Conf{RsyncClientCmd} (to something like ‘/usr/bin/sudo $rsyncPath $argList’, and same for $Conf{RsyncClientRestoreCmd}). THis worked with BackupPC v3 too.

How can the same be done with BackupPC v4 now that RsyncClientCmd isn't used anymore ? Setting RsyncSshArgs to undef does't work as it'll try to run with ssh (but without a full path), eg

[root@gerard ~]# sudo -u backuppc /usr/share/BackupPC/bin/BackupPC_dump -f -vv gerard Backup type: type = full, needs_full = , needs_incr = 1, lastFullTime = 1495674113, opts{f} = 1, opts{i} = , opts{F} = cmdSystemOrEval: about to system /bin/ping -c 1 -w 3 localhost cmdSystemOrEval: about to system /bin/ping -c 1 -w 3 localhost CheckHostAlive: ran ‘/bin/ping -c 1 -w 3 localhost’; returning 0.013 XferLOG file /var/lib/BackupPC//pc/gerard/XferLOG.190.z created 2017-06-15 10:22:29 Backup prep: type = full, case = 6, inPlace = 1, doDuplicate = 0, newBkupNum = 190, newBkupIdx = 35, lastBkupNum = , lastBkupIdx = (FillCycle = 0, noFillCnt = 20) _bpc_progress_state_ backup / Running: /usr/bin/rsync_bpc --bpc-top-dir /var/lib/BackupPC/ --bpc-host-name gerard --bpc-share-name / --bpc-bkup-num 190 --bpc-bkup-comp 3 --bpc-bkup-prevnum -1 --bpc-bkup-prevcomp -1 --bpc-bkup-inode0 1 --bpc- attrib-new --bpc-log-level 1 --rsync-path=/usr/bin/rsync --super --recursive --protect-args --numeric-ids --perms --owner --group -D --times --links --hard-links --delete --delete-excluded --partial --log-format =log:\ %o\ %i\ %B\ %8U,%8G\ %9l\ %f%L --stats --checksum --timeout=72000 --exclude=/dev --exclude=/proc --exclude=/sys --exclude=\*lost+found --exclude=/mnt/\* --exclude=/media/\* --exclude=/tmp --exclude=/var/t mp --exclude=/var/lib/libvirt/backup --exclude=/var/lib/BackupPC --exclude=/var/lib/libvirt/images --exclude=/var/lib/libvirt/iso --exclude=/var/lib/libvirt/qemu --exclude=/var/run --exclude=/selinux --exclude=/ var/lib/yum/yumdb/ --exclude=/cgroup/ --exclude=/var/lock/lvm/ localhost:/ / full backup started for directory / started full dump, share=/ Xfer PIDs are now 16424 xferPids 16424 This is the rsync child about to exec /usr/bin/rsync_bpc cmdExecOrEval: about to exec /usr/bin/rsync_bpc --bpc-top-dir /var/lib/BackupPC/ --bpc-host-name gerard --bpc-share-name / --bpc-bkup-num 190 --bpc-bkup-comp 3 --bpc-bkup-prevnum -1 --bpc-bkup-prevcomp -1 --bpc-bkup-inode0 1 --bpc-attrib-new --bpc-log-level 1 --rsync-path=/usr/bin/rsync --super --recursive --protect-args --numeric-ids --perms --owner --group -D --times --links --hard-links --delete --delete-excluded --partial --log-format=log:\ %o\ %i\ %B\ %8U,%8G\ %9l\ %f%L --stats --checksum --timeout=72000 --exclude=/dev --exclude=/proc --exclude=/sys --exclude=\*lost+found --exclude=/mnt/\* --exclude=/media/\* --exclude=/tmp --exclude=/var/tmp --exclude=/var/lib/libvirt/backup --exclude=/var/lib/BackupPC --exclude=/var/lib/libvirt/images --exclude=/var/lib/libvirt/iso --exclude=/var/lib/libvirt/qemu --exclude=/var/run --exclude=/selinux --exclude=/var/lib/yum/yumdb/ --exclude=/cgroup/ --exclude=/var/lock/lvm/ localhost:/ / rsync_bpc: Failed to exec ssh: No such file or directory (2) Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 1 inode rsync error: error in IPC code (code 14) at pipe.c(84) [Receiver=3.0.9.8]

Running:

  • CentOS 6

  • BackupPC v4.1.3

  • rsync-bpc 3.0.9.8

  • BackupPC::XS 0.56

DANIEL BERTEAUD

I looked on my own setup to answer this question, since I used a similar method under 3.x and have been backing up the local systems under 4.x since the alpha versions.

Turns out I just use a pretty vanilla rsync/ssh setup, and set up ssh keys so the box can log into itself without issues.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

ADSM.ORG Privacy and Data Security by KimLaw, PLLC