Created a local CloudDrive pointing to Amazon S3. I chose full encryption. The volume/bucket created successfully on S3 as well as the formatting and drive assignment for my local drive. I could see the METADATA GUID, and a few chunk files were created from the process on the S3 bucket.
Next, I upload one file and noticed that additional "chunk" files were created in the bucket. After the Stablebit GUI status indicated that all file transfers were completed, I deleted the file from my local CloudDrive. After awhile, I refreshed the S3 bucket and saw that all the chunks were still there...including the new ones that were created when I transferred the file.
Here's my newb questions:
1. Am I correct in stating that when I delete a local file which is on my local Stablebit CloudDrive pointing to Amazon S3, it should remove the applicable "chunks" from Amazon S3?
2. How can I be sure that when I delete a large file from my local CloudDrive, the applicable S3 storage bucket size reduces accordingly?
3. Am I off base to think that the two file systems should stay in sync? During my tests, and after waiting quite some time, the S3 bucket never decreased in size even though I deleted the large file(s). Which means Amazon boosts their bottom line at my expense.
Thanks, and I searched for this but could not find any discussion on point.
Question
mbCcuStl3bt
Hello,
System:
Windows 10
intel i4770
CloudDrive version: 1.0.0.417 BETA 64bit
Background/Issue
Created a local CloudDrive pointing to Amazon S3. I chose full encryption. The volume/bucket created successfully on S3 as well as the formatting and drive assignment for my local drive. I could see the METADATA GUID, and a few chunk files were created from the process on the S3 bucket.
Next, I upload one file and noticed that additional "chunk" files were created in the bucket. After the Stablebit GUI status indicated that all file transfers were completed, I deleted the file from my local CloudDrive. After awhile, I refreshed the S3 bucket and saw that all the chunks were still there...including the new ones that were created when I transferred the file.
Here's my newb questions:
1. Am I correct in stating that when I delete a local file which is on my local Stablebit CloudDrive pointing to Amazon S3, it should remove the applicable "chunks" from Amazon S3?
2. How can I be sure that when I delete a large file from my local CloudDrive, the applicable S3 storage bucket size reduces accordingly?
3. Am I off base to think that the two file systems should stay in sync? During my tests, and after waiting quite some time, the S3 bucket never decreased in size even though I deleted the large file(s). Which means Amazon boosts their bottom line at my expense.
Thanks, and I searched for this but could not find any discussion on point.
Link to comment
Share on other sites
4 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.