2011/9/22 Markus Fröhlich <markus.froehlich AT xidras DOT com>:
>
> Writing tar archive for host hosting1, backup #24, split to output files
> /SATA/BackupPC/archive/hosting1.24.tar.gz.*
> exiting after signal ALRM
> Archive failed: aborted by signal=ALRM
>
> the strange thing is, that the duration shows ~1200 min  on both
> backupPC servers for the archive job, when it fails.
> is there a limitation anywhere in the code?

See $Conf{ClientTimeout}  (Under Backup Setting in the web editor).

But if you are driving things with a cron job and want better control,
why not just run BackupPC_tarCreate in your own script?  I think the
'archive host' concept just exists to give a web link you can click.

-- 
  Les Mikesell
    lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/