Today Amazon released their Storage Gateway Service which provides on-premise customers with an i-SCSI interface to the Amazon S3. At initial glance, we went -gulp- there goes the competition, but upon further review, we think that Amazon fell short on going to market with this:
- At least the customers we’ve talked to (Fortune 500, 1000, amongst others) already have significant investment in Snapshot (point in time) capabilities. NetApp, EMC, VMWare, Symantec all compete in this space pretty aggressively. What the market wants is not point in time from Cloud providers, instead, it wants to leverage Cloud as an extend of their in-house Storage capability.
- Even the snapshot approach (where there are point-in-time backups of your data to be offloaded/mirrored to the Amazon S3 service) can be bandwidth and time consuming. Where’s the de-dupe logic? Where’s the efficient caching (Amazon’s offering requires 100% of the storage to reside locally, although they plan on offering gateway-caching in the coming months).
- Vendor locking is a bum – which is what you’ll get here. Easy to get onboard, hard to leave….
- Did anyone look at the footprint of this VM appliance? 4 vCPU, 7.5GB of RAM, and 75GB of storage is pretty hefty price to pay where the compute power is simply handling I/O (again, no intelligence in data de-dupe and intelligent caching, where the magic lies).
- Limit of 1TB per data volume, max of 12 volumes (effective 12TB). Last we checked, this means horizontal scaling limits will prevent penetration into enterprises. As 1TB is nowadays equivalent to 1GB 10 years ago. This also significantly increases your costs.
- Performance – the jury is still out, but based on how it operates we highly doubt it outperforms/out values competitors such as TwinStrata’s CloudArray.
Here’s a nice read from InformationWeek that shares the sames concerns.
Until then, we’ll stick to Veeam and TwinStrata for Offsite Backup and flexibility of storage providers 🙂