the local cache and large data

[duelistjp 6]

i'm looking into using cloud drive to backup a large 40tb drivepool.  i only have 50gb of cache space allocated to the drive.  will backing up to this  cause problems as the cache gets written to faster than it can upload to the cloud.  and if so what do i have to do to make it work.  also when i made the cache crashplan is reporting the cache as being the same size as the cloud drive and windows lists it as huge as well although space on disk is small.  will this cause huge amounts of data to be uploaded to crashplan?  if so does anyone know how to exclude the clouddrive folders from crashplan when other stuff in the same directory as the cache directories needs to be backed up.  i think you can do it with regex but not sure how

[modplan 9]

When you are writing data to the drive, the cache will expand as needed. If you write more than 50GB to the drive faster than you can upload, the cache will continually expand as much as possible until the drive the cache is on is almost full. As data is uploaded, it will be deleted from the cache.

[duelistjp 6]

well it'll be quite a bit more than one drive if i'm using a backup software to backup to it will this cause any problems when the drive is full or will it just slow to practically nothing on the write speed as it waits for data to be uploaded to make room.  just don't want any instability on the system

[modplan 9]

I think it will slow the copy to practically nothing, but I'm not sure if that will cause the backup app or windows to timeout the copy or anything. I've never come close to filling the drive my cache is on.

 

Here is a technical deep dive on the cache architecture: http://community.covecube.com/index.php?/topic/1610-how-the-stablebit-clouddrive-cache-works/

[steffenmand 60]

if needed just use an application like ultracopier or similar to copy to your drive at a slower speed so that you can upload just as fast

[Christopher (Drashna) 631]

modplan has linked the article that you should read about this.

 

But basically, as the drive that the cache resides on gets full, it will start to throttle the write speed to the disk. When you hit 6GBs free on the underlying disk, it will throttle to 10MB/s, and get lower as the space decreases. When you hit 5GB free, any cached data (including disk metadata) is cleared to make room for the upload cache, and it will get drastically slower at this point, as well. .  Once you hit 4GBs free, it will just start to error out and start denying writes.

 

 

If this sounds drastic... well, it basically is, because it otherwise causes BSOD issues.

modplan has linked the article that you should read about this.

 

But basically, as the drive that the cache resides on gets full, it will start to throttle the write speed to the disk. When you hit 6GBs free on the underlying disk, it will throttle to 10MB/s, and get lower as the space decreases. When you hit 5GB free, any cached data (including disk metadata) is cleared to make room for the upload cache, and it will get drastically slower at this point, as well. .  Once you hit 4GBs free, it will just start to error out and start denying writes.

 

 

If this sounds drastic... well, it basically is, because it otherwise causes BSOD issues.

[duelistjp 6]

thanks that was what i was thinking would happen