similar to: BackupPC 1.03 released (backup to disk for WinXX/Linux using Samba)

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

I just released version 2.0.0beta0 of BackupPC on SourceForge, see http://backuppc.sourceforge.net/ What is BackupPC? It is an enterprise-grade open-source package for backing up WinXX and *nix systems to disk. It supports transport via SMB, tar and now rsync over rsh/ssh and rsyncd. The backend features hard-linking of any identical files (not just files with the same name) and

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

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

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 never thought it would happen to me, but it did... I have read threads about slow copies from WinXX to Linux/Samba on the list in the past, but I don't recall a concise answer regarding what the cause was. THE PROBLEM: Trying to copy an 8 meg file from Win95 to my Linux/Samba box (named "Nemesis" - for good reason), the transfer speed slows to a crawl. The Win95 copy dialog box

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

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

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

On 9/18/2015 8:39 AM, Timothy Murphy wrote: > Bowie Bailey wrote: > >> On 9/13/2015 10:58 AM, Timothy Murphy wrote: >>> I take it then that there is no CLI method >>> of setting up and running BackupPC ? >> Sure there is. All of the configuration is stored in text config >> files. There is a main config file for global options and each host has >>

Hi. I've installed BackupPC 3.1.0 from Testing repository, to Cent OS 5.2 x86_64, and I am hitting an SE Linux denial - the httpd cannot talk to the BackupPC socket: type=AVC msg=audit(07/31/2008 17:18:53.623:410) : avc: denied { connectto } for pid=11767 comm=httpd path=/var/log/BackupPC/BackupPC.sock scontext=user_u:system_r:httpd_t:s0 tcontext=user_u:system_r:initrc_t:s0

On 16/10/2019 09:07, Alessandro Baggi wrote: > On 16/10/19 02:31, Ranbir wrote: >> Hello Everyone, >> >> Has anyone tried to install BackupPC v4 on CentOS 8 from epel? I just >> did and this happened: >> >> [root at resurrect ~]# dnf --enablerepo epel install BackupPC >> Last metadata expiration check: 0:18:41 ago on Tue 15 Oct 2019 >> 08:03:59 PM