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

Cloud Storage Migrations

Finishing up the migration series, let's talk about how you would migrate out of a storage cloud. With public storage clouds in particular, this can be a critical issue. These services are all in their infancy. What if you pick the wrong one, how can you get your data back?

Finishing up the migration series, let's talk about how you would migrate out of a storage cloud. With public storage clouds in particular, this can be a critical issue. These services are all in their infancy. What if you pick the wrong one, how can you get your data back?Initially, migration isn't going to be a big ordeal because most early adopters of cloud storage are using the services as an area to store backups and archives, but as the comfort level of the services increases, so will the data sets. As those data sets increase, so will the importance of an exit strategy. Similar to migration issues with internal disk-based archive solutions, migration from a public cloud is going to be a challenge that is compounded by the fact that the Internet is between you and your data.

If the cloud supplier isn't using its own proprietary technology, migration could be made to another service using the same technology. For example, the cloud service provider could use a standard archive-based solution as its storage back end from one of the standard archive storage providers like Copan Systems, Permabit, or EMC, all of which have replication capabilities. You simply (assuming you negotiated this upfront) could replicate your data from one provider to another. Similar to online backup service providers that use tools like Asigra, moving to another provider is pretty straightforward.

If the public cloud supplier is using cloud storage and/or cloud storage software like those solutions from Cleversafe or ParaScale, again the ability to move data to another provider should exist -- just confirm that this capability is on the road map and that you are comfortable with the time frames.

Private storage clouds are essentially public storage clouds on your internal intranet, but because they are internal they follow much the same migration rules that we wrote about in our previous entry on disk archive migration. The challenge is that I expect a private cloud to grow in capacity much more rapidly than a public cloud. There is a higher comfort level, it is behind your firewall and access should be somewhat faster. With either a disk-based archive or a private cloud, selection is critical because as the capacity of the archive grows, migration becomes more and more challenging. With either technology look for scalability, cost efficiency, and reliability.

For more on cloud storage, sign up for our Webcast this afternoon Cloud Storage 101.

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.