
Testing the Sun Fire X4500 Server as Network Attached Archival Storage
for the Enterprise Vault/SAM Solution
Hardware and Software
• Solaris 10 (8/07) OS
• SAMBA 3.0.25a (included in Solaris 10 8/07 OS)
• Sun StorageTek SAM 4.6
• Solaris ZFS
• Sun Fire X4500 Server configured with 48 x 500 GB SATA-II disks
Performance Tests
Extensive testing took place in Sun Microsystems' Labs in Colorado to determine the best way to configure a Sun Fire
X4500 Server as Network Attached Archival Storage for Enterprise Vault and SAM. The high-level design had a single
SAM file system shared with Enterprise Vault via SAMBA, making Copy 1 to a local SAM disk archive. However, there
were two dilemmas:
● One ZFS Storage Pool or Two? With one storage pool, all disks are available to support the write-intensive
workload, but the data in the SAM file system and the copy in the SAM disk archive would be in the same
storage pool and potentially on the same disks. Even with RAID protection and hot spare disks, some
organizations could not accept this risk. With two storage pools, the SAM file system and SAM disk archive are
in different storage pools, and so on different disks. This is secure, but fewer disks are available for the
workload.
● Can we use RAID-Z? If the write-intensive workload did not suit a RAID-Z configuration, the alternative, RAID-1,
would reduce the usable capacity.
The three configurations in Table 1 were stress tested on the equipment shown in Figure 3.
Case Number of ZFS Storage Pools ZFS Storage Pool Configuration
1 1 22 x RAID-1.1+1 stripes and two hot spares
2 1 8 x RAID-Z.5+1 stripes and six hot spares
3 2 2 x 4 x RAID-Z.5+1 stripes and three hot spares
Table 1: Tested Storage Configurations
Configuring the Sun Fire X4500 Server as Network Attached Archival Storage for Symantec Enterprise Vault 6
Comentarios a estos manuales