by Liem Nguyen, Corporate Communications Manager — February 01, 2010
This is in followup to my post on performance considerations for automated tiered storage. In a recent blog, Martin Glassborow @storagebod posed some good questions about how admins can stay ahead of data loss in a tiered storage environment. He asked for vendor feedback, so this is Compellent’s.
In a Compellent storage system, customers can specify the volumes that get automatically tiered, so you know what applications are tiered and which ones aren’t. A customer may even choose to “lock” an application/volume to a single tier for a specific business reason.
In a tiered environment, or any for that matter, we also recommend clustering controllers for load balancing and failover (the Compellent controllers don’t have to be the same model so you can cluster a 1st generation controller from 2004 with a currently shipping controller).
In case of physical disk failure, our PhoneHome proactive monitoring will alert both the customer and Compellent Copilot team. Often, a new drive is dispatched before the customer is even aware there’s a problem. In the meantime, hot spares can be used for rebuild. Because with thin provisioning we only use up space when data is written, generally rebuild times are faster than for those drives with a bunch of zeros written to them (ie. In SANs using RAID ranks and groups).
In case of data loss, admins can also roll back to locally stored replays (pointer based snapshots) to quickly recover a volume without having to declare a DR scenario. If it’s a physical server issue – say a power supply conks out - customers can use replays in conjunction with boot from SAN to quickly boot and configure a bare-metal standby server with an image centrally stored on the SAN, and mount the volume to the new server. The administration for the entire process can be handled in several ways – via click-through menus from the Storage Center GUI, scripting using PowerShell cmdlets for Windows servers, or the command utility.
If you do have to declare a DR scenario, you can use Enterprise Manager software to initiate failover to replicated volumes stored at the DR SAN site. Enterprise Manager can be accessed remotely and can used to manage replication between multiple sites. Within Compellent’s environment, a production SAN with automated tiered storage can replicate to a secondary site that’s configured as a single or multiple tiers of completely different storage type, RAID level and speed. This lowers the overall cost of replication and DR because you don’t need a copy-exact config between the two sites to do replication. Some customers want the DR SAN to be a full production site for business continuity purposes so may deploy automated tiered storage at the second site too. Then you can revert back to the primary SAN after you’ve resolved whatever issues caused you to declare a disaster. Enterprise Manager also provides dashboards and reports so admins can monitor capacity utilization by volume, RAID level, disk type and business unit, and the status of the tiered or untiered storage at any site.
A lot of buzz is being generated about automated tiered storage but what’s most important is to think about tiered storage as an integrated part of a Fluid Data environment. What other aspects of automated tiered storage are you thinking about?
by Liem Nguyen, Corporate Communications Manager — January 28, 2010
I’ve been eating crow from my last post on the hapless Vikings, so it’s taking me a little bit to respond to recent blogs by Hu Yoshida and Martin Glassborow. Hu’s focuses on different aspects of tiering whereas Martin’s frames tiering within the context of disaster recovery and asks vendors to clarify how they approach risk management – both topics of much interest and debate here at Compellent. I thought I’d offer a few thoughts on performance and data protection with respect to automated tiering and how it all relates to storage virtualization, thin provisioning, replays (snapshots), boot from SAN and remote replication.
First, storage virtualization
From our point of view, storage virtualization means separating physical disk from logical volumes and virtualizing all the drives (SSD, FC, SAS, SATA) in a system into a single pool of storage. The performance of all the drives can be shared and the system spreads read/writes across all the disks regardless of type or speed. The way Compellent virtualizes storage, we don’t specify RAID ranks or RAID groups in the way other vendors do—you know who you are =), so the issue of RAID rank loss that Martin talks about doesn’t affect a Compellent customer. Loss of a RAID rank is virtually impossible. The array can dynamically move data across different storage tiers at a very granular level—Compellent page sizes are 512KB, 2MB and 4MB—enabling applications and volumes to leverage tiers between disk types and RAID levels and spindle speeds. Also, with RAID 6 we protect against two drive failures in same RAID set (more on that later).
Additional performance considerations for automated tiered storage
Hu covered a lot of the different implementations of tiered storage and their benefits. However, I think he missed a few. Namely:
- Automated tiering inside the volume – Dynamic data movement between tiers certainly cuts storage costs but if the array is tiering data only at the volume level then the efficiencies of automated tiered storage are not being maximized. Better utilization, bigger cost savings and more fluid movement result if the array manages and tiers data inside the volume – at the block level, which is what Compellent does. In a Compellent architecture, written data associated with any volume or application can tier by frequency of use so that the active blocks stay on Tier 1 and inactive blocks cascade down to Tier 2 or 3 storage. An example is e-mail. The Exchange volume doesn’t have to be associated with a specific tier of storage, which means blocks of data representing old PDF or Powerpoint attachments can move to Tier 3 (along with read-only replays of the e-mail volume) while emails about a sales deal in progress stays on Tier 1. Same volume, different tiers, no admin intervention.
- Automated tiering within each drive – Let’s take the idea of tiering from within a volume and apply it to the physical tracks on a hard drive. Writing data on the outer edges of a drive helps speed up overall performance. It’s physics really. As data is read or written, the drive head moves across the disk platters from the outer to the inner tracks and back as the disk spins. So if the arm doesn’t have to move very far, the data gets read and written faster than if the arm has to move farther in. I’m grossly simplifying but you get the idea. Some vendors place entire volumes in the outer edge to improve performance. But they’re sacrificing disk utilization and efficiency. Compellent’s Fast Track technology by itself moves the active blocks stored in every drive to the outer tracks for performance (the “fast tracks,” get it?). Inactive data gets written to the inner tracks. When you combine Fast Track with automated tiering, this block-level analysis and movement of active/inactive data happens across all the drives across all the tiers.
- Automated tiering based on spindle speed – Take SAS drives. Tiering between15K and 7200 rpm SAS, especially if you do it within the same enclosure, means small enterprises can think more seriously about automated tiered storage at lower cost. Likewise, if you started out with shelves of 10K FC drives you could just add 15K FC as Tier 1 and get more use out of the relatively slower FC drives. Or you could add SSD and SAS or SATA tiers, whichever makes sense. The point is if you’re using different speeds of the same drive type you should be able to tier between them.
- Automated tiering between RAID levels – Data movement at a block level enables tiering between RAID 10, RAID 5 or RAID 6. A lot of people don’t implement RAID 6 because of the performance overhead with writing double parity for RAID 6. In Compellent’s tiered storage, active data is written to RAID10 first and then the inactive data is dynamically moved to RAID 6. There’s a better balance of performance and fault tolerance, and the RAID6 write penalty is essentially eliminated.
In my next post I’ll cover the data protection and risk management aspects of automated tiered storage.
by Liem Nguyen, Corporate Communications Manager — January 22, 2010
If you don’t know anything about Minnesota other than the 10,000 lakes and the winter wonderland weather, you should know that a lot of folks here are pretty passionate about Vikings football. Take for example, our sales rep Ross Smith. Normally, he builds and strengthens relationships with Compellent channel partners. But during the season, he’s been dressing like this for every home game at the Metrodome. And since the Vikings are playing the Saints this weekend in the NFC Championship game, he came into work today dressed and ready to rush the competition. If I were EMC and NetApp I’d try to avoid getting sacked. =) Skol Vikings!