S4 - $12 for 1 year of 1 TB write-only storage
supersimplestorageservice.com
supersimplestorageservice.com
<!-- Ahh... I see you're a distingushing Internet user. You're really a "check under the hood" -->
<!-- type of guy. I like that about you. I also like how you really told off that bully-->
<!--at the Christmas party... you're such a stud. And have you lost weight? You're looking great.-->
and at the bottom: <!-- You looked all the way down here?! Let's hump. -->
Classic."Please contact us with any questions by e-mailing us at the address below. All complaints and feature requests will be immediately stored using our S4-backed user request database."
Q: I can't read my data!
A: Good!Q: Do you use any file compression on the storage servers?
A: Yes, we use unix compression program: rm -rf
$ pv /dev/zero > /dev/null
18.6GB 0:00:05 [3.76GB/s] [ <=> ]Wow. What kind of hardware is your /dev/null ? Do you use striping ?
Until there's an enterprise-level solution for /dev/null, I think I'm going to have to stick with S4.
I wonder if there's a real business model there. Most of us restore an extremely small percentage of what we backup. Could you offer a cheaper storage cost than other businesses and make up the difference on the small number of restores that occur?
If you're really that desperate for cheap backups, you'd actually be best off storing terabyte hard drives / SAN boxes around the country, maybe in colo'd buildings.
If you can get the entire operation costing less, then it's fine if restores take longer and cost more... because you pass that fee on to the customer. I for one would be happy to pay less for writes and more for reads, since I read backups far less than I write them.
And it's not about being desperate for savings. It's about reducing the overall cost of a commodity... storage.
I wonder if simply using the backblaze type setup with 'green' drives that are set to 'power down' when not in use would be the best solution? In that case, you'd want to minimize writes as much as reads, but it would make some sense to offer a discount for data that 'just sits there'
On the other hand, I bet that when you buy power 'at scale' you can get your watt-month prices quite a bit below $0.27 (note, you must roll in the cost of both the watt your equipment uses /and/ the watts the a/c system uses to deal with the watt of heat. At the low end, the provider bundles those two, but if you build your own data centre, you need to be careful to build that into your cost assumptions.)
The other problem with doing this at the low end is that where I am, I pay full price for a circuit, no matter how much power I pull off it (the circuit just blows if I get too carried away) and even places that do rent you metered power usually have high costs for rackspace that are not metered, so really, you are only potentially saving two or three bucks a month per disk, even if they were idle all month.
Now, also, 'green' disks are usually really slow. 5900rpm rather than 7200rpm. But they are also really cheap, so if your customers want to accept slow, you can save quite a lot on your CapEx. Like probably half, if you use consumer-grade 'green' drives rather than the 'enterprise sata' I use. Using consumer grade drives has a bunch of other problems that your software will need to account for, too... but that's a place where you potentially could have pretty big savings.
That fell under "storage and redundancy".
Storage = the hardware and electricity required to store/minimally serve the data
redundancy = number of places the data is stored
thusly
cost = storage cost * redundancy
I really hate having to verbosely explain things like this. Is it even remotely possible for you to give me the benefit of the doubt and not assume I'm a blithering moron when I don't expound ad nauseam every little detail of what I'm describing?
Hilarious. I know lots of companies that must use this service.
"We are pleased to introduce a new storage option for Amazon S3 called Reduced Redundancy Storage (RRS) that enables customers to reduce their costs by storing non-critical, reproducible data at lower levels of redundancy than the standard storage of Amazon S3."
http://aws.amazon.com/about-aws/whats-new/2010/05/19/announc...
Well, let's say that as long as we're talking about files and there is enough local free space I might be able to do that.
But once committed that's it, no rollback past that point.
Or I'd have to charge significantly more.
We'll take this on a case-by-case basis.
I could store those in S4, free up some space and re-use it for other files.
Still working on the restore side of things, but that can't be too difficult, can it?
bignum i;
for (i=0;i<MAXBIGNUM;i++) {
if (hash(i) == filehash) {
break;
}
}
fprintf("%Bd",i);It was more of a pseudo code joke.
If you weren't serious, congratulations ;)
Sounds feasible, if you have enough strange matter lying around.