Re: [BackupPC-users] owner not shown after changing owner

[Klaas Vantournhout]

Hi, just some more info about this.

I noticed that when a host had one user in BackupPC 2.1.2, and I add 
more users after upgrade to version 3.0.0beta3, the line
"This PC is used by "
vanishes!  Altering the line back to only one user, shows the line again.

This is not the case when a PC original had multiple users in 2.1.2. 
Adding or removing users in such a host, always shows the line!

To my opinion this is a bug, but a tiny unimportant one ;-)

regards
Klaas

> I have checked the hosts file, and it looks clean.  I'm running 
> backupPC3.0.0-beta3.  The strange thing is that, the user himself can 
> login into the system, and sees his host.  There the host file 
> determines who gets access to which host, it must run correct, there 
> this works.  Is there an other place where host names are stored or host 
> names are determined?
> 
> Regards
> Klaas
> 
> Craig Barratt wrote:
>> Klaas writes:
>>
>>> Here I am again with another tiny problem.
>>>
>>> Lately I changed a host its owner by altering the host file.  What I 
>>> noticed now is that, when I look at the host itself, it does not show 
>>> the line
>>> "This PC is used by "
>>>
>>> Is there a way this can be explained?  I'm using 3.0.0beta3
>> Can't explain this.  Most likely a typo in the new hosts file?
>>
>> Craig
> 
> 



-- 
"Several billion trillion tons of superhot
exploding hydrogen nuclei rose slowly above
the horizon and managed to look small, cold
and slightly damp."
Douglas Adams - The Hitch Hickers
Guide to the Galaxy

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

[BackupPC-users] Schedule for per pc backup

[nilesh vaghela]

How can I make per pc schedule for backup purpose.

As I had 350 pc and want to keep maximum 4 pc to be connected concurrent.

--
Nilesh Vaghela
ElectroMech
Redhat Channel Partner and Training Partner
74, Nalanda Complex, Satellite Rd, Ahmedabad
25, The Emperor, Fatehgunj, Baroda.
www.electromech.info
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] how to update from 2.1.1

[Filipe]

I've followed a guide and I used apt-get install... when installing 
backuppc 2.1.1

and now what should I do?!
there's version 3 also out  :o

Nils Breunese (Lemonbit) wrote:

Filipe wrote:

I am running 2.1.1 with no major problems with 12 hosts for about 6 
months.

It is on a debian sarge system, what is the best procedure to update to
last 2.1.3 version?


Did you install using apt or using the archive directly from the 
BackupPC website? I you used apt (installed a .deb file) then you 
might want to ask the maintainer to create an updated package. I 
believe the layout in the Debian package is a bit different than the 
'original'. I don't know if you'll want to use the following procedure 
on a system that has BackupPC installed through a package manager.


Anyway, I'm just using the archive from the website and I upgraded 
from 2.1.2pl2 to 2.1.3 yesterday. Upgrading is not really different 
from installing.


1. Stop the backuppc service
2. Download the latest version
3. Unpack the archive
4. Run perl configure.pl in the unpacked directory
5. Start the backuppc service

Worked just fine for me. See the docs on the site if you need more 
detailed information on installing BackupPC.


Nils Breunese.


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
  


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] how to update from 2.1.1

[Nils Breunese (Lemonbit)]

Filipe wrote:

I've followed a guide and I used apt-get install... when installing  
backuppc 2.1.1

and now what should I do?!
there's version 3 also out  :o


You could contact the maintainer and ask if an update is in the works  
or maybe use Debian's Bug Tracker. I'm pretty sure you can also  
uninstall the BackupPC deb, download BackupPC 3.0.0 and point the  
installer to your previous config.


Nils Breunese.




PGP.sig
Description: Dit deel van het bericht is digitaal ondertekend
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Update to 3.0

[Klaas Vantournhout]

Hi Christophe,

I would not really worry about an update.  I have always updated without 
a single problem and this since version 1 of BackupPC.

If you install BackupPC, untar the file in a new directory (for 
backupreaasons if things go wrong, you should still have the old install 
dir of your previous version)

then do
/etc/init.d/backuppc stop
perl configure.pl

and answer all the questions!

The most important is that you point to the config.pl file correctly! 
If you don't do this, then things go wrong.

Your old config file will be copied to config.pl.pre-3.0.0

Again for backupreasons, install the program itself in a different 
directory then the old one!  (It is also one of the questions)

Then just copy the init.d file (maybe copy the old one somewhere if 
things go wrong)

And then just test.

If you see it goes wrong, copy the old config file back, replace the 
init file and everything should be fine!  Maybe the cgi could be 
corrupted, but that is just a matter of copiing it back!

I never had problems, the script is written well.  I must say I use 
rsync, but I dont think lots changes with samba!

Regards
Klaas
-- 
"Several billion trillion tons of superhot
exploding hydrogen nuclei rose slowly above
the horizon and managed to look small, cold
and slightly damp."
Douglas Adams - The Hitch Hickers
Guide to the Galaxy

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Long: How BackupPC handles pooling, and how transfer methods affect bandwidth usage

[Carl Wilhelm Soderstrom]

On 01/27 02:23 , Timothy J. Massey wrote:
> We are right now envisioning needing 2TB of space to back up a single 
> host:  our mail server, which has less than 100GB of data.  The deltas 
> on our mail server are currently in the neighborhood of 50GB/day. 
> That's because we have 50GB of mail data, and we all receive at least 
> one mail a day.  

I don't know what kind of mailserver you have, but I would *strongly*
suggest that if you're using a Linux mailserver, that you go to 'maildir'
format for your mailboxes.

In case you're not familiar with it:

the normal 'mbox' format is just a concatenation of all the mail messages in
one big file. every new mail message just gets appended onto the end of the
mbox.

maildir format uses directories and subdirectories full of little files,
one for each mail message. this is important for backups, since only the new
files get transferred. it did a world of good for backuppc when we converted
an old mailserver over to maildir format. I haven't done the math on it; but
I'm fairly sure it halved the backup time, and maybe quite a bit better.

the downside of maildir is that it takes longer to read the mailbox, since
there are more disk head seeks. this is balanced out by the reduced memory
requirements tho... you no longer have to hold the entirety of each user's
mbox in memory when they're connected with IMAP. (when you're dealing with
people who steadfastly refuse to clean up their mailbox, this gets to be a
problem).

-- 
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] how to update from 2.1.1

[Jim McNamara]

Due to the code freeze in Debian for the release of Etch as stable
"soon", it will be quite a while before a new deb package for backupPC
makes it to stable. The Debian backupPC maintainer is probably well
aware of the releases, but even if he made the packages, the code
freeze would prevent them from getting into the apt repositories.
We'll probably see 3.0 hit unstable not too long after Etch is
released, but getting a 3.0 package on a stable system is not going to
happen any time soon. They may put out a 2.1.3 package for stable,
after it has been tested, but due to the nature of Debian, I think
that is months away. If you want the new versions, you'll have to do
it yourself from source.

Peace,
Jim

On 1/29/07, Nils Breunese (Lemonbit) <[EMAIL PROTECTED]> wrote:
> Filipe wrote:
>
> > I've followed a guide and I used apt-get install... when installing
> > backuppc 2.1.1
> > and now what should I do?!
> > there's version 3 also out  :o
>
> You could contact the maintainer and ask if an update is in the works
> or maybe use Debian's Bug Tracker. I'm pretty sure you can also
> uninstall the BackupPC deb, download BackupPC 3.0.0 and point the
> installer to your previous config.
>
> Nils Breunese.
>
>
>
>
> -
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/backuppc-users
> http://backuppc.sourceforge.net/
>
>
>
>

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] how to update from 2.1.1

[Holger Parplies]

Hi,

Jim McNamara wrote on 29.01.2007 at 10:55:26 [Re: [BackupPC-users] how to 
update from 2.1.1]:
> Due to the code freeze in Debian for the release of Etch as stable
> "soon", it will be quite a while before a new deb package for backupPC
> makes it to stable.

true.

> The Debian backupPC maintainer is probably well
> aware of the releases, but even if he made the packages, the code
> freeze would prevent them from getting into the apt repositories.

