Thank you Jon, Joe, and Richard.
I guess I'll leave things as they are and continue to monitor daily.
Fortunately, only up to 3 years worth of data needs to be kept "live" in the
master-slave db's, so there is a limit to how much data I will have to cope
with.
David
On Tue, October 3, 2006 9:29 am, David Giragosian wrote:
> So, Question 1 is: does mysqldump's connection to the slave db exist
> for the
> entire script execution time, or just for the length of time of its
> own
> execution?
exec() runs its own little mini-not-quite-shell, so as soon as it
ends,
1. mysqldump will only keep the connection open for as long as it
needs it. Once your calling script is allowed to continue mysqldump
has either exited successfully or with an error, but either way the
connection should no longer be active.
2. I don't think that would be a good idea. 30 min
David Giragosian wrote:
So, Question 1 is: does mysqldump's connection to the slave db exist
for the
entire script execution time, or just for the length of time of its own
execution? I imagine if I used mysql_connect() in the script that it
would
be for the entire length of the script executi
Howdy Guys,
I have a PHP backup script running as a cronjob that has an exec(mysqldump)
line followed a bit later by an exec(tar -cjf) line. The backup script runs
against a slave db in the wee hours, and the master gets a continuous stream
of inputs at the rate of about 18,720 per day. Obviously
5 matches
Mail list logo
