I think about including SnapRaid per default with napp-it
Reason:
- ZFS is superiour due to realtime checksums and unlimited snapshots
- ZFS Software Raid is superiour in data security, performance and is realtime
Limitations:
For a pure media server, where data mostly keeps the same, where data are not too valuable and the performance of a single disk is enough, there are some some limitations with any striped Raid (ZFS or other).
- Striped raid means, all disks are active during read or write, no one can sleep
- You only can expand a pool with other Raidsets like mirrors or Raid-Z if you like redundancy
- You cannot use different sized disks or the smallest determines the Raid-size.
This is where Snapraid can fill the gap and combine the best of both.
- Use ZFS Raid where you need the performance and the realtime Raid.
- Use Snapraid on ZFS for media data with different sized disks where unused disks can sleep. You can expand with any sized single disk.
How it can work:
- Use as many datadisks as you like, size does not matter
- Build a ZFS pool from each disk (1 disk=1vdev=1pool)
- Use one or two disks (must have the same size as the biggest datadisk) for redundancy
Use your datapools as usual, create zfs folders and share. If one Pool fails (due to no ZFS redundancy), the data of this disk/pool is lost. This is where Snapraid is used.
With snapraid, you can use one or two disks to save a raid-like redundancy information on one or two extra disks (similar to Raid5/6) but not in realtime but on demand. The consequence is, that you can only restore the state of the last Snapraid sync-run.
Snapraid is quite easy to use, its only a small app.
You can install via: (similar to http://zackreed.me/articles/72-snapraid-on-ubuntu-12-04)
You need to create a conf file with settings in /etc
To have it running quite maintenance, i think about using poolnames like snapraid_p1, snapraid-p2, snapraid_d1..snapraid_dn to have a setup that is working without extra setup together with a napp-it control menu and autojobs to sync timer based.
What I like to know now:
- Are there any known problems with OmniOS or OpenIndiana?
Reason:
- ZFS is superiour due to realtime checksums and unlimited snapshots
- ZFS Software Raid is superiour in data security, performance and is realtime
Limitations:
For a pure media server, where data mostly keeps the same, where data are not too valuable and the performance of a single disk is enough, there are some some limitations with any striped Raid (ZFS or other).
- Striped raid means, all disks are active during read or write, no one can sleep
- You only can expand a pool with other Raidsets like mirrors or Raid-Z if you like redundancy
- You cannot use different sized disks or the smallest determines the Raid-size.
This is where Snapraid can fill the gap and combine the best of both.
- Use ZFS Raid where you need the performance and the realtime Raid.
- Use Snapraid on ZFS for media data with different sized disks where unused disks can sleep. You can expand with any sized single disk.
How it can work:
- Use as many datadisks as you like, size does not matter
- Build a ZFS pool from each disk (1 disk=1vdev=1pool)
- Use one or two disks (must have the same size as the biggest datadisk) for redundancy
Use your datapools as usual, create zfs folders and share. If one Pool fails (due to no ZFS redundancy), the data of this disk/pool is lost. This is where Snapraid is used.
With snapraid, you can use one or two disks to save a raid-like redundancy information on one or two extra disks (similar to Raid5/6) but not in realtime but on demand. The consequence is, that you can only restore the state of the last Snapraid sync-run.
Snapraid is quite easy to use, its only a small app.
You can install via: (similar to http://zackreed.me/articles/72-snapraid-on-ubuntu-12-04)
The app is then in /usr/local/bin. I may include this in napp-itcd $HOME
wget http://sourceforge.net/projects/snapraid/files/snapraid-2.1.tar.gz
tar xzvf snapraid-2.1.tar.gz
cd snapraid-2.1
./configure
./make
./make install
You need to create a conf file with settings in /etc
To have it running quite maintenance, i think about using poolnames like snapraid_p1, snapraid-p2, snapraid_d1..snapraid_dn to have a setup that is working without extra setup together with a napp-it control menu and autojobs to sync timer based.
What I like to know now:
- Are there any known problems with OmniOS or OpenIndiana?
Last edited: