580guy

Thanks for all the help, Chris. I tried out the Beta of 2.x for a week or so, and guess what? I ended up going back to 1.x. Even with the possibility of the inaccessible folder problem showing up occasionally again. My reasons are: 1. Better performance. With 2.x, I noticed at times activity on the pool would just stop for 5-10 seconds, even though I was running stuff like WinRar extraction while I was watching pool activity, it would just pause then finally resume. Never have that happen with 1.x. 2. Purely Manual Folder Duplication I need this. I run a drive defragger t

Thanks Chris. I will try the 2.x Beta. The inaccessible folder problem cropped up again even with drivepool 2.x stable last night again. I am wondering if it has something to do with the number of drives in my pool (21) and the wacky windows permissions (WHS 2011). May have to upgrade server to 2012 Essentials down to road. Need more memory and already up to 8GB (max for WHS 2011). Never had this problem until the last few months. Still I believe I like drivepool 2.x version better than 1.x. It's nice to be able to run the interface without waiting to load the Dashboard to access/ch

I run WHS 2011 and have been running Drivepool 1.x for some years. Lately I have had some folder permission problems with folder moves between shares, and the folder that is "moved" is left empty on it's share and I cannot access the folder without a server reboot. Cannot take ownership, etc. even with Administrator account. Anyhow, after much troubleshooting I decided to try Drivepool 2.x and so far so good. Still not sure where the system was glitching, maybe a large pool of 21 drives? But.... I always preferred to run manual duplication on Drivepool 1.x, and also without background

I know my post above is from a couple of years ago, but just wanted to confirm that it DOES INDEED work if there are any out there using this combination. I had my first drive failure in my server of 21 drives. I know I have been extremely lucky as I have drives that have over 6 1/2 years of 24/7 operation and are still going strong. Anyhow.... The drive that failed, didn't fail completely. I had been receiving warnings from Stablebit Scanner about remapping sectors for the last several months. I decided to wait and see how long the drive would go before it failed completely. This driv

Thanks, Drashna. Actually, what I found there was my shares weren't selected to be indexed. Now all is fine. Thank you again for pointing the way!

I migrated my pool to my new Lenovo TS440 Server from an HP MediaSmart Ex495. Everything went smoothly with no problems. Transferred my license for Drivepool and the pool was recognized right off the bat and has been running great for 3 weeks now. But, as shown on my screenshot of the WHS2011 Dashboard, my folder sizes are ZERO except for Client Computer backups. I have re-measured, re-indexed to my heart's content, but nothing seems to fix this. I have no other problems at all, running fine, but I always enjoyed having these Stats available. What else can I do to get this to work?

Here is what I did to run FlexRaid Snapshot parity along with Stablebit Drivepool to help with drive replacements in your pool. When you replace a drive in your drivepool, a new PoolPart.xxxx folder is created automatically by Drivepool. FlexRaid's Data config is pointing to the "old" Poolpart.xxxx folder of the removed drive. While FlexRAID can restore the files to the new drive, they will be restored to the "old" PoolPart.xxxx folder, and it's parity will not be current. You can move the files to the new PoolPart.xxx folder, but FlexRaid is still looking at the old one when updating

Thanks, Drashna for your reply. However, nothing much worked. If I rename the PoolPart.xxxx folder, the drive goes into a second pool. Tried this many times, and always the same. So, decided to re-create my FlexRaid snapshot array, but this time I am setting up some hard links on C drive, pointing to the PoolPart.xxxx folders on each drive in the pool, with the MKLINK command from a Dos shell. That way I can always change my link if a drive is upgraded/replaced (new PoolPart.xxx folder created) and leave FlexRaid config the same, as it just uses the link named DRU1 etc which points to

Well, drive arrived Saturday. So, tried this method, and it worked, sort of. I manually created the PoolPart.xxxx folder with the Drivepool service stopped. I restarted the service, but the drive was not added to the pool. I was only running this one drive, and had all my other disks off. Again, running WHS2011, so this is the System drive C, with another partition (D). I rebooted, and the drive (D) was added to a pool! I noticed the Drive letter of the pool was G, instead of Z (as I like to use). I changed it to Z thru Disk Management. I then shut down, turned on my other 10 drives, a

I am running a WHS2011 server using Stablebit Drivepool 1.3 and Flexraid snapshot parity for unduplicated shares. I want to upgrade/replace an existing drive. This is how I would like to do it. 1. Stop Drivepool service, remove drive. 2. Install new hard drive 3. Manually create Folder: PoolPart.7ff9720d-58fa-4081-9ebc-70ae65a7a336 and make hidden 4. Restart Drivepool service. 5. If added to pool, wait for duplicate file re-build 6. copy back shares from old drive to new drive My Question is, will this new drive be added into the pool? After some research, I read this olde

Thanks so much for your reply. Just what I needed to know. I may try the "File Placement Limiter" to move the data off the drive first, and simplify the removal from the pool. Thanks again.

I haven't been able to ascertain this while searching throught the forums and blogs. While removing a drive from the pool, is the pool still useable through the remaining drives? In other words, is my server unuseable until Drivepool finishes removing the drive from the pool? As this could take a day or so to perform, I am trying to figure out if I will still have PC Backup, FTP, Media streaming, etc available during this time. Is Drivepool smart enough to allow you to still use the remaining drives in the pool while removing a single drive from the pool? This will help me plan a littl