What about experimental?
Besides that, there is no reason not to use the maintainer's package even if
it is not in an official Debian repository.

> We'll probably see 3.0 hit unstable not too long after Etch is
> released, but getting a 3.0 package on a stable system is not going to
> happen any time soon.

I disagree. There aren't any (versioned) libc-dependencies in BackupPC. There
may be other versioned dependencies ("Depends: dpkg >= 1.8.3"? Shouldn't
that be Pre-Depends?), but if we're lucky, BackupPC 3.0.0 from sid (or even
experimental) may install in stable without pulling in any further
dependencies.

> If you want the new versions, you'll have to do it yourself from source.

Or wait for someone else to build a package ...

Regards,
Holger

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

[BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Timothy J. Massey]

Hello!

I have had a bug with BackupPC, rsync and RHEL4 for some time now.  I 
blindly assumed that this bug had been fixed in the last year or so.  It 
turns out it has not.

BackupPC Configuration:
BackupPC 3.0beta3 running on CentOS 3.8 with latest updates


# uname -a
Linux vault.example.com 2.4.21-47.EL #1 Tue Aug 1 08:56:24 EDT 2006 i686 
i686 i386 GNU/Linux


# perl -V
Summary of my perl5 (revision 5.0 version 8 subversion 0) configuration:
   Platform:
 osname=linux, osvers=2.4.21-37.0.1.el.centos3.xfs.0smp, 
archname=i386-linux-thread-multi
 uname='linux sillage.bis.pasteur.fr 
2.4.21-37.0.1.el.centos3.xfs.0smp #1 smp fri jan 20 10:58:28 cet 2006 
i686 athlon i386 gnulinux '
 config_args='-des -Doptimize=-O2 -g -pipe -march=i386 -mcpu=i686 
-Dmyhostname=localhost [EMAIL PROTECTED] -Dcc=gcc -Dcf_by=Red 
Hat, Inc. -Dinstallprefix=/usr -Dprefix=/usr -Darchname=i386-linux 
-Dvendorprefix=/usr -Dsiteprefix=/usr 
-Dotherlibdirs=/usr/lib/perl5/5.8.0 -Duseshrplib -Dusethreads 
-Duseithreads -Duselargefiles -Dd_dosuid -Dd_semctl_semun -Di_db 
-Ui_ndbm -Di_gdbm -Di_shadow -Di_syslog -Dman3ext=3pm -Duseperlio 
-Dinstallusrbinperl -Ubincompat5005 -Uversiononly -Dpager=/usr/bin/less 
-isr'
 hint=recommended, useposix=true, d_sigaction=define
 usethreads=define use5005threads=undef useithreads=define 
usemultiplicity=define
 useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
 use64bitint=undef use64bitall=undef uselongdouble=undef
 usemymalloc=n, bincompat5005=undef
   Compiler:
 cc='gcc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS 
-DDEBUGGING -fno-strict-aliasing -I/usr/local/include 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm',
 optimize='-O2 -g -pipe -march=i386 -mcpu=i686',
 cppflags='-D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS 
-DDEBUGGING -fno-strict-aliasing -I/usr/local/include -I/usr/include/gdbm'
 ccversion='', gccversion='3.2.3 20030502 (Red Hat Linux 3.2.3-54)', 
gccosandvers=''
 intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
 ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', 
lseeksize=8
 alignbytes=4, prototype=define
   Linker and Libraries:
 ld='gcc', ldflags =' -L/usr/local/lib'
 libpth=/usr/local/lib /lib /usr/lib
 libs=-lnsl -lgdbm -ldb -ldl -lm -lpthread -lc -lcrypt -lutil
 perllibs=-lnsl -ldl -lm -lpthread -lc -lcrypt -lutil
 libc=/lib/libc-2.3.2.so, so=so, useshrplib=true, libperl=libperl.so
 gnulibc_version='2.3.2'
   Dynamic Linking:
 dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic 
-Wl,-rpath,/usr/lib/perl5/5.8.0/i386-linux-thread-multi/CORE'
 cccdlflags='-fPIC', lddlflags='-shared -L/usr/local/lib'


Characteristics of this binary (from libperl):
   Compile-time options: DEBUGGING MULTIPLICITY USE_ITHREADS 
USE_LARGE_FILES PERL_IMPLICIT_CONTEXT
   Locally applied patches:
 MAINT18379
   Built under linux
   Compiled at Jun 10 2006 13:23:46
   @INC:
 /usr/lib/perl5/5.8.0/i386-linux-thread-multi
 /usr/lib/perl5/5.8.0
 /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi
 /usr/lib/perl5/site_perl/5.8.0
 /usr/lib/perl5/site_perl
 /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi
 /usr/lib/perl5/vendor_perl/5.8.0
 /usr/lib/perl5/vendor_perl
 /usr/lib/perl5/5.8.0/i386-linux-thread-multi
 /usr/lib/perl5/5.8.0
 .


The following code has been loaded from a *minimal* CentOS 3.8 install:

BackupPC-3.0.0beta3.tar.gz
CGI.pm-3.25.tar.gz
compat-libstdc++-7.3-2.96.128.i386.rpm
Encode-2.18.compiled.tar.gz
par2cmdline-0.4-alt0.M24.1.i586.rpm
perl-Archive-Zip-1.16-1.1.el3.rf.noarch.rpm
perl-Compress-Zlib-1.42-1.el3.rf.i386.rpm
perl-File-RsyncP-0.68-1.el3.rf.i386.rpm
perl-HTML-Parser-3.26-17.i386.rpm
perl-HTML-Tagset-3.03-28.noarch.rpm
perl-libwww-perl-5.65-6.noarch.rpm
perl-suidperl-5.8.0-94.EL3.i386.rpm
perl-URI-1.21-7.noarch.rpm
perl-XML-Parser-2.31-16.EL3.i386.rpm
perl-XML-RSS-1.10-1.el3.rf.noarch.rpm

As you can see, I'm running the latest version of File::RsyncP.


Host Confiugration:
Red Hat Enterprise Linux 4
Latest rsync RPM from DAG


# uname -a
Linux host.example.com 2.6.9-5.ELsmp #1 SMP Wed Jan 5 19:30:39 EST 2005 
i686 i686 i386 GNU/Linux


# rsync --version
rsync  version 2.6.9  protocol version 29
Copyright (C) 1996-2006 by Andrew Tridgell, Wayne Davison, and others.

Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,
   inplace, IPv6, 64-bit system inums, 64-bit internal inums


Here is my /etc/rsyncd.conf:


# cat /etc/rsyncd.conf
log file = /var/log/rsyncd.log
pid file = /var/run/rsyncd.pid
lock file = /var/run/rsync.lock

[ROOT]
 path = /
 comment = Root filesystem
 uid = root
 gid = root
 read only = yes
 list = no
 auth users = backupuser

[BackupPC-users] When the backup are made?

[Joe Skop]

Hi,

first thanks for this fine program. I discover it by HowToForge
yesterday, and I prepare and install immediatly.

My first question is: exaclty, when the backup are made? In which
time? I can't find this information, maybe somewere in config but I'm
sure I read fine it. I would like to know this for scheduling the pc
on network that must be open. This means that I need to make the
backup on night.

Thanks and again compliments.

Regards,
JS

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] When the backup are made?

[Nils Breunese (Lemonbit)]

Joe Skop wrote:


first thanks for this fine program. I discover it by HowToForge
yesterday, and I prepare and install immediatly.

My first question is: exaclty, when the backup are made? In which
time? I can't find this information, maybe somewere in config but I'm
sure I read fine it. I would like to know this for scheduling the pc
on network that must be open. This means that I need to make the
backup on night.


Take a look at $Conf{BlackoutPeriods} in the 'What to backup and when  
to do it' section of the docs [1] and/or in the configuration file.


Nils Breunese.

[1] http://backuppc.sourceforge.net/faq/ 
BackupPC.html#what_to_backup_and_when_to_do_it





PGP.sig
Description: Dit deel van het bericht is digitaal ondertekend
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Backuppc host discovery for linux computers

[Ted To]

DNS is done by my router.  It has DNSmasq and I've now turned on local DNS
-- will that do the trick?

