similar to: BackupPC 2.0.0beta0 released - now supports rsync

I have just released the first version 0.10 of File::RsyncP to SourceForge. See: http://perlrsync.sourceforge.net File::RsyncP is a perl implementation of an Rsync client. It is compatible with Rsync 2.5.5 (protocol version 26). It can send or receive files, either by running rsync on the remote machine, or connecting to an rsyncd deamon on the remote machine. What use is File::RsyncP?

BackupPC version 2.0.0 has been released on SourceForge, see http://backuppc.sourceforge.net. New features include support for rsync/rsyncd and internationalization of the CGI interface (including English, French, Spanish and German). BackupPC a high-performance perl-based package for backing up linux, unix or WinXX PCs and laptops to a server's disk. BackupPC is highly configurable and

BackupPC version 2.0.0 has been released on SourceForge, see http://backuppc.sourceforge.net. New features include support for rsync/rsyncd and internationalization of the CGI interface (including English, French, Spanish and German). BackupPC a high-performance perl-based package for backing up linux, unix or WinXX PCs and laptops to a server's disk. BackupPC is highly configurable and

BackupPC version 1.5.0 has been released on SourceForge, see http://backuppc.sourceforge.net. BackupPC a high-performance perl-based package for backing up linux, unix or WinXX PCs and laptops to a server's disk. BackupPC is highly configurable and easy to install and maintain. No client SW is needed. BackupPC uses Samba's smbclient to extract files via SMB from WinXX clients, and uses

BackupPC version 1.03 has been released on SourceForge, see http://backuppc.sourceforge.net. BackupPC a high-performance perl-based package for backing up Linux and WinXX PCs and laptops to a server's disk. BackupPC is highly configurable and easy to install and maintain. It uses Samba's smbclient to extract files from clients, and uses Samba on linux clients to serve up shares (no

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

John, are you using c6? I have c7 and epel, nux repo and can't find this packages on these repo. Only backuppc on nux repo. Il 11/mag/2015 23:26, "John R Pierce" <pierce at hogranch.com> ha scritto: > On 5/11/2015 1:28 PM, Alessandro Baggi wrote: > >> To install backuppc perl is required, >> to install File::Rsync from cpan I must install gcc. >> >

I have been using backuppc (rsync protocol) to backup up a Linux web server onto a local server for a number of years. I recall that data volumes were quite low (about 40MB), regardless of whether I was doing full or incremental backups. I recently switched to both a new web server and backuppc server. Early morning traffic volumes when backuppc runs are much higher than expected - I have

On 5/11/2015 1:28 PM, Alessandro Baggi wrote: > To install backuppc perl is required, > to install File::Rsync from cpan I must install gcc. never met a unix that didn't come with Perl already installed, or as a base option Using CPAN on a package-based distribution can lead to conflicts, rather, you should install cpan modules from a repository, for instance, perl-File-RsyncP is

On Wed, 2015-07-15 at 16:29 -0400, m.roth at 5-cent.us wrote: > I hear that backuppc does *not* have a native *Doze client... It is simple to set up a rsyncd server under Cygwin / WinX to feed BackupPC. I normally install "full" cygwin to access rsyncd, but there is a limited client available. http://sourceforge.net/projects/backuppc/files/cygwin-rsyncd/3.0.9.0/ >From the

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

-----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

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

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

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

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. >

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

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