Earlier quoted context omitted.
the volumes are cached... from reading the post, you write synchronously to the iSCSI device, which is Asynchronously sent to S3
I'm not sure if that's what kondro meant but what I would like to see is a virtually unlimited size ("elastic") volume where the local disk acts only as the cache. This would make a wide range of big-storage use-cases ridiculously trivial - those where only ~10% of the data-set is frequently accessed. I.e. one could lazily scale the expensive local storage with throughput-demand, while the S3 backing store takes care…
AWS Storage Gateway
21–30 of 34 posts
Re: AWS Storage Gateway
#22Re: AWS Storage Gateway
#23So you are basically paying 125$+ to have S3 cached locally and get an iSCSI interface ?
Re: AWS Storage Gateway
#24Earlier quoted context omitted.
Note that the mirroring is asynchronous -- if your local server fails you can replace it with an EC2 instance, but you lose anything since the last snapshot.
Not since the last snapshot. It syncs as close to real-time as possible without the latency and network speeds affecting the performance locally. This solution isn't designed to replace fault-tolerance on local hardware. It is for close to realtime offsite replication and backup. Data in S3 is stored in at least three geographically separate locations and snapshots are very fast and very efficient on storage space. T…
In contrast, storing 50TB for 5 years on S3's reduced redundancy storage would cost $250,000. If I ever need to transfer any of that data back to my data center, there'll be a hefty bill for that as well.
Re: AWS Storage Gateway
#25Not only that, it solves a lot of problems such as dangerously storing backup snapshots on-site, archival and easy deployment and access to S3's CDN functionality.
Sold as far as I am concerned!
(Yes I know it's expensive, but it's cheaper than buying something in-house and employing another hairless monkey to manage it).
Re: AWS Storage Gateway
#26Earlier quoted context omitted.
the volumes are cached... from reading the post, you write synchronously to the iSCSI device, which is Asynchronously sent to S3
I'm not sure if that's what kondro meant but what I would like to see is a virtually unlimited size ("elastic") volume where the local disk acts only as the cache. This would make a wide range of big-storage use-cases ridiculously trivial - those where only ~10% of the data-set is frequently accessed. I.e. one could lazily scale the expensive local storage with throughput-demand, while the S3 backing store takes care…
Implementing a tiered storage system yourself is pretty complex. Using this S3 gateway might be simpler, but it's not trivial (e.g. you'll need VMware ESXi just to get started).
Re: AWS Storage Gateway
#27Earlier quoted context omitted.
Not since the last snapshot. It syncs as close to real-time as possible without the latency and network speeds affecting the performance locally. This solution isn't designed to replace fault-tolerance on local hardware. It is for close to realtime offsite replication and backup. Data in S3 is stored in at least three geographically separate locations and snapshots are very fast and very efficient on storage space. T…
Let's say I need 50TB of usable space. I can purchase an Equallogic PS6100E (a mid-level "enterprise" storage device) with twenty-four 3TB drives and 5 years of support for $85,000. Rack space and power isn't free, so let's say the total cost of equipment and facilities over 5 years is $100,000. In contrast, storing 50TB for 5 years on S3's reduced redundancy storage would cost $250,000. If I ever need to transfer an…
Re: AWS Storage Gateway
#28More details at Werner's post http://www.allthingsdistributed.com/2012/01/The-AWS-Storage-...
http://aws.typepad.com/aws/2012/01/the-aws-storage-gateway-i...
Re: AWS Storage Gateway
#29Earlier quoted context omitted.
I'm not sure if that's what kondro meant but what I would like to see is a virtually unlimited size ("elastic") volume where the local disk acts only as the cache. This would make a wide range of big-storage use-cases ridiculously trivial - those where only ~10% of the data-set is frequently accessed. I.e. one could lazily scale the expensive local storage with throughput-demand, while the S3 backing store takes care…
Let's say you expect to grow to 20TB of data. Storing that for one month on S3 costs $2,560 (standard) or $1700 (reduced redundancy). In contrast, a Dell R515 with twelve 2TB drives costs $7,000. In a year that's one-third to one-quarter the price of using S3. Implementing a tiered storage system yourself is pretty complex. Using this S3 gateway might be simpler, but it's not trivial (e.g. you'll need VMware ESXi jus…
I.e. instead of VMware it'd be more useful for us to hook in with a FUSE-layer or a patched variant of a filesystem such as GlusterFS.
You're of course correct about the pricing. Their current prices cover some middle-ground but would need to be discounted to make it feasible for larger deployments. However, at the low-end (your 20T figure) the price seems already justifiable when you factor in staff and infrastructure costs (rack+power alone make up for half of the difference).
Re: AWS Storage Gateway
#30Earlier quoted context omitted.
Let's say I need 50TB of usable space. I can purchase an Equallogic PS6100E (a mid-level "enterprise" storage device) with twenty-four 3TB drives and 5 years of support for $85,000. Rack space and power isn't free, so let's say the total cost of equipment and facilities over 5 years is $100,000. In contrast, storing 50TB for 5 years on S3's reduced redundancy storage would cost $250,000. If I ever need to transfer an…
With Amazon you could facilitate a DR onto their other platforms. With your Equallogic example you would need to mirror that data to another device with recovery targets in another location.