News
8/25/2008
09:21 AM
George Crump
George Crump
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Migration Relief

In my last entry on migration migraines we discussed the challenges of moving from one primary storage provider to another and went through a few solutions. One of the best methods to make migrations easier is to keep the amount of data on primary storage at a minimum, but what do you do about archives that will grow to petabytes in size?

In my last entry on migration migraines we discussed the challenges of moving from one primary storage provider to another and went through a few solutions. One of the best methods to make migrations easier is to keep the amount of data on primary storage at a minimum, but what do you do about archives that will grow to petabytes in size?Moving from one primary storage platform to another is a fact of life. New suppliers will continue to emerge which offer compelling advantages over your current supplier, or new technologies altogether such as solid state disk may cause the need to change primary storage suppliers. The answer as I have written about is to move inactive data off primary storage as soon as you can. Keeping primary storage small not only keeps costs in line, it also makes migration between platforms easier by keeping the data set small.

The potential pitfall of aggressive archiving is that the capacity of that archive will and should get very large over time. Archives of 50 terabytes to 100 terabytes will become commonplace and over the next five or six years, PB-sized archives will not be uncommon. Data sets of this size not only make migration impossible; they make tasks like backup a challenge. Does this invalidate the disk archive concept? No. Growth is inevitable. You have to choose where you want that growth to happen and a platform to deal with that growth. As I stated in a prior post on the potential cost savings of archives, you want to grow your storage in the area where it costs the least and that area is the archive. How, then, do you deal with large archives? You need to design the archive to be a permanent fixture in the data center. The answer is scalability, massive scalability. This is where "real" archive solutions come into play, systems that were designed from the ground up to provide archiving as opposed to dense, cheap RAID boxes.

Companies like Copan Systems and Permabit all have systems that can scale close to 1 PB and both will exceed that number as drive capacities continue to grow. They get there differently. Copan Systems uses densely packed power-managed drives, while Permabit uses grid architecture to offer scale. The point is that they both can scale, offer key redundancy capabilities, and offer functionality that will routinely check the health of the data and drives in the system. They are designed for long-term retention of data. Even with all this scalability, technology will continue to march on. The ability to upgrade these architectures without moving data is going to be critical and is something for you to pay attention to. This is something that cloud storage may seem ideal for and a topic we will address tomorrow. I am participating in a Cloud Storage 101 Webinar this coming Wednesday at 3 p.m. EDT. If you are interested, please click here.

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
Flash Poll
Current Issue
Cartoon
DevOpsí Impact on Application Security
DevOpsí Impact on Application Security
Managing the interdependency between software and infrastructure is a thorny challenge. Often, itís a ďdevelopers are from Mars, systems engineers are from VenusĒ situation.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0607
Published: 2014-07-24
Unrestricted file upload vulnerability in Attachmate Verastream Process Designer (VPD) before R6 SP1 Hotfix 1 allows remote attackers to execute arbitrary code by uploading and launching an executable file.

CVE-2014-1419
Published: 2014-07-24
Race condition in the power policy functions in policy-funcs in acpi-support before 0.142 allows local users to gain privileges via unspecified vectors.

CVE-2014-2360
Published: 2014-07-24
OleumTech WIO DH2 Wireless Gateway and Sensor Wireless I/O Modules allow remote attackers to execute arbitrary code via packets that report a high battery voltage.

CVE-2014-2361
Published: 2014-07-24
OleumTech WIO DH2 Wireless Gateway and Sensor Wireless I/O Modules, when BreeZ is used, do not require authentication for reading the site security key, which allows physically proximate attackers to spoof communication by obtaining this key after use of direct hardware access or manual-setup mode.

CVE-2014-2362
Published: 2014-07-24
OleumTech WIO DH2 Wireless Gateway and Sensor Wireless I/O Modules rely exclusively on a time value for entropy in key generation, which makes it easier for remote attackers to defeat cryptographic protection mechanisms by predicting the time of project creation.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Sara Peters hosts a conversation on Botnets and those who fight them.