From: Micah Anderson Date: Sun, 6 Jul 2008 17:58:52 +0000 (+0000) Subject: clarify how the nodata option should be specified in the config file for mysql X-Git-Tag: backupninja-0.9.6~2 X-Git-Url: https://git.stderr.nl/gitweb?p=matthijs%2Fupstream%2Fbackupninja.git;a=commitdiff_plain;h=cb833ea82cbc59e14fc1f0b71e2cebdf88ff30d0;ds=sidebyside clarify how the nodata option should be specified in the config file for mysql --- diff --git a/examples/example.mysql b/examples/example.mysql index d22cbcb..bd996e7 100644 --- a/examples/example.mysql +++ b/examples/example.mysql @@ -53,12 +53,14 @@ compress = yes # which databases to backup. should either be the word 'all' or a # space separated list of database names. # -# nodata = < table1 table2 table3 > (no default) +# nodata = < db.table1 db.table2 db.table3 > (no default) # only dump the structure for the database tables listed here, this means # no data contained in these tables will be dumped. This is very useful # to backup databases that have tables with large amounts of cache data that # isn't necessary to backup, but you still need the structure to exist -# on a restore +# on a restore. You *must* specify the table as part of a database, such +# as "drupal.cache", where the database name is "drupal" and the table that +# you do not want to dump the data for is called "cache". # # backupdir = < path/to/destination > (default = /var/backups/mysql) # where to dump the backups. hotcopy backups will be in a subdirectory