I want to implement the 3,2,1 rule (3 copies, 2 local, one remote/cloud) using DrivePool and CloudDrive. For important files, I would like 2 copies of files stored locally (spanned at least two disks, which I'm already doing) with a third copy stored in the cloud via a CloudDrive disk added to the pool. How can I use the balancers to enforce that a (third) copy is always made specifically to the CloudDrive disk, and not just spanned to a random third disk in the local pool?
Beyond that, for less important data where a single local copy is made, how can I enforce that a (second) copy is always made specifically to the CloudDrive disk, and not just spanned to a random second disk in the local pool?
Might be a nice optimizer option to add to enhance tiered storage, like the SSD optimizer. Maybe SSD, HDD, Archive, Cloud, etc.
Question
collapsed
My apologies if this has been discussed before...
7 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.