View Single Post
  #2   (View Single Post)  
Old 28th November 2008
phoenix's Avatar
phoenix phoenix is offline
Risen from the ashes
Join Date: May 2008
Posts: 696

Originally Posted by mtx View Post
I have successfully configured ZFS using FreeBSD amd64 on a quad core box with 2Gb of RAM. With the proper tuning found on wiki, mailing lists on which i found a great post in which our phoenix clarified some things, the machine is stable.
You're a glutton for punishment. Put some RAM in that baby. You're starving your CPUs.

The new things that are coming with ZFS in terms of backup (snapshots & clones) are great, quick and easy to understand and manage. As far as i understood you can move the snapshots *only* between systems that are running ZFS (zfs send | receive) and archiving a snapshot. Now the first question, what are the implications of tar-ing or gzip-ing a snapshot and moving it to an outside storage which doesn't run ZFS, this in terms of the consistency of the snapshot.
Haven't played with the snapshot send/receive bits as yet (waiting for some multi-lane SATA to arrive so we can finish our second backup box).

The archiving of the data is great and reduces the space usage. Here comes the second question, which one of them to use lzjb or gzip. I did google for lzjb vs gzip but couldn't find a relevant answer.
lzjb requires the least amount of CPU, but only gives decent compression (don't expect more than 2:1). Use this for locations that you want to compress, but that are accessed frequently.

gzip requires more CPU, but gives much better compression rations. Use this for filesystems that won't get used as often.

I have a separate dataset for mysql (MyISAM). I have found an article on the website about zfs and mysql - A look at MySQL and ZFS but it only talks about InnoDB+ZFS optimization. Here i have a couple of questions too:
  • What recordsize to use for that specific data set?
Whatever you configure the record size in MySQL is what you use for the record size in ZFS.

  • What are the implications in term of performance if i compress the mysql zfs data set?
Considering how often MySQL data is accessed, you shouldn't compress it. You don't want anything to get in the way of your data I/O.

  • Other things i should take into account when using MyISAM + ZFS?
Only this: DON'T USE MYISAM! Really, just don't.

I would also like to hear anything about what techniques do you use for backing up a zfs system and anything you can recommend to read for a better understanding of the zfs concept as a whole.
Snapshots are your backups. Sending the snapshots to another system running ZFS is your off-server backups. And if that system is in another building, there's your off-site backups.

The OpenSolaris website is fount of ZFS info, as are the Sun blogs. Everything ZFS is located there, including the ZFS Admin manual.

Help for FreeBSD: Handbook, FAQ, man pages, mailing lists.
Reply With Quote