Cloud
10/22/2010
03:00 PM
George Crump
George Crump
Commentary
Connect Directly
RSS
E-Mail
50%
50%

How To Get Data To The Cloud: Onramps

As we discussed in our last entry, deciding when to use cloud storage is an important decision that data center mangers are now trying to make. While adding the capabilities to your own software was an early approach most were waiting for an easier way to get to the cloud and it comes in the form of software that allows near seamless access. We call these onramps.

As we discussed in our last entry, deciding when to use cloud storage is an important decision that data center mangers are now trying to make. While adding the capabilities to your own software was an early approach most were waiting for an easier way to get to the cloud and it comes in the form of software that allows near seamless access. We call these onramps.The onramp software do the same basic core functions, translating the storage protocols that you are accustomed to today and converting them to the storage models that the cloud providers are using. Almost all of the onramps use a hybrid model that leverages a local storage capability and then as bandwidth is available copies that data to the cloud. The onramps typically come in two forms today, either a specific piece of hardware that is provided to you or as a software application that you load onto a server or into a virtual infrastructure.

On premise part of the cloud implementation typically acts as a cache. When data is accessed, written or modified it is stored in the cache for faster access. The data is in most cases copied as soon as possible to the cloud for redundancy. Then like any other type of cache as that data ages and becomes unused it is moved solely to the cloud. This allows for the local cache to be relatively small.

The most common use case of these devices or software extensions is as a part of a backup or archive applications where data is written to a local device quickly so the backup job can complete and then replicate through the cloud as bandwidth allows. This provides an automatic off-site vaulting capability that many users need. Most leverage deduplication and compression to optimize bandwidth, the only downside is the initial seeding of the cloud storage target. Providers and backup software developers have worked around this by shuttling an initial seeding unit to build the baseline by which data optimization can work against.

Onramps are not just limited to backup or archive data. Primary storage onramps to the cloud are now available for a variety of primary storage situations including both NAS and SAN. In cloud enabled NAS product, data is typically moved at the file level in and out of the cache. The SAN type of implementations have to take a finer level of granularity and need to move data at a sub-file level, typically a block. They also tend to have much larger cache capacities than the file serving versions but in general tend to respond to demands very quickly, even within databases. In both NAS and SAN there is not an initial seeding option, so these implementations are ideal for new projects or where data can be slowly populated to the device.

Most users are going to dip their toes in first with cloud storage and onramps allow that to happen with relative ease. For example they can be a device that backups are sent to first, then a storage area for blob oriented databases like Sharepoint or Exchange. From there as confidence builds they can move into the role of providing more traditional primary storage services.

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

Subscribe to our RSS feed.

George Crump is lead analyst of Storage Switzerland, an IT analyst firm focused on the storage and virtualization segments. Find Storage Switzerland's disclosure statement here.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
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.