From: Steve C. <cam...@cn...> - 2007-10-04 17:48:02
|
Thanks Scott, Can I assume the script does all of the waiting required before starting the data backup? How would this differ from just setting up a shell script that has a mysqldump statement in it? I don't read Perl real well and didn't see anything that does that (at least based on my knowledge of Perl) and just skimming the file. Sorry do be demanding, but this is the crutch of the problem I had before. Any type of shell didn't return a code before timing out. The manual addresses this, but in a couple of different ways. At the present time, by doing the mysqldump from cron locally on the client, and using logrotate to keep the directory clean, it works pretty well, but still I'd like to get it working with the benefit of ClientRunBefore. Steve Scott Ruckh wrote: > > ----- Original Message ----- From: "Steve Campbell" > <cam...@cn...> > To: <bac...@li...> > Sent: Thursday, October 04, 2007 8:05 AM > Subject: [Bacula-users] Client Run Before job > > >> I gave up a while back on getting a job to run on the client before >> doing the backup. Mostly all I am trying to do is get an MySQL backup >> (mysqldump) to run before I do a backup job that includes the file just >> created. As I recall, I was having a problem with the return code >> indicating the job had completed. I tried all of the suggestions in the >> manual, to no avail. >> >> Anyone out there have a simple step by step set of rules, scripts, >> whatever to get this accomplished for both the director conf and the >> client scripts? >> >> Sorry to be so vague on the problem errors I received, but it's been a >> while back and I got pulled away for another little fire. Kinda new to >> bacula also, although I'm fairly certain I have RTFM concerning this >> area. For now, I just run a job in cron to do the mysqldump in time to >> have the output ready for the bacula backup, but it would be nice to >> have it all run together. > > Here is what I use: > http://www.worldcommunity.com/opensource/utilities/mysql_backup.html > > This is the directive I use in my job{} definition: > ClientRunBeforeJob= "/usr/local/bin/mysqlbackup/mysqlbackup.pl" > > Then of course my FileSet {} definition would include the directories > where the compressed archives have been created. > > As I use this configuration at home, it works fine for me. In the > version I am using, clear text password is stored in configuration > file so this would need to be evaluated in your environment. > > |