On 1/28/07, Holger Parplies <[EMAIL PROTECTED]> wrote:


Hi,

Ted To wrote on 23.01.2007 at 10:06:15 and on 27.01.2007 at 19:08:37
[[BackupPC-users] Backuppc host discovery for linux computers]:
> Reading the documenation on host discovery, it's not clear to me how to
set
> up my network so that backuppc knows what dhcp assigned IP address to
> associate with a linux box.  Can someone offer some help or point me in
the
> right direction?

easiest would be if your host was resolvable via DNS. What do you use as
DHCP server? dnsmasq for instance supposedly does both DNS proxying and
DHCP
serving, allowing the DHCP hosts to be visible in DNS. If this was the
case,
you shouldn't need to do anything (except point the BackupPC server at the
right DNS server, of course ;-) for your hosts to be resolved correctly
(or
am I missing something?).

I presume you have a good reason to use DHCP and not fixed IP addresses in
the first place?

Regards,
Holger

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Les Mikesell]

Timothy J. Massey wrote:
> 
> I have had a bug with BackupPC, rsync and RHEL4 for some time now.  I 
> blindly assumed that this bug had been fixed in the last year or so.  It 
> turns out it has not.
> 
> BackupPC Configuration:
> BackupPC 3.0beta3 running on CentOS 3.8 with latest updates
> 
> Host Confiugration:
> Red Hat Enterprise Linux 4
> Latest rsync RPM from DAG
> 
> 
> # uname -a
> Linux host.example.com 2.6.9-5.ELsmp #1 SMP Wed Jan 5 19:30:39 EST 2005 
> i686 i686 i386 GNU/Linux
> 
> 
> # rsync --version
> rsync  version 2.6.9  protocol version 29
> Copyright (C) 1996-2006 by Andrew Tridgell, Wayne Davison, and others.
> 
> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,
>inplace, IPv6, 64-bit system inums, 64-bit internal inums


That's not the stock rsync package for RHEL4. The changed behavior of 
rsync has been discussed on the list before in the context of distros 
that include it:
http://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg04181.html

Or, you could put the stock package back - the RHEL guys get some of 
this stuff right...

-- 
   Les Mikesell
 [EMAIL PROTECTED]



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] When the backup are made?

[Les Mikesell]

Nils Breunese (Lemonbit) wrote:
>>
>> My first question is: exaclty, when the backup are made? In which
>> time? I can't find this information, maybe somewere in config but I'm
>> sure I read fine it. I would like to know this for scheduling the pc
>> on network that must be open. This means that I need to make the
>> backup on night.
> 
> Take a look at $Conf{BlackoutPeriods} in the 'What to backup and when to 
> do it' section of the docs [1] and/or in the configuration file.
> 
> Nils Breunese.
> 
> [1] 
> http://backuppc.sourceforge.net/faq/BackupPC.html#what_to_backup_and_when_to_do_it
>  

Note that the blackout period does not apply until a new target has been 
pinged some number of times outside of the blackout to establish that it 
is normally available.  I usually add hosts and start their first backup 
manually at the end of a day so their cycle will start out after hours 
even before the blackout would enforce it.

-- 
   Les Mikesell
[EMAIL PROTECTED]


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Backuppc host discovery for linux computers

[Ski Kacoroski]

Ted To wrote:
> Hi,
> 
> Reading the documenation on host discovery, it's not clear to me how to set
> up my network so that backuppc knows what dhcp assigned IP address to
> associate with a linux box.  Can someone offer some help or point me in the
> right direction?

The way I do this is via dynamic dns.  I run cron jobs on the unix 
clients (in my case mac) that update an ldap directory with the mac 
address, computer name, and current IP.  Then I run a job once an hour 
that creates the dhcpd.conf files and restarts the dhcp server.  Now 
BackupPC can just query dns to get the ip address for the computer. 
Works very well for desktops and ok for most laptops.  I have a few that 
move between 4 - 5 subnets a day and are always on wireless that are 
problematic, but other than that the system works ok.

cheers,

ski

-- 
"When we try to pick out anything by itself, we find it
  connected to the entire universe"John Muir

Chris "Ski" Kacoroski, [EMAIL PROTECTED], 206-501-9803

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Timothy J. Massey]

Les Mikesell <[EMAIL PROTECTED]> wrote on 01/29/2007 12:35:29 PM:

 > Timothy J. Massey wrote:
 > >
 > > I have had a bug with BackupPC, rsync and RHEL4 for some time now.  I
 > > blindly assumed that this bug had been fixed in the last year or 
so.  It
 > > turns out it has not.
 > >
 > > BackupPC Configuration:
 > > BackupPC 3.0beta3 running on CentOS 3.8 with latest updates
 > >
 > > Host Confiugration:
 > > Red Hat Enterprise Linux 4
 > > Latest rsync RPM from DAG
 > >
 > >
 > > # uname -a
 > > Linux host.example.com 2.6.9-5.ELsmp #1 SMP Wed Jan 5 19:30:39 EST 
2005
 > > i686 i686 i386 GNU/Linux
 > >
 > >
 > > # rsync --version
 > > rsync  version 2.6.9  protocol version 29
 > > Copyright (C) 1996-2006 by Andrew Tridgell, Wayne Davison, and others.
 > > 
 > > Capabilities: 64-bit files, socketpairs, hard links, symlinks, 
batchfiles,
 > >inplace, IPv6, 64-bit system inums, 64-bit internal 
inums
 >
 >
 > That's not the stock rsync package for RHEL4. The changed behavior of
 > rsync has been discussed on the list before in the context of distros
 > that include it:
 > 
http://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg04181.html
 >
 > Or, you could put the stock package back - the RHEL guys get some of
 > this stuff right...

Well, the rsync package for RHEL4 didn't work, and *then* I upgraded to 
a standard rsync package.  It's not like I randomly go around adding 
non-standard packages...

And wasn't the "change to -D and add --specials" supposed to not be 
needed in BackupPC 3.0?  That's what I'm running...

Tim Massey

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Timothy J. Massey]

[EMAIL PROTECTED] wrote on 01/29/2007 
01:25:06 PM:

 > Les Mikesell <[EMAIL PROTECTED]> wrote on 01/29/2007 12:35:29 PM:
 >
 >  > That's not the stock rsync package for RHEL4. The changed behavior of
 >  > rsync has been discussed on the list before in the context of distros
 >  > that include it:
 >  >
 > 
http://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg04181.html

And the *very* next e-mail says that this is fixed in 3.0beta3.  That's 
what I'm running...

http://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg04205.html

 >  > Or, you could put the stock package back - the RHEL guys get some of
 >  > this stuff right...
 >
 > Well, the rsync package for RHEL4 didn't work, and *then* I upgraded to
 > a standard rsync package.  It's not like I randomly go around adding
 > non-standard packages...

For compleness, I have installed the following RPM instead:

rsync-2.6.3-1.i386.rpm

I've started a full backup.  We'll see if it makes a difference. 
However, I believe that was the previous version that had problems 
*before* I upgraded...

 > And wasn't the "change to -D and add --specials" supposed to not be
 > needed in BackupPC 3.0?  That's what I'm running...

I've checked:  here is my config.pl:

