On 11/29 07:56 , dan wrote:
> not the linux scheduler, the backuppc backup scheduler :) it just counts
> days with no awareness of months. also, i cannot know that last day of
> business unless it had some interface that you could schedule that.
ah, I see.
perhaps at some point in the distan
not the linux scheduler, the backuppc backup scheduler :) it just counts
days with no awareness of months. also, i cannot know that last day of
business unless it had some interface that you could schedule that. i have
good luck with the default linux scheduler. no issues
cygwin+rsync wont act
On 11/28 08:46 , dan wrote:
> i dont know if ditching the build in scheduler is an option for you
Presuming you're talking about changing the linux I/O scheduler; which one
did you find works best for you?
i am currently
> using the built-in scheduler but it isnt sophisticated enough for my nee
i dont know if ditching the build in scheduler is an option for you but i
will give a little idea of a test environment i am running. i am currently
using the built-in scheduler but it isnt sophisticated enough for my needs.
I am having the client initiate the backup with an ssh session. i have
On 11/28 09:00 , John Rouillard wrote:
> To do this, I limit the number of simultaneous backups to 4, and use
> --bwlimit 100 to limit the sending rsync speed. This gives us a total
> of 3,276,800 bits/sec approx. It can be a bit higher at tims, but
> averages out.
I've never had good luck doing m
Hi all:
We use backuppc to perform backups of 70 odd systems at remote sites
to our main servers over the internet. As a result we have a bandwidth
limitation of 5Mbit/sec that we don't want to exceed.
To do this, I limit the number of simultaneous backups to 4, and use
--bwlimit 100 to limit the
