Les Mikesell wrote:
You are probably short on RAM when you add in the nightly run. Tuning down the number of concurrent backups might help. That probably shouldn't be higher than the number of processors in the server anyway unless you have some low-bandwidth connections to handle.Then why is MaxBackups set to 4 by default? I don't think 4 processors are the standard yet...If the client side is slow or on a slow network branch, having more running would help. With fast local clients the bottleneck is more likely the CPU or disk seek time.
All my clients are servers with fast connections. I'll take MaxBackups down to 1 then.
Still, I used BackupPC with MaxBackups set to 4under 2.1 and the server only has a single Pentium 4 processor. I have now taken MaxBackups down to 2, but we're still seeing a lot of failing backups.Do they fail at all times or only when the nightly run happens concurrently?
I've changed the WakeupSchedule so there are a few backup-free hours for the nightly runs. Backups are still failing (certainly the two backups that are started together with the nightly runs), but they were failing more before this change.
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/
