Not so long ago, I tested the Sun Fire X4500 Storage Server, aka Thumper, This wass a dual-CPU, dual-core Opteron-based server running OpenSolaris and housing a whopping 48 3.5-inch SATA drives, all within a 4U chassis. The sheer size and scale of that storage server could only be handled by Sun's own ZFS file system. Thumper was a tank in every sense of the word and carved a niche for itself in a wide variety of infrastructures.
Sun has taken that 48-drive behemoth and turned it into an appliance, the Sun Storage 7210 Unified Storage System. While its lineage is immediately clear, the 7210 differs from its predecessor in key ways.
First, the 7210 runs with two quad-core Opteron CPUs and 64GB of RAM, roughly doubling the processing power present in the original X4500. Second, it's a true appliance, not just a server. It does run OpenSolaris, but all interactions with the server are via the FishWorks GUI, not the command line. In fact, if you try to gain root access to the box via serial console, a large warning informs you that doing so will void the warranty, cause irreparable damage to the server, and possibly open a portal to another dimension. While this is somewhat disappointing from a flexibility perspective, the completeness of the FishWorks GUI makes up for it.
The 7210 isn't merely filled with SATA drives, either. In fact, there is a solid-state drive (SSD) present in the system, specifically designed for write operations. This SSD is configured as the ZIL (ZFS Intent Logging) drive and provides for faster access times for the file system, leaving the physical disks to handle the data storage tasks. Sun dubs this drive "Logzilla." It's an 18GB write-biased SSD in a 3.5-inch form factor, and aside from a slightly different bezel, it looks identical to the hard drives in the 47 other internal hot-swap slots. The system uses RAM as a read cache.
On the software side, the 7210 offers a wide range of file-serving protocols: NFSv3, NFSv4, CIFS, iSCSI, FTP, and HTTP. It supports onboard virus scanning; snapshots; cloning; compression; SNMPv3/v4; NDMP (Network Data Management Protocol) backups; and CLI scripting in Perl, Python, Java, and more. There's even an SSL-based phone-home option that can automate support services.
For authentication and authorisation, the 7210 can be linked to Active Directory, NIS (Network Information Server), or an LDAP server, or it can run with local users and authentication.
The FishWorks GUI is not only entirely web-based, but entirely AJAX. At first, I wondered how wise that might be, but after only a few minutes of use, I was smitten. It's very attractive and very accessible. In fact, it may be the most complete filer interface I've ever seen, blowing the doors off Network Appliance's web-based manager.
As a brief example, the dashboard display is a constantly moving visual representation of everything the 7210 is currently doing, providing instant feedback on load and throughput for any or all the protocols in use. The graph displays are not only clickable, but they can be arranged on customised worksheets to provide easy at-a-glance status reports. You can drill down (using the handy drill-shaped icon) into any graph to get more granular data and even pull up a list of files or users who are currently hogging the most bandwidth at that exact moment in time. This works at the file level in most protocols, so if the 7210 is being hammered, you can almost instantly determine not only who is responsible, but also what files are being accessed and from where.
The dashboard shows the various aspects of the 7210 itself, including network I/O, memory and CPU utilisation, and independent protocol statistics. Next to each graph heading is an icon representing the health of that particular data point, as denoted by a meteorological symbol. If the icon is a sun, all is well. Clouds indicate that the protocol or system component is working hard, while raindrops indicate that activity is really ramping up. A lightning bolt signifies that the protocol or component is running near capacity. Because the entire interface is constantly updating, it's possible to leave pages open at all times and get a to-the-second report on the filer's health.
Beyond the frankly stunning statistical representation, administering the 7210 is relatively straightforward, using drag-and-drop concepts to build link aggregation configurations and the like. I developed a love/hate relationship with this approach. For example, it's not immediately obvious why a link is or is not available to be configured, and you have to drag a physical interface around to link it. When dealing with configurations that can result in the box being completely inaccessible if a mistake is made, I prefer to have a much clearer representation.
That said, you won't configure the network interface very often; more likely, you'll need to perform it only once. Aside from this quibble, the configuration and management of the server are as easy as one could expect. There's no need for any CLI involvement, and creating storage pools, shares, quotas, snapshots, and such is really quite simple.
The FishWorks GUI ran without issue in Firefox on Linux and Mac OS, as well as in Internet Explorer on Windows.