>I solve this using a custom cron script that calls mysqldump on the remote >machine before calling amdump, and I save the generated dump file, not the >raw MySQL files. > >Big win, because it means that I can use this dump to restore the database on >_another_ machine without any problem (granted, I always use the same charset >for MySQL databases, so it's easier).
Could you explain me more details on custom cron script and charset for MySQL databases? -- View this message in context: http://www.nabble.com/MySQL-Integrity-tf4389486.html#a12517443 Sent from the Amanda - Users mailing list archive at Nabble.com.
