« Analyst Day Vision Themes: "Application Integration" and "Smart Copies" | Main | Tom Mendoza's "Three Step Management Algorithm" for Solving Any Problem »

March 22, 2007

Comments

Dave, the people who don't think power consumption is a problem are the ones who don't see the energy bill. If it doesn't benefit the storage or server admin to operate more energy efficiently, they're not going to see it as an issue.
Data Center Blog: Server Specs

Blake: Thanks for the correction! Yes, I meant gigabytes and not terabytes. It's fixed now.

Alex: I agree completely. A handful of big disks won't provide as much performance as many small ones. So you can't always move, but for data with lower performance requirements, there is an opportunity to save lots of power.

As John points out, an automated policy engine can be a good way to find and move rarely used data that probably doesn't need so much performance.

Dave, I couldn't agree with you more. I would add to your list, however, de-duplication and deletion. A simple tool to view files by age, filetype, user, creater, and last use, combined with a policy engine for migration and deletion can go a long way to cleaning up the data cabinet. And we need the IT department, not the facilities director, to pay for the electricity, power generators, and chillers.

... same power to run a 144 terabyte FC drive as a 750 terabyte ATA drive, so using the largest drives possible ...

Gigabyte, right?

Coming from the database workloads, I tend to count, first of all, the number of disk spindles and then capacity.
Blindly, going to 750G ATA drives in RAID 5 from 36G FC in RAID 1+0 just to save on power might be a disaster unless it's clear what are the performance requirements and whether the new storage infrastructure with 5 times higher capacity and 2 times less power consumption would be able to sustain the old workload.

The comments to this entry are closed.

Subscribe to This Blog




© NetApp, Inc.  |  "Safe Harbor" Statement  |  Privacy Policy