CODEWITHSUNDEEP
mysqlubuntucron
Brian
Brian

Reputation: 6071

Creating a cron job for mysqldump

I'm trying to create a cron job for database backup.

This is what I have so far:

mysqldump.sh

 mysqldump -u root -ptest --all-databases | gzip > "/db-backup/backup/backup-$(date)" 2> dump.log

 echo "Finished mysqldump $(date)" >> dump.log

Cron job:

 32 18 * * * /db-backup/mysqldump.sh

The problem I am having is the job is not executing through cron or when I am not in the directory.

Can someone please advise. Are my paths incorrect?

Also, the following line I'm not sure will output errors to the dump.log:

 mysqldump -u root -ptest --all-databases | gzip > "/db-backup/backup/backup-$(date)" 2> dump.log

What worked:

 mysqldump -u root -ptest --all-databases | gzip > "../db-backup/backup/backup-$(date).sql.gz" 2> ../db-backup/dump.log

 echo "Finished mysqldump $(date)" >> ../db-backup/dump.log

Upvotes: 5

Views: 17428

Answers (1)

Brandon
Brandon

Reputation: 284

There are a couple of things you can check, though more information is always more helpful (permissions and location of file, entire file contents, etc).

  1. It can never hurt to preface the mysqldump.sh file with the Shebang syntax for your environment. I would venture to guess #!/bin/bash would be sufficient.
  2. Instead of mysqldump -u .... use the absolute path /usr/bin/mysqldump (or where ever it is on your system). Absolute paths are always a good idea in any form of scripting since it's difficult to say if the user has the same environment as you do.

As for storing the errors in dump.log, I don't believe your syntax is correct. I'm fairly sure you're piping the errors from gzip into dump.log, not the errors from mysqldump. This seems like a fairly common question which arrives at the answer of mysqldump $PARAMS | gzip -c dump-$(date)

Upvotes: 6

Related Questions