Le mercredi, 31 janvier 2007 17:20, Carl Wilhelm Soderstrom a écrit :
You probably also want to change:
$Conf{MaxBackups} = 4;
to something lower. that's the number of backups which will run
simultaneously. I've found that the default of '4' is too high for most
backup servers, and that '2'
Le jeudi, 1 février 2007 11:01, vous avez écrit :
Linux sees four processors in my servers: Intel(R) Xeon(TM) CPU 3.20GHz
So 4 is a good number for me? There are only 2 physical CPUs however.
Hyperthreading (at least I guess 3.2GHz Xeons are hyperthreaded, and not
dual-core) doesn't give you
The real question is why your backups and your nightly runs are taking
so long to complete.
One reason might be network bandwidth. In which case, you're probably
stuck. I'm gonna guess this isn't the problem though. If you're on a LAN
almost certainly this isn't it. It's easy to measure this.
I have three servers (2.x) in production. One of them is backing up
three big fileservers. Any one of these backups can take more than
24 hours. I recently started full backups of each of the servers on
different days to see if I could stagger the network load, but it
looks like they're
On 01/31 02:52 , James Ward wrote:
I have three servers (2.x) in production. One of them is backing up
three big fileservers. Any one of these backups can take more than
24 hours. I recently started full backups of each of the servers on
different days to see if I could stagger the
James Ward wrote:
it looks like they're going to all get started at the same time again
due to waiting on the nightly process to complete after the longest
of these backups.
Does version 3 get me away from this scenario?
Yes. Version 3 doesn't need nightly processing to be mutually
