aapedrib

I've been a DrivePool user for many years. I downloaded and activated an evaluation license for CloudDrive about 5 days ago. Things were working well until this morning when the activation was lost and I am unable to request another trial license.
 
Any suggestions?

I have a newbie question that I'm failing to find through search. 
 
I have 8 drives in my pool. 2 of which I have low confidence in remaining lifetime. The other 6 I have high confidence in. 
 
Other than setting my redundant folders to "store on " 3 drives instead of 2, is there a way to set the balancer to only store redundant data on my 2 low confidence drives? And not redundant data for each other. IE, use the 2 drives to only store redundant data from the other 6 drives and not from each other?  

when windows starts, i have to manually start cloud drive, why?

Hi Folks (especially Chris),
 
I'm especially frustrated right now because of a dumb mistake on my part and a high likelihood of a misunderstanding of the intricacies of how, when, and why DP is balancing and duplicating to a cloud drive.  My setup is a local pool balanced across 5 hard drives with several folders duplicated x2 comprising ~4.1TB.  The local drivepool is part of a master pool that also contains a cloud drive.  The cloud drive is only allowed to contain duplicated data and currently it is storing about 1TB of duplicates from the local pool.  I only have ~5Mbps upload bandwidth and I just spent the month of October duplicating to this cloud drive.  Yesterday I wanted to remove my local pool from the master pool because I was experiencing slow access to photos for some reason and I was also going to explore a different strategy of just backing up to the cloud drive instead (which allows for versioning).  Well, I accidentally removed my cloud drive from the pool.  At the time, CD still had about 125G to upload, so I assume that was in the write cache because DP was showing optimal balance and duplication.  When the drive was removed of course, those writes were no longer necessary and were removed from CloudDrive's queue.  OK, I didn't panic, but I wanted to make sure that the time I just spent using my last courtesy month of bandwidth over 1TB was not wasted.  So I added the cloud drive back into the master pool, expecting DP to do a scan and reissue the necessary write requests to duplicate the as yet unduplicated 125G.  But lo and behold after balancing/duplication was complete in DP, I look at the CD queue and I see 536G left "to upload"!  All I can say at this point is WTF?  There was very little intervening time between when I removed the cloud drive and re-added it and almost nothing changed in the duplicated directories.
 
Can someone please explain or at least theorize?  I own DrivePool but I've been testing CloudDrive for a while now for this very reason.  I needed to assess its performance and functionality and so far it's been a very mixed bag, partly because it's relatively inscrutable.
 
Thanks,
Marc
 

I currently have Stablebit drive pool ver. 2.2.0.651 64bit. I've been trying to update to ver. 2.2.0.852 x64 but i keep getting a error message about a missing DLL, screen shot and error log included.
 
thank you in advanced

StableBit_DrivePool_(64_bit)_20171102145214.log

Hi, I'm a new user of DrivePool.

I have an external Fantec USB 3.0 hard drive enclosure box, with 4 HGST 4TB drives, all combined in a pool.

I use this pool as long term storage for my photography raw files, so I switch it on only when I need to retrieve an "old" picture or to store a pack of new processed photography sessions.

What I've observed is that every time I switch on the enclosure, the DrivePool process begins to measure the whole pool. It's not a very big pool so it doesn't take more than 10 minutes, but I would like to know id it DrivePool really needs to measure the whole pool each time.

I've tried to switch on the enclosure before the computer to discard the "I haven't found the pool on start", with same results.

My computer is running Windows 10, 1703 compilation and the DrivePool versión is 2.2.0.863 BETA.

Best regards.
--
JGM

I'm doing some shuffling of hard drives between two systems, and want to remove two drives from my main file server. So I clicked "Remove" on the two drives I want to remove from DrivePool, and wait.
 
I noticed that the data from the first disk removed (Disk 3) was balanced between the remaining two in the pool (including the one that was queued for removal). So half the data from Disk 3 was moved to Disk 2, then after Disk 3 was finished the removal process, the "extra" data had to be moved from Disk 2 to Disk 1, along with the original data that was contained on Disk 2. This resulted in ~500 GB being moved twice, and a significant amount of extra time added to the removal process.
 
I did play around with some of the balancing settings, specifically with the Disk Space Equalizer and Drive Usage Limiter (tried unchecking Disk 2 to force files to be placed on Disk 1, but Disk 2 continued to be filled up.
 
I'm not sure if this is an bug, or I just don't know how to use the balancers properly? My pool is fine now, but I'm curious if I were to ever try this again, is there something I can do differently?