What to Backup

From The Open Source Backup Wiki (Amanda, MySQL Backup, BackupPC)
Jump to navigationJump to search

ZRM for MySQL does not impose any choice or restriction upon you, except that right now it backs up only MySQL databases. It gives you full flexibility to backup.

Specify What to Backup

  • All Databases
  • A number of databases
  • A single database
  • One or more tables from a single database
  • If you want to backup two or more tables from different databases, you can do so by specifying the names of different backup sets.
  • In one backup set, tables form one single database can be backed up.
  • You can exclude some databases from all databases or some tables from a database by specifying exclude-pattern wildcard expression. If you are using mydumper logical backup method, you will not be able to use exclude database/table options. For mydumper, you can use --regex mydumper option and can be specified using --extra-mydumper-options in the configuration file.

Databases/tables in the Backup Set

One of the all-databases or databases or tables/database parameters should be specified.

If none of them is specified, all-databases is assumed.

Default is backup set that contains all databases on the MySQL server.

all-databases
This parameter should be set to 1 if all databases are to be a part of the backup set.
host
Host name of the MySQL server.
databases
List of databases that are part of the backup set.
  The database names have to be separated by space character. 
  If all databases are part of backup set, use all-databases parameter. 
database
There can be only one database name specified as value.
   The tables specified in tables backup parameter should belong to the database specified in this field.
tables
List of tables that are part of the backup set.
   These tables should belong to the database specified in database backup parameter. 
   The table names should be separated by space character. 
   database backup parameter must be specified if this parameter is to be valid. 
   ZRM for MySQL does not verify database referential integrity of the backups. 
   Backup will fail if ZRM for MySQL does not find the specified tables in the given database.

Index File

ZRM for MySQL creates an index file for each backup run. The index file should not be read or modified by the user. This file is used for backup reports. All the fields can be obtained from backup reports.

The following fields in the index file specify the details of what was backed up.

raw-databases
List of databases that have raw backups - backups done using the mysqlhotcopy command.
 If the raw-tables field is present, all the tables listed in raw-tables belong to the 
 database in this parameter. 
raw-databases-snapshot
List of databases backed up using snapshots.
backup-type
Type of backup - regular or quick.
raw-tables
List of tables backed up using the mysqlhotcopy command.
  All the tables listed in this parameter belong to the database in the raw-databases field. 
  This parameter will have valid values only if --tables parameter was specified for the backup 
  run in the mysql-zrm.conf configuration file.
raw-tables-snapshot
List of tables backed up using snapshots. All the tables listed in this parameter belong to the database in the raw-tables-snapshot field.
logical-databases
List of databases backed up using mysqldump(1)
logical-tables
List of tables belonging to logical-databases backed up using mysqldump(1)
replication
Names of replication files that were backed up - namely master.info and relay-log.info
slave-load-files
Names of SQL_LOAD* files that were backed up
incremental
Names of Binary log files that are part of incremental backup.