News
8/15/2008
05:38 PM
George Crump
George Crump
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Oh, Tier 3...

Remember about five years or so ago when life was simple? We had fast SCSI and Fibre Channel drives for data and we had tape for backup. Seemed perfect. Then came the ATA-based drives, and you were told to move your older data to them and start sending backups to disk. Then powering the data center and storage in particular became a problem; another use for ATA, put them in stand-by mode, spin them down, put them to sleep, and then eventually turn them off. As is usually the case, the hardware i

Remember about five years or so ago when life was simple? We had fast SCSI and Fibre Channel drives for data and we had tape for backup. Seemed perfect. Then came the ATA-based drives, and you were told to move your older data to them and start sending backups to disk. Then powering the data center and storage in particular became a problem; another use for ATA, put them in stand-by mode, spin them down, put them to sleep, and then eventually turn them off. As is usually the case, the hardware is ahead of the software and there's limited automation to leverage all of this, so what's a user to do?There are so many variations on Tier 3 that it's hard to categorize this entry and catch every permutation. First, what type of data should go on Tier 3? Ideally, everything that isn't currently being accessed (old data) or copies of current data where there is value in freezing the state of that data for some reason; for example, a database archive or a copy of a PowerPoint presentation that you are going to modify heavily. However, this data does NOT include backup data. That data needs to go on another disk tier: Tier 4. Tier 3, then, is essentially data at rest, but data that might need to be accessed in the future, so you want to keep it on a medium that can still deliver that data back to you in short order. The challenge has been to understand how the various manufacturers have responded to this market. One of the first incarnations and one of the most popular still today is manufacturers are just adding shelves with ATA drives to their existing systems or adding just an external box of cheap ATA RAID. Both of these strategies have limited value, unless you have a specific need for a scratch area or something of that nature. The exception being some storage systems that can auto-migrate old data blocks to this storage on an as-needed basis. If your storage system can't do this for you automatically, either change storage systems or don't use Tier 3 storage in this manner. Regardless of the capabilities of your Tier 1 or 2 offering, where things get interesting is with systems that are focusing specifically on the data-retention market. They address key requirements like portability, scalability, density, power management, data integrity, and cost efficiencies that the ATA in shelf solutions lack. By moving (not copying) data either manually or in an automated fashion, you can move this data off primary storage, while at the same time giving yourself a data vault. When I mention a data vault or retention, the first thought is usually compliance or litigation readiness. While these are important, think of the vault from another value ... assets. As the wealth of retained information grows and the ability to index its content improves year by year, data as an asset will be a key strategic initiative in many enterprises. The common requirement in data indexing will be the ability to access that data. What (if anything) you choose to index, the application today may be different than what you choose to index with tomorrow. Having that data stored in a simple open interface file system like CIFS or NFS will be critical. Next we will finish up our "Tour of Tiers" with Tier 4.

Track us on Twitter: http://twitter.com/storageswiss.

Subscribe to our RSS feed.

George Crump is founder of Storage Switzerland, an analyst firm focused on the virtualization and storage marketplaces. It provides strategic consulting and analysis to storage users, suppliers, and integrators. An industry veteran of more than 25 years, Crump has held engineering and sales positions at various IT industry manufacturers and integrators. Prior to Storage Switzerland, he was CTO at one of the nation's largest integrators.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Threat Intel Today
Threat Intel Today
The 397 respondents to our new survey buy into using intel to stay ahead of attackers: 85% say threat intelligence plays some role in their IT security strategies, and many of them subscribe to two or more third-party feeds; 10% leverage five or more.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-2595
Published: 2014-08-31
The device-initialization functionality in the MSM camera driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, enables MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl calls for an unrestricted mmap interface, which all...

CVE-2013-2597
Published: 2014-08-31
Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that lever...

CVE-2013-2598
Published: 2014-08-31
app/aboot/aboot.c in the Little Kernel (LK) bootloader, as distributed with Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to overwrite signature-verification code via crafted boot-image load-destination header values that specify memory ...

CVE-2013-2599
Published: 2014-08-31
A certain Qualcomm Innovation Center (QuIC) patch to the NativeDaemonConnector class in services/java/com/android/server/NativeDaemonConnector.java in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.3.x enables debug logging, which allows attackers to obtain sensitive disk-encryption pas...

CVE-2013-6124
Published: 2014-08-31
The Qualcomm Innovation Center (QuIC) init scripts in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.4.x allow local users to modify file metadata via a symlink attack on a file accessed by a (1) chown or (2) chmod command, as demonstrated by changing the permissions of an arbitrary fil...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.