$Conf{RsyncArgs} = [
 #
 # Do not edit these!
 #
 '--numeric-ids',
 '--perms',
 '--owner',
 '--group',
 '-D',
 '--links',
 '--hard-links',
 '--times',
 '--block-size=2048',
 '--recursive',

So this should not be an issue.  Am I missing something?

Tim Massey

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

[BackupPC-users] Bad disk copy of repository--best recovery approach?

[John Locke]

Hi,

My main backuppc file repository ran out of disk space last week. I had
it running on a software RAID 1 array, without LVM, a 120GB ext3 partition.

So over the weekend I put in two new 320GB drives, configured them for
(software) RAID 1, and created an LVM partition running there to ease
the pain in the future.

To move the data over, I booted into single user mode (the system disk
is on another drive), and used dd to copy over the entire filesystem
from the /dev/md1 device to the logical volume.

The problem is, dd kept running far beyond the actual size of the
partition. After it had copied 148 GB of data, I killed it. Then after
resizing the filesystem I mounted it and fired everything up.

So now I have a drive with the main Backuppc pool, with some files in an
unknown state. The backups are running mostly successfully, but certain
computers are showing a bunch of errors in the Xferlog. Here are some
examples of the errors I've gotten:

Unable to open 
/var/lib/backuppc/pc/pcname/new/f%2fvar%2fwww/fOR/fcache/f%252Fcategory%252Fhome%252Fexped_or%252Fexped_bags%252Fcategory%252Fhome%252Fheadware%252Fcold_hats%252Fstyle%252Fhome%252Fexped_or%252Fexped_bags%252Fcategory%252Fhome%252Fheadware%252Fcold_hats%252Fbalaclavas%252F83130%252F^%25%25754^%25%25754976500^new.tpl
 for writing
Botch, no matches on 
/var/lib/backuppc/pc/pcname/new/f%2fvar%2fwww/fOR/fcache/f%252Fcategory%252Fhome%252Fexped_or%252Fexped_bags%252Fcategory%252Fhome%252Fheadware%252Fcold_hats%252Fstyle%252Fhome%252Fexped_or%252Fexped_bags%252Fcategory%252Fhome%252Fheadware%252Fcold_hats%252Fbalaclavas%252F83130%252F^%25%25754^%25%25754976500^new.tpl
 (7332b1505935902fd6f937d6df24ac85)
[ skipped 1 lines ]
Unable to open 
/var/lib/backuppc/pc/pcname/new/f%2fvar%2fwww/fOR/fcache/f%252Fcategory%252Fhome%252Fexped_or%252Fexped_bags%252Fcategory%252Fhome%252Fheadware%252Fcold_hats%252Fstyle%252Fhome%252Fexped_or%252Fexped_bags%252Fcategory%252Fhome%252Fheadware%252Fcold_hats%252Fbalaclavas%252F83237%252F^%25%25754^%25%25754976500^new.tpl
 for writing
Botch, no matches on 
/var/lib/backuppc/pc/pcname/new/f%2fvar%2fwww/fOR/fcache/f%252Fcategory%252Fhome%252Fexped_or%252Fexped_bags%252Fcategory%252Fhome%252Fheadware%252Fcold_hats%252Fstyle%252Fhome%252Fexped_or%252Fexped_bags%252Fcategory%252Fhome%252Fheadware%252Fcold_hats%252Fbalaclavas%252F83237%252F^%25%25754^%25%25754976500^new.tpl
 (cdf3fd4831b6f7c87b5c08bea892ff4b)
[ skipped 1 lines ]

Unable to link 
/var/lib/backuppc/pc/pcname/117/f%2fvar%2fwww/fhtml/fadvancededucators.com/feditor/findex.html
 to 
/var/lib/backuppc/pc/baker.freelock.com/new//f%2fvar%2fwww/fhtml/fadvancededucators.com/feditor/findex.html
[ skipped 6 lines ]
Unable to link 
/var/lib/backuppc/pc/pcname/117/f%2fvar%2fwww/fhtml/fadvancededucators.com/fhelp/fcss/findex.html
 to 
/var/lib/backuppc/pc/baker.freelock.com/new//f%2fvar%2fwww/fhtml/fadvancededucators.com/fhelp/fcss/findex.html
[ skipped 1 lines ]


Now, I'm confident that if worst came to worst, I could load up the old
drive to restore any of the existing data. But going forward, will
Backuppc repair any corrupt files on the disk? When I browse to the
files in the error message, I'm not seeing any problems, but I would
hate to have a bad file linked in all future backups so that I end up
never having a good copy.

Does Backuppc verify the integrity of already backed up files, before
linking them? Or should I wipe out the current backups on the disk and
just start fresh to be sure I have good copies going forward?

Thanks for your help, and a great project!

Cheers,

-- 
John Locke
"Open Source Solutions for Small Business Problems"
published by Charles River Media, June 2004
http://www.freelock.com


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Timothy J. Massey]

[EMAIL PROTECTED] wrote on 01/29/2007 
01:40:56 PM:

 >  >  > Or, you could put the stock package back - the RHEL guys get 
some of
 >  >  > this stuff right...
 >  >
 >  > Well, the rsync package for RHEL4 didn't work, and *then* I 
upgraded to
 >  > a standard rsync package.  It's not like I randomly go around adding
 >  > non-standard packages...
 >
 > For compleness, I have installed the following RPM instead:
 >
 > rsync-2.6.3-1.i386.rpm
 >
 > I've started a full backup.  We'll see if it makes a difference.
 > However, I believe that was the previous version that had problems
 > *before* I upgraded...

Another failure.  And here's the log:

2007-01-29 13:41:49 full backup started for directory ROOT
2007-01-29 14:19:55 Got fatal error during xfer (Child exited prematurely)
2007-01-29 14:20:00 Backup aborted (Child exited prematurely)
2007-01-29 14:20:00 Saved partial dump 0

Here's the log from the host:

# cat rsyncd.log
2007/01/29 12:56:15 [8021] name lookup failed for 192.168.1.32: Name or 
service not known
2007/01/29 12:56:15 [8021] rsync on . from [EMAIL PROTECTED] (192.168.1.32)
2007/01/29 13:34:09 [8021] rsync: writefd_unbuffered failed to write 
4096 bytes: phase "unknown" [sender]: Connection timed out (110)
2007/01/29 13:34:09 [8021] rsync error: error in rsync protocol data 
stream (code 12) at io.c(909)

I've tried older versions of rsync, I've tried newer version of rsync. 
I've tried Red Hat's versions, I've tried generic versions.  I've tried 
older versions of File::RsyncD, I've tried newer versions of 
File::RsyncD.  I've tried RsyncArgs with '--devices', I've tried 
RsyncArgs with '-D'.  I'm now going to try adding '--specials' with both 
'-D' and '--devices'.  But according to what I've read, '--specials' is 
not supposed to be needed with *either* File::RsyncP 0.68 (which I 
have), or '-D'.

Anything else I can try?  This is an error I can reproduce on at least 3 
different hosts, with 3 different BackupPC servers: two of which are 
identical, and a third one which is different, yet all of them give me 
the same error.

Tim Massey

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Timothy J. Massey]

[EMAIL PROTECTED] wrote on 01/29/2007 
02:40:59 PM:

 > I've tried older versions of rsync, I've tried newer version of rsync.
 > I've tried Red Hat's versions, I've tried generic versions.  I've tried
 > older versions of File::RsyncD, I've tried newer versions of
 > File::RsyncD.  I've tried RsyncArgs with '--devices', I've tried
 > RsyncArgs with '-D'.  I'm now going to try adding '--specials' with both
 > '-D' and '--devices'.

Failure with '-D' and '--specials':

2007-01-29 14:34:16 full backup started for directory ROOT
2007-01-29 14:34:17 Got fatal error during xfer (fileListReceive failed)
2007-01-29 14:34:22 Backup aborted (fileListReceive failed)

Log file from host:

2007/01/29 14:15:47 [9432] name lookup failed for 192.168.1.32: Name or 
service not known
2007/01/29 14:15:47 [9432] rsync on . from [EMAIL PROTECTED] (192.168.1.32)
2007/01/29 14:15:47 [9432] rsync: on remote machine: --specials: unknown 
option
2007/01/29 14:15:48 [9432] rsync error: requested action not supported 
(code 4) at clientserver.c(473)

Same failure when you change the '-D' to '--devices', leaving '--specials'.

Doing an rsync --help on the host, it doesn't seem to know what 
'--specials' is.  I'm not sure what that does, or if it's a parameter 
that's supposed to be used by File::RsyncP.  In any case, no permutation 
of '-D', '--devices', and '--specials' corrects this problem.

Tim Massey

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Timothy J. Massey]

"Joe Casadonte" <[EMAIL PROTECTED]> wrote on 01/29/2007 
02:39:52 PM:

 > On Mon, 29 Jan 2007, Timothy J. Massey wrote:
 >
 > > So this should not be an issue.  Am I missing something?
 >
 > Can you run rsync from the command line from the backuppc server
 > hitting the client machine?  Something like:
 >
 >rsync --list-only [EMAIL PROTECTED]::[module-name]
 >rsync --list-only [EMAIL PROTECTED]::home

