Template:ZRM ZFS snapshot requirements

MySQL Configuration Requirements

To take advantage of ZFS snapshots, all MySQL data and logs for databases/tables that belong to the backup set. The following are some of the possible configurations

• All MySQL data is on a single ZFS Volume
• Specific database directories are on different volumes
• For databases containing InnoDB-based tables, the snapshot can only be used if the database directory, the InnoDB data files and the InnoDB logs are all on ZFS volumes.
  • The InnoDB shared data files are on a separate ZFS volume
  • The InnoDB logs are on a separate ZFS volume

Pre-conditions for Using ZFS Snapshots

• The MySQL backup user (described in System Requirements) must be granted sudo privileges to execute ZFS commands on the MySQL server. Add a line similar to the following example to /usr/local/etc/sudoers on the MySQL server:

mysql MySQLserver.mycompany.com=NOPASSWD:/usr/sbin/df,NOPASSWD:/usr/sbin/zfs

where MySQLserver.mycompany.com is the fully-qualified domain name for the MySQL server. If MySQL database resides on the ZRM server, ZRM server name should be used. Note that if ZFS commands are installed in non-standard locations, the above example would not work without editing it to reflect the different paths.

* MySQLserver.mycompany.com name should be resolvable using hosts or nis (or any other authentication mechanism)
* To test sudo configuration, run the command as "mysql" user. Password prompt should not appear and the command should work. Example:
  # su - mysql
  $ sudo /usr/sbin/df

• 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 will be taken based on the storage engines of the tables in each of the databases.

Refer to the Solaris ZFS documentation for details on ZFS administration.