This information is intended for use by Calendar Server 7 installations that use the MySQL database for the calendar store.
Calendar store backup and restore is one of the most important administrative tasks for your Calendar Server deployment. You must implement a backup and restore policy for your calendar store to ensure that data is not lost if problems such as system crashes, hardware failures, or accidental deletion of information occur.
This information describes your options for backing up and restoring the calendar store (MySQL database). You need to understand the pros and cons of these solutions to make the proper choice for your deployment.
You can also use backup and restore to migrate data from one Calendar Server host to another.
For general information about MySQL backup and restore, see http://dev.mysql.com/doc/refman/5.1/en/backup-and-recovery.html.
The following lists recommended backup techniques for the calendar store:
- File system snapshots (that is, ZFS Snapshots)
- Use ZFS snapshots to produce a snapshot of the file system containing the MySQL database. Then use ZFS send or a third-party file system backup software to back up the snapshot. See http://docs.sun.com/app/docs/doc/819-5461/gavvx?a=view.
- MySQL Async Replication
- Use MySQL replication to replicate the databases. See http://dev.mysql.com/doc/refman/5.1/en/replication.html.
- MySQL online logical backup
- Use mysqldump to back up the databases. See http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html
- Amanda: For information about the integration of ZFS snapshots with MySQL and Amanda Enterprise 2.6 Software, see http://www.sun.com/bigadmin/features/articles/zmanda_sfx4540.pdf
- Innodb Hot Backup
- Innodb MySQL online backup tool: http://www.innodb.com/doc/hot_backup/manual.html