I'm evaluating CloudDrive (already using DrivePool and very happy with it).
My intention is to use CloudDrive for offsite backup, through a daily Robocopy job. So, CloudDrive would (for the most part) be "write-only".
I need to decide on a storage provider. I'm currently inclined to use Google Cloud Storage, as I'm familiar with it, but to make some sense of the costs involved, I'd need to better understand how CloudDrive uses GCS. I mean, is there a situation where it makes sense to use GCS near/coldline, perhaps through lifecycle management?
This will largely depend on how metadata is stored and what kinds of GCS operations would be used by CloudDrive when Robocopy lists a directory to figure out file sizes and modification times, and how often are blocks that are neither read nor written to accessed.
Does this make sense? Is there any way I can debug this for myself?
Question
Nuno
Hi,
I'm evaluating CloudDrive (already using DrivePool and very happy with it).
My intention is to use CloudDrive for offsite backup, through a daily Robocopy job. So, CloudDrive would (for the most part) be "write-only".
I need to decide on a storage provider. I'm currently inclined to use Google Cloud Storage, as I'm familiar with it, but to make some sense of the costs involved, I'd need to better understand how CloudDrive uses GCS. I mean, is there a situation where it makes sense to use GCS near/coldline, perhaps through lifecycle management?
This will largely depend on how metadata is stored and what kinds of GCS operations would be used by CloudDrive when Robocopy lists a directory to figure out file sizes and modification times, and how often are blocks that are neither read nor written to accessed.
Does this make sense? Is there any way I can debug this for myself?
Thanks!
3 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.