Limiting Super duper's FW transfer speed....

[tspore]

Here is a situation,
I have a few mac mini's and they are all connected to a G5 server. On the G5 I run mysql for the mini's & Put backups from the mini to a seperate drive on the server. But now I have come up with an issue. When the Super duper script runs, mySQL driven sites get well bogged down, fighting for the bandwidth to get through the FW connection. I was shuting down the public side of the websites weekly, but I would really like to do more frequent backup's than 1X a week.
So does someone know, or can someone point me to a way to limit the backup speeds on the FW connection?
The mini's only have 1 FW port... And no FW 800, or else I would be using that.
If I can keep the bandwidth that superduper pulls through I can upgrade to each mini gets backed up every other day, which I would prefer.
Many of my sites, are heavely accessed 24 hours a day, so shutting them down for even 30 minutes every other night isn't acceptable either.
Thanks
T

[dnanian]

Actually, try excluding the MySQL databases from the backup. My guess is that MySQL is switching into a "no cache" mode when you try to back them up directly.

Instead, I'd suggest using mysqldump to dump the database to a file before backing up. Exclude the "real" databases, and then you should be all set.

[tspore]

Quick reply, thanks!
Well the DB's are on the G5 already and seperate from the webservers, because on the G5 I have redundancy, so that they are backed up already. They communicated to the other 2 servers via FW, as does Superduper.
They do get dumped regularly.
But for example right now I was running a mini backup, and it was blowing through at 43 MB a/sec... This left no room in the FW connection for the mysql to transfer through on the connection when the 30+ member at this instant were accessing 1 of the 30 DB driven websites.
(Software on the sites such as Vbulleting, and joomla...)
So the only fix I see is to somehow tell Superduper to only read/write at 15-20 MB a second or some such thing.

[dnanian]

Got ya. Sorry -- I don't know of any way to limit our transfer rate other than perhaps nice-ing down the SDCopy process once it kicks off, but I don't even think that'd do it...