No, for a couple of reasons:

1) The BackupPC server is running on CentOS (RHEL) 3.8.  The latest 
version of rsync is 2.5.7, which does not support --list-only.  I'll 
update to test and see, but...

2) I'm not sure that it's very conclusive.  BackupPC doesn't use the 
rsync binary on the server.  It uses File::RsyncP, a version of rsync 
rewritten in perl.  It seems to me that the problem is between rsync and 
File:RsyncP.  However, I'll try to update.  Some people may not like it, 
though:  I'll have to use a non-Red-Hat rsync!  :)

OK, here goes, from the BackupPC server:

: # rsync --version
rsync  version 2.6.9  protocol version 29
Copyright (C) 1996-2006 by Andrew Tridgell, Wayne Davison, and others.

Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,
   inplace, IPv6, 64-bit system inums, 64-bit internal inums

# rsync --list-only [EMAIL PROTECTED]::ROOT
Password:
rsync: on remote machine: --list-only: unknown option
rsync error: requested action not supported (code 4) at clientserver.c(473)
rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(604) 
[receiver=2.6.9]


So, it looks like --list-only is not supported by Red Hat's RHEL4 
version of rsync, either.  On the host side:

# rsync --version
rsync  version 2.6.3  protocol version 28
Copyright (C) 1996-2004 by Andrew Tridgell and others

Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,
   inplace, IPv6, 64-bit system inums, 64-bit internal inums

# rpm -ivh rsync-2.6.9-1.el3.rf.i386.rpm  --force
warning: rsync-2.6.9-1.el3.rf.i386.rpm: V3 DSA signature: NOKEY, key ID 
6b8d79e6
Preparing...### 
[100%]
1:rsync  ### 
[100%]

# rsync --version
rsync  version 2.6.9  protocol version 29
Copyright (C) 1996-2006 by Andrew Tridgell, Wayne Davison, and others.

Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,
   inplace, IPv6, 64-bit system inums, 64-bit internal inums


Now, when I run rsync --list-only [EMAIL PROTECTED]::ROOT from the 
BackupPC server, it runs fine.

For the record, I have always been able to do a transfer using the 
normal rsync binaries just fine, no matter what version of rsync or OS, 
without error.  Again, I think that's because the problem is an issue 
between File::RsyncP and the remote rsync binary.  Therefore, doing 
tests from the command-line won't help...

But I've used multiple versions of the rsync binary (2.5.x, 2.6.3 RHEL 
and 2.6.9 generic) on the host side, and I've used different distros 
(Knoppix 3.7 and CentOS 3.8, fully updated), and different versions of 
File::RsyncP (0.52 and 0.68, the latest).  I get the exact same error 
every time.
Timothy J. Massey

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Les Mikesell]

Timothy J. Massey wrote:
> 
> Another failure.  And here's the log:
> 
> 2007-01-29 13:41:49 full backup started for directory ROOT
> 2007-01-29 14:19:55 Got fatal error during xfer (Child exited prematurely)
> 2007-01-29 14:20:00 Backup aborted (Child exited prematurely)
> 2007-01-29 14:20:00 Saved partial dump 0
> 
> Here's the log from the host:
> 
> # cat rsyncd.log
> 2007/01/29 12:56:15 [8021] name lookup failed for 192.168.1.32: Name or 
> service not known
> 2007/01/29 12:56:15 [8021] rsync on . from [EMAIL PROTECTED] (192.168.1.32)
> 2007/01/29 13:34:09 [8021] rsync: writefd_unbuffered failed to write 
> 4096 bytes: phase "unknown" [sender]: Connection timed out (110)
> 2007/01/29 13:34:09 [8021] rsync error: error in rsync protocol data 
> stream (code 12) at io.c(909)

Does this aways happen on the same file?  It looks like what used to 
happen when rsync had a 2 gig file size limit, but I don't think any 
versions you've mentioned would have that.  How about disk space for a 
tmp copy of whatever you've hit back on the backuppc server.  I've seen 
errors approximately like that with stock rsync copies when the receiver 
runs out of disk space.   Or as a final guess, what about 
disk/filesystem problems?  Does 'dmesg' show any problems when this happens?

-- 
   Les Mikesell
[EMAIL PROTECTED]



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Timothy J. Massey]

Les Mikesell <[EMAIL PROTECTED]> wrote on 01/29/2007 04:21:51 PM:

 > Timothy J. Massey wrote:
 > >
 > > Another failure.  And here's the log:
 > >
 > > 2007-01-29 13:41:49 full backup started for directory ROOT
 > > 2007-01-29 14:19:55 Got fatal error during xfer (Child exited 
prematurely)
 > > 2007-01-29 14:20:00 Backup aborted (Child exited prematurely)
 > > 2007-01-29 14:20:00 Saved partial dump 0
 > >
 > > Here's the log from the host:
 > >
 > > # cat rsyncd.log
 > > 2007/01/29 12:56:15 [8021] name lookup failed for 192.168.1.32: 
Name or
 > > service not known
 > > 2007/01/29 12:56:15 [8021] rsync on . from [EMAIL PROTECTED] 
(192.168.1.32)
 > > 2007/01/29 13:34:09 [8021] rsync: writefd_unbuffered failed to write
 > > 4096 bytes: phase "unknown" [sender]: Connection timed out (110)
 > > 2007/01/29 13:34:09 [8021] rsync error: error in rsync protocol data
 > > stream (code 12) at io.c(909)
 >
 > Does this aways happen on the same file?

No.  Similar times, but not the same file.

 >  It looks like what used to
 > happen when rsync had a 2 gig file size limit, but I don't think any
 > versions you've mentioned would have that.

Nope.

 >  How about disk space for a
 > tmp copy of whatever you've hit back on the backuppc server.

Nope.  Tons on both.

 >  I've seen
 > errors approximately like that with stock rsync copies when the receiver
 > runs out of disk space.   Or as a final guess, what about
 > disk/filesystem problems?  Does 'dmesg' show any problems when this 
happens?

Nope.  I *do* get tons of these:

TCP: Treason uncloaked! Peer 192.168.1.32:32929/873 shrinks window 
1512534234:1512535682. Repaired.

But I get those when rsyncing to RHEL3 boxes, too, and they work fine.

Remember, this happens on *3* different servers, with 3 different 
BackupPC servers.  This is *not* related to a unique property of the 
individual server.  This is *very* related to RHEL4, instead of RHEL3. 
Like I said, we upgraded a server from 3 to 4:  used to work, then failed.

Timothy J. Massey

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Timothy J. Massey]

[EMAIL PROTECTED] wrote on 01/29/2007 
03:10:18 PM:

 > [EMAIL PROTECTED] wrote on 01/29/2007
 > 02:40:59 PM:
 >
 >  > I've tried older versions of rsync, I've tried newer version of rsync.
 >  > I've tried Red Hat's versions, I've tried generic versions.  I've 
tried
 >  > older versions of File::RsyncD, I've tried newer versions of
 >  > File::RsyncD.  I've tried RsyncArgs with '--devices', I've tried
 >  > RsyncArgs with '-D'.  I'm now going to try adding '--specials' 
with both
 >  > '-D' and '--devices'.
 >
 > Failure with '-D' and '--specials':
 >
 > 2007-01-29 14:34:16 full backup started for directory ROOT
 > 2007-01-29 14:34:17 Got fatal error during xfer (fileListReceive failed)
 > 2007-01-29 14:34:22 Backup aborted (fileListReceive failed)
 >
 > Log file from host:
 >
 > 2007/01/29 14:15:47 [9432] name lookup failed for 192.168.1.32: Name or
 > service not known
 > 2007/01/29 14:15:47 [9432] rsync on . from [EMAIL PROTECTED] 
(192.168.1.32)
 > 2007/01/29 14:15:47 [9432] rsync: on remote machine: --specials: unknown
 > option
 > 2007/01/29 14:15:48 [9432] rsync error: requested action not supported
 > (code 4) at clientserver.c(473)

