-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 13 Nov 2006 13:11:30 -0600
Carl Wilhelm Soderstrom <[EMAIL PROTECTED]> wrote:
> On 11/13 10:40 , Jacob S wrote:
> > If I understand backuppc correctly, a backup can not take longer
> > than 24 hours or it will end the job. (At least, that's the way it
> > seems to work on my backup servers.)
>
> no, there's a value set in config.pl:
> $Conf{ClientTimeout} = 7200;
> (at least this is the default from 2.1.2) which says that if a job
> runs that may seconds, it'll be killed after that point. it's pretty
> commonly upped, since the default is 2 hours.
>
> My jobs sometimes run more than 24 hours (tho usually that means
> something is wrong). if a job runs that long tho, it'll hold up the
> backups of all the other machines until it's done. (BackupPC_nightly
> has to run after the last job; and then the next set of backups can
> begin).
Reading about ClientTimeout in config.pl, it seems it only affects how
long backuppc waits to get data, not the overall time the job takes. I
know I have at least one client that commonly takes at least 6 hours to
do a full backup and other clients have errored out at the 24 hour mark,
yet my ClientTimeout is only set to 4 hours.
Jacob
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFWMp6kpJ43hY3cTURAtnMAJ4pk/CepE8ivLc6jm6Xu3Zo96p6FgCgk+li
lJrnAIxBgFjXpBj11IBPI8k=
=QoLW
-----END PGP SIGNATURE-----
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
