similar to: is it possible to continue rsync after network interruption?

I've running a rsyncd and ssh port forwarding (-R 12345:localhost:873 backup@server) on a client because the client should not reachable but over ssh. The rsyncd should acessible because I can backup and restore files with backuppc (a wonderfull program which use perl::rsync) And I can "ssh -p 12345 backup@localhost" to this client too. If I try to connect (from the machine/user

Hi, I want to disable windows suspend before starting backup by rsync. My rsyncd.conf: ----------------- max connections = 6 log file = /var/log/backup-service.log read only = false write only = false transfer logging = no list = false max verbosity = 6 pre-xfer exec = powercfg /H off [C] path = /cygdrive/c/ [D] path = /cygdrive/d/ ----------------- Unfortunately that didn't work.

Hi there list :) I use backuppc to take backup of a bunch of hosts, but I ran into problems with the last one I set up, I can't find anything that is different on this one...but it won't work... So any hints would be greatly appreciated, here are the files ryncd.conf: log file=/var/log/rsyncd pid file=/var/run/rsyncd.pid [all] comment = All disk path = / use

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

Hi, I've configured 'backuppc' to transfer files via rsyncd, with enabled checksums. Whith one of the shares I get the error (in syslog): --------------------------------------------------------------------- robbe rsyncd[2183]: ERROR: out of memory in receive_sums [sender] robbe rsyncd[2183]: rsync error: error allocating core memory buffers (code 22) at util2.c(106)

I hear that backuppc does *not* have a native *Doze client. On the other hand, I know amanda's been around a long time, and it does. Opinions on amanda, folks? mark

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

Hello, Been working on this for a couple days and I am stuck! Followed the CentOS WIKI on BackupPC to the letter. It may be outdated, not sure. I also looked at the tutorial on HowToForge. I'm trying to get a windows client to backup via smb. I created the user 'backuppc' on the windows client with admin priviledges. I can map the drive/share from my CentOS Samba server using

I finally got BackupPC working under Centos-7.1 after several hours of pain. I had been running it for several years under CentOS-6, and probably CentOS-5, but there seem to me to have been several new issues that arise with CentOS-7. In my experience, the official documentation on this, <http://backuppc.sourceforge.net/faq/BackupPC.html>, is more or less useless unless you have a very long

I'm running BackupPC under Centos-5.2. 1. Will BackupPC backup files in NFS-mounted directories? If so, is there any simple way of preventing this? 2. I have seen it suggested that it is not a good idea to backup onto a partition on the same drive as the BackupPC server? Is that true? If so, is a partition on a separate drive on the same machine also bad? Ps Apologies if this has been

Hi, I've installed cygwin and rsync on a vista client and want backup it to a Linux server: On client side (vista) I use rsync 3.0.4 (protocol version 30) Capabilities: 64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, no IPv6, batchfiles, inplace, append, ACLs, no xattrs, iconv, symtimes On server side (linux) I have rsync 3.0.3

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

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

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

On 9/20/2015 6:00 PM, Eliezer Croitoru wrote: > I am interested in understanding the thing with BackupPC. > What does it have compared to basic rsync? its a full blown backup service for any number of client hosts, it maintains a pool of full and incremental backups going back as far as you care, and this pool is fully dedupped to reduce its size. it uses rsync to fetch files from the

On 09/13/2015 03:48 PM, Timothy Murphy wrote: > Timothy Murphy wrote: > >> I thought I'd write a 1-page note to myself of the steps I took, >> in preparation for CentOS-8... >> I have a couple of questions that this raises. >> >> 1. Why exactly does backuppc want to ssh to root? >> Is this just a way of running BackupPC as root? >> >> 2.

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

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

For some time now i have been running BackupPC 3.1.0 on CentOS 5.1 x86_64 however after upgrading to CentOS 5.2 BackupPC will not start. "sudo /etc/init.d/backuppc start" return OK but there is no BackupPC processes. This fails also. # sudo -u backuppc /usr/bin/BackupPC -d # echo $? 0 This succeeds, but of course does not fork. # sudo -u backuppc /usr/bin/BackupPC So for some

Hi all, I installed BackupPC on one of my Centos 5.4-machines following the wiki at http://wiki.centos.org/HowTos/BackupPC#head-725ed151d366bcf182cea92f765c373900cfc9dc, where BackupPC is installed from the c5-testing repo. root at mach012 ~/ [0]# rpm -qa backuppc backuppc-3.1.0-1.el5.centos root at mach012 ~/ [0]# Seeing how there's been some updates to BackupPC in the near past, I