I went ahead and updated the host's rsync back to the generic 2.6.9 RPM, 
and am rerunning with '--devices' and '--specials'.  It got past the 
above error.  I'll let you know how that one ends as soon as it does. 
But wasn't this supposed to be fixed with File::RsyncP 0.68?  If so, I'm 
not sure it's completely fixed...

Timothy J. Massey

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Les Mikesell]

Timothy J. Massey wrote:

> Remember, this happens on *3* different servers, with 3 different 
> BackupPC servers.  This is *not* related to a unique property of the 
> individual server.  This is *very* related to RHEL4, instead of RHEL3. 
> Like I said, we upgraded a server from 3 to 4:  used to work, then failed.

Maybe, but I think there is something subtle involved.  I back up a 
bunch of CentOS 4.x boxes without any problems like that and it's 
compiled from the same source rpms.   Full-version upgrades sometimes 
don't end up exactly the way you expect.  Do you have any RHEL4's that 
were installed from scratch to compare?

-- 
   Les Mikesell
[EMAIL PROTECTED]


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Timothy J. Massey]

[EMAIL PROTECTED] wrote on 01/29/2007 
04:52:15 PM:

 > Timothy J. Massey wrote:
 >
 > > Remember, this happens on *3* different servers, with 3 different
 > > BackupPC servers.  This is *not* related to a unique property of the
 > > individual server.  This is *very* related to RHEL4, instead of RHEL3.
 > > Like I said, we upgraded a server from 3 to 4:  used to work, then 
failed.
 >
 > Maybe, but I think there is something subtle involved.  I back up a
 > bunch of CentOS 4.x boxes without any problems like that and it's
 > compiled from the same source rpms.

I've actually used the latest CentOS4 RPM instead of the latest Red Hat 
just because it's easier to get!  :)

 > Full-version upgrades sometimes
 > don't end up exactly the way you expect.  Do you have any RHEL4's that
 > were installed from scratch to compare?

Yes:  One is a pure RHEL4, one is an upgrade from RHEL3 to RHEL4 and one 
is an upgrade from RHEL3 to CentOS4.

Timothy J. Massey

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Timothy J. Massey]

[EMAIL PROTECTED] wrote on 01/29/2007 
04:54:36 PM:

 > [EMAIL PROTECTED] wrote on 01/29/2007
 > 03:10:18 PM:
 >
 >  > [EMAIL PROTECTED] wrote on 01/29/2007
 >  > 02:40:59 PM:
 >  >
 >  >  > I've tried older versions of rsync, I've tried newer version of 
rsync.
 >  >  > I've tried Red Hat's versions, I've tried generic versions.  I've
 > tried
 >  >  > older versions of File::RsyncD, I've tried newer versions of
 >  >  > File::RsyncD.  I've tried RsyncArgs with '--devices', I've tried
 >  >  > RsyncArgs with '-D'.  I'm now going to try adding '--specials'
 > with both
 >  >  > '-D' and '--devices'.
 >  >
 >  > Failure with '-D' and '--specials':
 >  >
 >  > 2007-01-29 14:34:16 full backup started for directory ROOT
 >  > 2007-01-29 14:34:17 Got fatal error during xfer (fileListReceive 
failed)
 >  > 2007-01-29 14:34:22 Backup aborted (fileListReceive failed)
 >  >
 >  > Log file from host:
 >  >
 >  > 2007/01/29 14:15:47 [9432] name lookup failed for 192.168.1.32: 
Name or
 >  > service not known
 >  > 2007/01/29 14:15:47 [9432] rsync on . from [EMAIL PROTECTED]
 > (192.168.1.32)
 >  > 2007/01/29 14:15:47 [9432] rsync: on remote machine: --specials: 
unknown
 >  > option
 >  > 2007/01/29 14:15:48 [9432] rsync error: requested action not supported
 >  > (code 4) at clientserver.c(473)
 >
 > I went ahead and updated the host's rsync back to the generic 2.6.9 RPM,
 > and am rerunning with '--devices' and '--specials'.  It got past the
 > above error.  I'll let you know how that one ends as soon as it does.

I went ahead and deleted the pc/host directory before I restarted. 
Here's the logs:

BackupPC host log:

2007-01-29 17:21:19 full backup started for directory ROOT
2007-01-29 17:41:51 Got fatal error during xfer (Child exited prematurely)
2007-01-29 17:41:57 Backup aborted (Child exited prematurely)
2007-01-29 17:41:57 Saved partial dump 0

BackupPC server log:

2007-01-29 17:21:19 Started full backup on dcfraid02 (pid=21077, share=ROOT)
2007-01-29 17:41:57 Backup failed on dcfraid02 (Child exited prematurely)
2007-01-29 17:41:57 Running BackupPC_link dcfraid02 (pid=21122)
2007-01-29 17:43:41 Finished dcfraid02 (BackupPC_link dcfraid02)

BackupPC XferLog.0:

# tail XferLog.0
   create   744   0/0   47604 
lib/modules/2.6.9-5.EL/kernel/drivers/parport/parport.ko
   create   744   0/08716 
lib/modules/2.6.9-5.EL/kernel/drivers/parport/parport_cs.ko
Read EOF: No route to host
Tried again: got 0 bytes
finish: removing in-process file 
lib/modules/2.6.9-5.EL/kernel/drivers/parport/parport_pc.ko
Child is aborting
Parent read EOF from child: fatal error!
Done: 7730 files, 82068065 bytes
Got fatal error during xfer (Child exited prematurely)
Backup aborted (Child exited prematurely)
#

config.pl RsyncArgs:

$Conf{RsyncArgs} = [
 #
 # Do not edit these!
 #
 '--numeric-ids',
 '--perms',
 '--owner',
 '--group',
 '--devices',
 '--links',
 '--hard-links',
 '--times',
 '--block-size=2048',
 '--recursive',
 '--specials',
 '--one-file-system',
];


Host rsyncd.log:

# cat rsyncd.log
2007/01/29 16:35:17 [11153] rsyncd version 2.6.9 starting, listening on 
port 873
2007/01/29 16:35:43 [11158] name lookup failed for 192.168.1.32: Name or 
service not known
2007/01/29 16:35:43 [11158] connect from UNKNOWN (192.168.1.32)
2007/01/29 16:35:43 [11158] rsync on . from [EMAIL PROTECTED] 
(192.168.1.32)
2007/01/29 16:35:43 [11158] building file list
2007/01/29 16:56:09 [11158] rsync: writefd_unbuffered failed to write 4 
bytes [sender]: Connection timed out (110)
2007/01/29 16:56:09 [11158] rsync error: error in rsync protocol data 
stream (code 12) at io.c(1122) [sender=2.6.9]
# rsync --version
rsync  version 2.6.9  protocol version 29
Copyright (C) 1996-2006 by Andrew Tridgell, Wayne Davison, and others.

Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,
   inplace, IPv6, 64-bit system inums, 64-bit internal inums



Remember that I've done '-D'; '--devices'; '--devices' and '--specials'; 
'--specials'; '-D' and '--specials' with the same results.  I've used 
rsync 2.6.9 generic, 2.6.6 generic and 2.6.3-1 RHEL.

I am completely out of ideas.

Tim Massey


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Nils Breunese (Lemonbit)]

Les Mikesell wrote:


Timothy J. Massey wrote:


Remember, this happens on *3* different servers, with 3 different
BackupPC servers.  This is *not* related to a unique property of the
individual server.  This is *very* related to RHEL4, instead of  
RHEL3.
Like I said, we upgraded a server from 3 to 4:  used to work, then  
failed.


Maybe, but I think there is something subtle involved.  I back up a
bunch of CentOS 4.x boxes without any problems like that and it's
compiled from the same source rpms.


We use CentOS 4 with rsync from Dag's repository (dag.wieers.com).  
Never had any rsync problems.


Nils Breunese.




PGP.sig
Description: Dit deel van het bericht is digitaal ondertekend
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[ckeil]

Maybe I shouldn't chime in, because I've only been half following this
thread, but I can't help wondering if you've looked into all the
firewall/timeout possibilities?  Sometimes those settings get hosed during
an upgrade too.

ck



> Les Mikesell wrote:
>
>> Timothy J. Massey wrote:
>>
>>> Remember, this happens on *3* different servers, with 3 different
>>> BackupPC servers.  This is *not* related to a unique property of the
>>> individual server.  This is *very* related to RHEL4, instead of
>>> RHEL3.
>>> Like I said, we upgraded a server from 3 to 4:  used to work, then
>>> failed.
>>
>> Maybe, but I think there is something subtle involved.  I back up a
>> bunch of CentOS 4.x boxes without any problems like that and it's
>> compiled from the same source rpms.
>
> We use CentOS 4 with rsync from Dag's repository (dag.wieers.com).
> Never had any rsync problems.
>
> Nils Breunese.
>
>
> -
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/backuppc-users
> http://backuppc.sourceforge.net/
>



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Les Mikesell]

Timothy J. Massey wrote:

> lib/modules/2.6.9-5.EL/kernel/drivers/parport/parport_cs.ko
> Read EOF: No route to host

That's an odd network error. What's between these boxes?

-- 
   Les Mikesell
[EMAIL PROTECTED]




-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Jason Hughes]

[EMAIL PROTECTED] wrote:
> Maybe I shouldn't chime in, because I've only been half following this
> thread, but I can't help wondering if you've looked into all the
> firewall/timeout possibilities?  Sometimes those settings get hosed during
> an upgrade too.
>
>   
Not a bad thing to look into.  I remember someone saying earlier that 
they found a switch that would drop a TCP connection after only a few 
minutes of inactivity.  On a large file, is it possible rsync is busy 
calculating a checksum for a long time, especially on a busy system, 
causing that period of inactivity to trigger some denial-of-service 
rules for open ports?

One thing you could do is hook up a packet sniffer (tcpdump) and see 
what is happening on the wire during that time.  If it's nothing, that's 
your first clue.

Also, you might crank up the timeout settings for just the failing hosts 
and see if it allows your backups to run longer before failing.  Your 
failures are right about 20 minutes into them, which is a suspiciously 
round number.

JH

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Found a Bug

[Jason Hughes]

Willem Viljoen wrote:
> I have inserted the username and password required to make backups and 
> it works, full and inrcremental. When turning "Use simple File Sharing" 
> of - incremental backups fail with the message: "backup failed (session 
> setup failed: NT_STATUS_LOGON_FAILURE)". My printer monitoring server 
> require that "Use simple File Sharing" is turned off.
>
>   
Are you sure that full backups are working?  The only way a 
NT_STATUS_LOGON_FAILURE can occur is if the authentication for your 
user/pass is denied by SMB on the Windows XP box.  If it's wrong for 
incremental, it's wrong for full backups as well, since it's the same 
setting.

You might want to re-create the root$ share now that Use Simple File 
Sharing is turned off, as sometimes SMB likes to have its configuration 
recreated after certain settings change.  Also, I would mention that if 
your username has an empty password associated with it, you may 
experience strange behavior using Samba as a transfer method, because 
users without passwords may be considered 'guests' through that protocol 
and arbitrarily be denied access to some directories.

Good luck,
JH

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Timothy J. Massey]

[EMAIL PROTECTED] wrote on 01/29/2007 
07:01:03 PM:

 > Also, you might crank up the timeout settings for just the failing hosts
 > and see if it allows your backups to run longer before failing.  Your
 > failures are right about 20 minutes into them, which is a suspiciously
 > round number.

Actually, you're seeing it after it's done dozens of failed attempts. 
Each attempt copies a few files and then dies.  After dozens of 
attempts, it takes 40 minutes before failure.  If I delete the host, it 
fails after a much shorter time.

Timothy J. Masssey

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Timothy J. Massey]

Les Mikesell <[EMAIL PROTECTED]> wrote on 01/29/2007 06:31:03 PM:

 > Timothy J. Massey wrote:
 >
 > > lib/modules/2.6.9-5.EL/kernel/drivers/parport/parport_cs.ko
 > > Read EOF: No route to host
 >
 > That's an odd network error. What's between these boxes?

A switch and a couple of Ethernet cables...  :)

OK, fine.  I quit.

I have done with this server what I've done with others in this 
sutation:  switched to SMB.  I don't like it, but it will work for today.

I will set up a test environment from scratch:  a newly-loaded CentOS4 
server and my standard BackupPC configuation.  Seeing as everyone else 
but me seems to have no problems with CentOS/RHEL 4, hopefully I won't 
either.

That won't help me with those servers already in production...  :(

I would *really* like to know why I have three different servers that 
exhibit the same problems, with different rsync and File::RsyncP versions...

It will probably be a couple of days before I can get all this 
together...  I'll keep you posted.

Timothy J. Massey

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Les Mikesell]

Timothy J. Massey wrote:
> Les Mikesell <[EMAIL PROTECTED]> wrote on 01/29/2007 06:31:03 PM:
> 
>  > Timothy J. Massey wrote:
>  >
>  > > lib/modules/2.6.9-5.EL/kernel/drivers/parport/parport_cs.ko
>  > > Read EOF: No route to host
>  >
>  > That's an odd network error. What's between these boxes?
> 
> A switch and a couple of Ethernet cables...  :)

In that case, 'no route to host' means your arp cache has expired and 
you aren't getting an answer to your arp query.  Or your own NIC has 
lost its connection, but you'd see other lost connections at the same 
time then.

-- 
   Les Mikesell
[EMAIL PROTECTED]


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

[BackupPC-users] Win Rsyncd and BackupPC

[L Matthew Blancett]

I have installed the Windows rsync package, written my rsyncd.conf
files, configured the rsync containers, etc. When I command-line rsync
from the backuppc server, everything works fine. How do I now get
BackupPC to act as host to the rsync process, rather than executing it
remotely over ssh?




-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Craig Barratt]

> BackupPC XferLog.0:
> 
> # tail XferLog.0
>create   744   0/0   47604 
> lib/modules/2.6.9-5.EL/kernel/drivers/parport/parport.ko
>create   744   0/08716 
> lib/modules/2.6.9-5.EL/kernel/drivers/parport/parport_cs.ko
> Read EOF: No route to host

"No route to host" indicates the sudden onset of a networking problem.
Could this machine have lost connectivity or changed IP address?

I haven't looked at the rest of the thread carefully - the
fileListReceive failure problem needs to be understood.
Hopefully I can check that out later tonight.

Craig

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Found a Bug

[Craig Barratt]

Jason writes:

> Willem Viljoen wrote:
> > I have inserted the username and password required to make backups and 
> > it works, full and inrcremental. When turning "Use simple File Sharing" 
> > of - incremental backups fail with the message: "backup failed (session 
> > setup failed: NT_STATUS_LOGON_FAILURE)". My printer monitoring server 
> > require that "Use simple File Sharing" is turned off.
> >
> >   
> Are you sure that full backups are working?  The only way a 
> NT_STATUS_LOGON_FAILURE can occur is if the authentication for your 
> user/pass is denied by SMB on the Windows XP box.  If it's wrong for 
> incremental, it's wrong for full backups as well, since it's the same 
> setting.

Could this be related to an smbclient problem reported earlier
where incrementals fail authentication?  I'm attaching the
concluding email from that thread.

Craig

-- Forwarded message --
To:   backuppc-users@lists.sourceforge.net
From: Bill Hudacek <[EMAIL PROTECTED]>
Date: Sat, 22 Jul 2006 00:07:58 -0400
Subj: Re: [BackupPC-users] NT_STATUS_LOGON_FAILURE after samba update

Les Mikesell wrote:
> On Tue, 2006-07-18 at 21:57, Bill Hudacek wrote:
> 
> Is  there some subtle difference in your $Conf{SmbClientFullCmd} and
> $Conf{SmbClientIncrCmd} entries?  Can you execute something
> resembling the expanded incremental command manually with
> smbclient?
> 

Thanks, Les, for the reply.  I've been busy, and that's one of the 
things I've checked.

What it comes down to, isSamba 3.0.23-1 broke my system.  I'd setuid 
the smbclient and mount.cifs commands on disk; it complained until I 
removed that permission bit from those files.  That didn't fix the 
backuppc problems (though I held my breath as I tested again).

