Backups
[http://www.amazon.com/gp/product/B004VJ46M4/ref=as_li_ss_il?ie=UTF8&camp=1789&creative=390957&creativeASIN=B004VJ46M4&linkCode=as2&tag=xen02-20] In my quest to restore some binaries from a Windows client to a Linux client (an unsupported operation) with NetBackup I had to trim off a
MySQL
Backing up MySQL used to be quick, easy and silent using mysqldump, but more recent versions of MySQL produce the following nagging warning: mysqldump -u root -p --all-databases --single-transaction > bak.sql Enter password: -- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly. If you'd like
MySQL
The following SQL will create a MySQL user with the minimum number of privileges necessary to backup databases: CREATE USER 'backup'@'localhost' IDENTIFIED BY '#PASSWORD#'; GRANT SELECT, RELOAD, FILE, SUPER, LOCK TABLES, SHOW VIEW ON *.* TO 'backup'@'localhost' IDENTIFIED BY '#PASSWORD#' WITH MAX_QUERIES_PER_HOUR
CLI
If you keep your database backed up into a single SQL dump and want to retrieve only the part matching one database, perhaps to transfer to another system, I find the simplest and most re-usable trick is to use sed's "p" function which prints the "pattern space" to STDOUT even
Backups
I'm currently using s3sync [http://s3sync.net/wiki%22], a ruby script that gives rsync like functionality with Amazon's S3 service, to store some of my more irreplaceable data. However it looks like maintenance of the program has become a bit spotty. The latest updated version can be found on