|
|
|
|
|
by kbenson
4115 days ago
|
|
How about an add-on cost/service that tags your data as needing datacenter redundancy, and only replicating that to a new datacenter. It has the benefit of not requiring as much up-front investment, as it's used it pays for itself, and you have a bunch of current customers you can upsell to. The architecture to segregate redundant from non-redundant backup customers could be a pain, but as long as you have tools to migrate data between systems (I imagine you do), then it could just be running two separate backblaze clusters in the first datacenter, one which supports redundancy and one which doesn't, and then just migrate customer data between the clusters as the add/drop the redundancy service. That saves you from having to cherry-pick specific files/customers from the the cluster to duplicate in the other datacenter, you just make sure one cluster is always redundant. |
|