Settings and activity
5 results found
-
2 votes
Kevin R. Smith
shared this idea
·
-
45 votes
An error occurred while saving the comment Kevin R. Smith
supported this idea
·
-
5 votesKevin R. Smith
supported this idea
·
-
212 votesKevin R. Smith
supported this idea
·
-
3 votesKevin R. Smith
shared this idea
·
A loud and thunderous vote of support for this idea, @Jason S
As it stands today, the only ways to make a backup of an SBS volume are
1. Create *another* SBS and backup to it.
2. Find another hosting provider and backup remotely to their infrastructure.
The downsides to these are numerous, not the least of which is that it's self-managed and not LW managed.
I don't want to be in the data management business; that's why we pay LW.
Further, if you go offsite with it to another ISP, you're paying transit costs, not to mention when you're going offsite, restoration time, particularly when you're talking about terabytes of data, which we have, is massive, in our case literally days of transit to restore.
And, while multiple support staff have said things along the lines of, "Well, we don't intend for you to use this for production data because of the latency," the LiquidWeb setup page for SBS Volumes says,
"SBS is a distributed, highly available block storage
device that can be attached and detached from any
server dynamically.
"It is provisioned as a raw block device allowing you
the flexibility to use it in any way you require and
create any filesystem that meets your needs."
So, which is it: something to use "any way you require" or "yah... don't use that for real data"?