similar to: how to connect to rsyncd via forwarded ssh port?

Hi list! I'm trying to use rsync to do a regular remote backup of a 450GB sized container file located on my squeeze server onto a colocated QNap NAS device. Both use rsync 3.0.7. While this setup works for most files, it fails on this large file (see log below). I'm already trying to help rsync using "-P" to indicate that rsync should reuse the current copy and not trying

Hi All, I must not understand the uid/gid line in rsyncd.conf. If someone could briefly point out where I've gone wrong, I'd appreciate it. I've created a special user to backup a server which has some users who don't want all their files backed up, so I'm trying to address their concerns by using the uid= and gid= lines in rsyncd.conf to have the rsyncd run with

hello, I get some error messages when using BackupPC with rsyncd-style backup: - on the backup server : BackupPC 2.1.2, using its own rsync perl module - on the box being backed up : rsync 2.6.6 , runing as a daemon (rsyncd) the area to be backed up is rather big : ~120 Gb the rsyncd daemon is configured with a big timeout = 7200 a) this is what I get on the backup server

Hello list! I want to try to sync files from one SUN box to another. Both running rsync version 2.5.5 protocol version 26 whenever I try to run the command: [root@server1:/qdmsfs]# rsync -avvv -e ssh /qdmsfs/test/ server2:/ qdmsfs/test I receive the messages: opening connection using ssh server2t rsync --server -vvvlogDtpr . / qdmsfs/test sh: select: Bad file number rsync: connection

Hi, This is a very simple question I realise, but I hope maybe someone can just help me out. I am trying to do a very simple thing, just transfer a file from machine A to machine B using rsync with ssh. This is what i'm typing: bash-2.03# rsync -avvv --rsh="ssh -l tdf" tdf@machine.niss.ac.uk:/export/home/tdf/demofile.html demofile.html This is what I get: opening connection

I want to set up rsyncd to expose the whole drive read-only to BackupPC running on another machine. So I need to set selinux to allow this. According to the Fedora wiki I can do so like this: setsebool -P rsync_disable_trans 1 <https://fedoraproject.org/wiki/SELinux/rsync> But when I run the command on CentOS 7.3 it tells me that this bool is not defined. So what do I do now?

Gang, I've read the manual(s), surfed google, spent about 5 hours on this, to no avail.... I'm trying to run rsync in server mode and it appears to start normally, but it refuses all connections (refuses connection when I tried telnetting in on localhost 873!). I've turned off all firewalls on this server (do I dare tell you guys that?...), which is fine: it is on a local network. I

I am interested in understanding the thing with BackupPC. What does it have compared to basic rsync? - It has a webui Is it like a central backup server? if so, how it works with windows clients(if it is?) Just want to make sure.. I understood right. Why did you choose this over other software? Thanks, Eliezer On 20/09/2015 16:51, Timothy Murphy wrote: > I'd be interested in any

I'd be interested in any corrections or comments on the following instructions (basically for myself): We assume that BackupPC has been installed: sudo yum install BackupPC 1. BackupPC must be run by the user backuppc. Accordingly the lines User apache Group apache in /etc/httpd/conf/httpd.conf should be changed to User backuppc Group backuppc 2. The user backuppc must be able to

There is an upgraded BackupPC in the testing repository. It is version 3.0.0, which was released in January. The setup differences between version 2.1.2 and this version is that some file directories have shifted locations: 1. /var/lib/backuppc/conf is now instead /etc/BackupPC/ 2. /var/lib/backuppc/log is now /var/log/BackupPC =============================== If you are upgrading ... you

Fabian Arrotin wrote: >> This message occurs in the Perl script >> /usr/share/BackupPC/bin/BackupPC : >> >> my $sockFile = "/var/run/BackupPC/BackupPC.sock"; >> unlink($sockFile); if ( !bind(SERVER_UNIX, sockaddr_un($sockFile)) >> ) { print(LOG $bpc->timeStamp, "unix bind() failed: $!\n"); >> exit(1); } >> >> As far as

When I try to start BackupPC with "sudo systemctl restart backuppc" on my CentOS-7 server (running kernel 3.10.0-229.14.1.el7.x86_64) I get the following error in /var/log/BackupPC/LOG 2015-09-26 13:58:14 Reading hosts file 2015-09-26 13:58:14 unix bind() failed: No such file or directory This message occurs in the Perl script /usr/share/BackupPC/bin/BackupPC : my $sockFile

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 26/09/15 16:16, Timothy Murphy wrote: > When I try to start BackupPC with "sudo systemctl restart > backuppc" on my CentOS-7 server (running kernel > 3.10.0-229.14.1.el7.x86_64) I get the following error in > /var/log/BackupPC/LOG > > 2015-09-26 13:58:14 Reading hosts file 2015-09-26 13:58:14 unix > bind() failed: No

Hello, i386 Platform; FreeBSD v. 7.2 O/S I am experiencing repeated rsync failures, rsyncing from a remote site to which I have no access. >From the client side I can run truss to collect system calls truss -faedD -o truss.out -s 64 /usr/local/bin/rsync -avvv --contimeout=1200 --port=33444 ftp.wwwxxx.org::ftp . >> rsynclog & >From truss.out => 44755: 4492.350089813

1. I'm running - or trying to run - BackupPC under Centos-5.2, and have been looking at various BackupPC HOWTOs and tutorials. I see that the "Falko" tutorial at <http://www.howtoforge.com/linux_backuppc> recommends (on page 3) that one should enter one's username, "falko" in this case, as the user in /etc/BackupPC/hosts . Other tutorials suggest one should use

Dear Developers First of all I would love to thank you for a nice tool I had been using rsync within backuppc project to backup my remote hosts. It had been working fine until the moment (as I think) whenever I moved RAID to another box and now the source directory (/raid/research) is now actually NFS mounted. Now backup (rsync process) stalls and sleeps indefinitely On the backup server:

On Sat, Sep 26, 2015 at 08:12:40PM +0100, Timothy Murphy wrote: > I don't really understand this. > The perl script wants to create /var/run/BackupPC/BackupPC.sock > which it seems it cannot do unless /var/run/BackupPC/ exists. > If as you say this disappears on re-booting, > I don't see how this program could work. Seems like a packaging bug in EPEL. Fedora does this

kpolberg at olberg.name wrote: >>> 2. The graphical interface seems to be treated as an extra, >>> but what other way is there of accessing BackupPC? >>> Is there a CLI approach? >>> If so, where is the list of transfer requests kept? > 2. You can do all operations through CLI, all of it is mentioned in the > documentation. >

Hi! I try to use batch mode to send only the difference between two packed CDs by email over a slow line. I create the diff with: rsync -avvv --write-batch=rs CD-ROM-V6.6.32.zip CD-ROM-V6.6.31.zip where alfred:/Auslieferung/CD # l -n -rw-r--r-- 1 0 0 453248121 Sep 2 16:22 CD-ROM-V6.6.31.zip -rw-r--r-- 1 0 0 407416499 Sep 29 13:39 CD-ROM-V6.6.32.zip resulting

Ulf Volmer wrote: Thanks for your response, which clarifies matters for me. >> I have a couple of questions that this raises. >> 1. Why exactly does backuppc want to ssh to root? > To enable access to all of the files on the client. >> Is this just a way of running BackupPC as root? > Why do you want this? It's not required to run backuppc as user root. I