Sun Microsystems X4540 instruction

12 Configuring ZFS Snapshots

Sun Microsystems, Inc.

To take advantage of ZFS snapshots, all MySQL database files (data, log, indexes) belonging to the backup set must be stored in ZFS volumes to ensure consistency. If any of the files are not on ZFS volumes, a raw backup (using mysqlhotcopy) or a logical backup (using mysqldump) is performed, depending on the storage engines of the tables in each of the databases. Refer to the ZFS documentation mentioned in the “For More Information” section at the end of this document for details on ZFS administration.

Here are some valid scenarios for database storage on ZFS:

•All MySQL data is stored on a single ZFS Volume

•Specific database directories are stored on different volumes

Note: For databases containing InnoDB-based tables, the snapshot can be used only if the database directory, the InnoDB data files, and the InnoDB logs are all on the same ZFS volume.

Choose the preferred method of snapshot backup using the drop-down menu. The Standard (Copy) option specifies that the snapshot should be copied to a specified earlier backup location on the Sun Fire X4540 server. The Quick (No Copy) option specifies that the snapshot itself should be used as a nearline backup.

Quick backups are convenient because they provide faster backups and restores, but because they remain on the MySQL server, they do not protect against disk or server failure. Quick snapshot backups can be converted to standard backups stored on the ZRM server using the Convert Backup option available from the Reports menu tab.

To enable backup via a snapshot, Backup Mode (selected from the upper left of the Backup How page) must be Raw. If the current backup mode for the set is Logical, you cannot select a snapshot plug-in from the Backup How page.

The ZFS snapshot does not require additional parameters.

Using Sun Fire X4540 Server With Zmanda Recovery Manager 2.2 for MySQL Database