6 Configuration | Sun Microsystems, Inc. |
root@thumper1 # zpool list |
|
|
| ||
NAME | SIZE | USED | AVAIL | CAP HEALTH | ALTROOT |
nbupool | 18.1T | 58.6G | 18.1T | 0% ONLINE | - |
The size listed in the above command is the actual physical space in the pool. This may differ from the actual space data may occupy as various RAIDZ methods and configurations are not taken into account. See the zpool(1M) man page for more details.
ZFS Configuration
In this example, the X4500 Media Server is configured to write to Basic Disk Storage Units. Each Storage Unit is created from a ZFS filesystem mountpoint. The number of filesystems needed will be a implementation by implementation decision but a few factors should be considered.
•Number of Backup/Recover streams needed
•Number of duplication or stage operations needed
•Number of Tape Drives configured for duplication or stage operations
In this example, 4 backup filesystems are created (/backup1, /backup2, /backup3, /backup4). Testing has shown that creating a single ZFS filesystem for all backup streams is a bottleneck that limits the throughput to
Example ZFS filesytem creation script:
#!/bin/bash for fs in 1 2 3 4 do
zfs create
root@thumper1 # zfs list |
|
| ||
NAME | USED AVAIL REFER MOUNTPOINT | |||
nbupool | 46.8G 14.2T 39.1K /nbupool | |||
nbupool/backup1 14.8G | 14.2T | 14.8G | /backup1 | |
nbupool/backup2 10.8G | 14.2T | 10.8G | /backup2 | |
nbupool/backup3 5.38G | 14.2T | 5.38G | /backup3 | |
nbupool/backup4 15.8G | 14.2T | 15.8G | /backup4 | |
