Am Samstag 22 September 2007 22:18 schrieb Matthias Meyer:
> Am Samstag 22 September 2007 13:51 schrieb Nils Breunese (Lemonbit):
> > Matthias Meyer wrote:
> > > Since some days the backup of 1,5 GB on one of my servers need more
> > > than 20h
> > > (both, the INCR as well as the FULL backup) and will aborting
> > > backup up
> > > after signal ALRM.
> > > What the reason for this signal ALRM?
> > > What the reason can be for need such a long time for backup?
> > > I use the TarClientCmd "$sshPath -q -x -n -l root $host env LC_ALL=C
> > > $tarPath -c -v --one-file-system -f - -C $shareName+ --totals" for
> > > this
> > > backup.
> >
> > $Conf{ClientTimeout} is set to 72000 seconds (20 hours) by default.
> > You might want to increase this value if your backups do not complete
> > within 20 hours. How is your client connected to your server? 20
> > hours is an awful long time for only 1,5 GB.
> >
> > Nils Breunese.
>
> In principal it is a 100MBit LAN. In this case it is the host machine.
> backuppc runs in a vmware on this host.
>
> Matthias
I found the following messages in log:
tarExtract: Unexpected end of tar archive (tot = 512, num = , posn = )
tarExtract: BackupPC_tarExtact aborting (Unexpected end of tar archive)
tarExtract: Done: 1 errors, 42700 filesExist, 497173333 sizeExist, 220546118
sizeExistComp, 42714 filesTotal, 498817301 sizeTotal
Tar exited with error 33280 () status
Got fatal error during xfer (Unexpected end of tar archive)
I use GNU Tar 1-16.2 from debian stable on both, backuppc and client which
have to backed up.
Matthias
--
Don't Panic
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