[It turns out smbmnt is /not/ based on "libsmb" - which is why samba was 
complaining and bailing - nothing based on this library can be suid 
anymore, fyi...so I simply setuid that executable.  Bob's your uncle.]

Prepare for this upgrade, folks! They're trying to improve the world 
over at Samba-land, and we're gonna be hurtin' until we figure all this out.

I still have no idea why logins only fail on incrementals.

I've upgraded to BackupPC v3.0.0beta0, but the smbclient command lines 
for SMB-based incremental, full, and restore are the same as in past 
versions :-/  No satisfaction there.  I tested anyway, but you already 
know how that story turns out.

I've been through the entire release notes for this version of Samba - 
my prev version was 3.0.14a-2 (fedora core-4) - and there are literally 
thousands of changes.  My eyes are bleeding.  Nothing jumped out at me, 
no eureka moment...

We need a Linux kernel approach for samba, it would seem, where 
even numbers and odd numbers are used for stable versions and for 
massive changes, respectively - and those unstable versions are not 
pushed out to every computer in the world!  

Is anyone else running this version of samba? If so, is it working for 
you?  I'll work this problem from both endsif anyone has any info, I 
would be grateful.

I'd go back, but the idea is that sofwtware changes are *for the 
better*, and the Samba guys have as good a rep as anyone.  I'm going to 
try to fix this before I punt and downgrade.

I'm simply running a full backup on each machine that has not been 
backed up for the last week or so!  I would have punted days ago if 
I didn't have this escape hatch.

Complicating things is the fact that I have this half-a-terabyte volume, 
and it's 95% full, because I have it retaining nearly every backup I've 
ever doneso I really reduced the retention figures, and now 
BackupPC_trashClean is going nuts - it's already returned nearly 4 
GB...and I have this feeling it'll be running all night - or all weekend :-)

More as it happens

Thought for the day: Fedora makes "trailblazers" of us all, I think, 
when you have an untested combination of software - like BackupPC and Samba!

/bill

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Archive file name question/change

[Craig Barratt]

Tim writes:

> Is there a reason why archives made with "-1" as the backup number are 
> saved as "-1" instead of the actual backup number that was used?  If 
> not, would you accept a patch that changes it to use the actual backup 
> number instead (assuming I can figure out how to make the change, of 
> course...)?

That makes sense.  In bin/BackupPC_archiveHost you can just read the
backups file and use the one-liner from bin/BackupPC_tarCreate.

Craig

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Bug: Cannot use rsyncd on RHEL4 hosts: child exited prematurely

[Timothy J. Massey]

"Joe Casadonte" <[EMAIL PROTECTED]> wrote on 01/29/2007 
10:42:32 PM:

 > On Mon, 29 Jan 2007, Timothy J. Massey wrote:
 >
 > > [EMAIL PROTECTED] wrote on 01/29/2007
 > > 07:01:03 PM:
 > >
 > >  > Also, you might crank up the timeout settings for just the
 > >  > failing hosts and see if it allows your backups to run longer
 > >  > before failing.  Your failures are right about 20 minutes into
 > >  > them, which is a suspiciously round number.
 > >
 > > Actually, you're seeing it after it's done dozens of failed
 > > attempts.  Each attempt copies a few files and then dies.
 >
 > So it successfully copies a few files and then dies?  Does the next
 > attempt pick up from where it left off or start all over again?

Yes.

 > > After dozens of attempts, it takes 40 minutes before failure.  If I
 > > delete the host, it fails after a much shorter time.
 >
 > Delete the host?  Not sure I follow that.

rm -rf the files in the host directory, so that it starts from scratch, 
instead of using the partial.

Tim Massey

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Submitting an archive via BackupPC_serverMesg in a scriptable way

[Holger Parplies]

Hi,

Timothy J. Massey wrote on 29.01.2007 at 01:46:34 [[BackupPC-users] Submitting 
an archive via BackupPC_serverMesg in a scriptable way]:
> 
> Here are some notes on how to submit an archive job to BackupPC in the 
> same way that the GUI does.

thank you for sharing the result of your research. I've hacked together a
Perl script which accepts a few command line options to do what you've
described, copying a lot from what you wrote. I'm not claiming that it's
brilliantly coded, complete, or even works (well, it's meant to ...). I
wanted to try out using BackupPC::Lib functions, and might as well share
the result, in case it's useful to someone.

> [Generation of request file name]
> No matter:  the file name is not very important at all:  from what I can 
> tell, the whole file name could be completely random.  So, onward we go.

I'll stick to it in my example for consistency.

> Here is the contents of a sample file made by selecting localhost, and 
> accepting the defaults (at least, as I have them configured):

Please correct my comments if they're wrong.

> %ArchiveReq = (
>'archiveloc' => '/var/lib/BackupPC/removable',

That's where the archive goes. Can be either a special file (eg. tape,
partition) or a directory. -o option for my script (default
/var/lib/backuppc/removable, because I use Debian ;-).

>'reqTime' => '1170042557',

Time the request file is generated (Perl: time()). Not important except for
reference. Actually, since the request file is interpreted as Perl code, you
*could* write
 reqTime => time (),
in a 'static' request file instead. That would be evaluated whenever the
request file is read, which may or may not be better than leaving a fixed
value. I substitute the value according to when my script is run.

>'BackupList' => [
>  '12'
>],

List of backup numbers to archive. Corresponds element by element with
HostList below, i.e. for archiving backup 1 on host1 and backup 2 on host2
you'd have BackupList = [1, 2] and HostList = ['host1', 'host2'].
-n option for my script, eg. -n 1,2 (default -1 = last backup).
I don't know how meaningful more than one entry is, but it *is* an array,
and BackupPC::Xfer::Archive loops over them, so ...

>'host' => 'archive',

Name of archive host. -a option for my script.

>'parfile' => '5',
>'archtype' => '0',
>'compression' => '/bin/cat',
>'compext' => '.raw',

I left those as they are and otherwise ignored them. Adding options to make
these variable is left as an exercise to the reader ;-).

>'HostList' => [
>  'localhost'
>],

List of host names to archive. See 'BackupList'. -h option for my script.

>'user' => 'backupuser',

I ignored that, except for providing a -u option defaulting to 'backuppc'
(and using that for the '' parameter as well).

>'splitsize' => '000'

Ignored. Is that an octal zero, by the way?

> );

Looks sad, but it's just the closing brace of the list assigned to the hash
%ArchiveReq and the semicolon ending the statement. (;

> How Your Code Can Submit an Archive
> ===
> 
> [...]
> 
> There are two problems with this.  The first is that the specific backup 
> number to be archvied (BackupList) is hard-coded.

Solved by providing a command line option, verifying existance of the specified
backup beforehand (or at least trying to) and changing negative values to the
corresponding backup number for your convenience :).

> The second problem is the fact that the time the job was requested 
> (reqTime) is also hard-coded.

Also solved.

> Once you have created the request file in the proper directory, you 
> simply tell BackupPC to process it.  That can be done easily from the 
> command line:
> 
> __INSTALLDIR__/bin/BackupPC_serverMesg archive   
> 

You'll need to check and probably change the two paths in the 'use lib' and
'use constant' lines.

Does anyone know whether the  parameter has to be a "valid" user, as
far as BackupPC is concerned?

> This will run your job just as if you had submitted it from the GUI.  It 
> can be scripted from wherever you would like, such as from a crontab, 
> just as easily as using BackupPC_archiveHost.

Note that you'll need permissions on the pc directories, so you're probably
best off to run it as backuppc user. If you do at all, that is. Disclaimer:
USE AT YOUR OWN RISK. It's like IP: best effort, no guarantees :).

> Notes about Archive Parameters
> ==
> 
> I have not delved extensively into the code to find out exactly how each 
> parameter is parsed, and what (if any) error-checking is done.

Neither have I.

> ** First, why is there a user parameter on the command line, when the 
> request file also contains this information?  How are they used?

I decided to supply the same user name in both places.

> ** Second, how is reqTime used?

I'd guess for generating correct output about when the job was submitted
via the CGI interface. Mightn't it run arbitrarily