similar to: BackupPC 2.0.0 released (backup to disk for WinXX/Linux/Unix)

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

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

Any feedback on this patch and the possibility of getting it into CVS or the patches directory? Thanks, Craig ---------- Forwarded message ---------- To: jw schultz <jw@pegasys.ws> From: Craig Barratt <cbarratt@users.sourceforge.net> cc: rsync@lists.samba.org Date: Sat, 01 May 2004 17:06:10 -0700 Subject: Re: setting checksum_seed jw schultz writes: > > > There was some

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

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

On 09/13/2015 01:35 PM, Timothy Murphy wrote: > 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. It is also possible to run the backup running the rsyncd- daemon on the client. > Is this just a way of running BackupPC as root? Why do you want this? It's not required to run

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

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