nwtim

I didn't realize there was a 'file placement limiter balancer' when I started, or that's the route I would've taken from the get-go. I wasn't removing a bad disk, just one that runs at 7200 RPM which is not as favorable in a home server environment. I'll have to look at the log and see if it'll help identify any files that may have gotten lost in the removal. Thanks!

So you don't think it's because I set up folder duplication manually via the dp-cmd SetDuplicationCount command? I was curious if that might've caused a problem because Drive Scanner and Home Server SMART 2013 showed no errors on the drive. I wouldn't think that having PerfectDisk WHS installed could've been running a background process that was causing a problem, but perhaps it is?

I'm hoping to replace a 7200 RPM 2TB drive with a slower WD Red 2TB drive in my WHS. Last night I added a new WD Red 2TB drive to the pool and then began the process of moving all the files off the 7200 RPM 2TB drive by removing it from the pool. For the first 90 minutes or so, everything seemed to be going according to plan and the 'migrating data' progress bar had moved to about the 40% percent point. I began to wonder about the temperature of the drives due to the high rate of reading and writing and the factor that all four drive slots were populated in my Lenovo D400's packed drive bay. On the dashboard, I clicked on the Home Server SMART 2013 tab to check the temps. At that point, the migration of the drive removal aborted and I was informed about some kind of access denied error. Further attempts at removing the drive have repeatedly failed, reporting the same access denied error. Any idea what may have happened and how I can get out of that loop to resume removing the drive? Thanks!

That sounds great! How soon will 2.0 be available for WHS2011? My update last night only brought it up to 1.3.7558 RC.

Okay, I found the way to use dp-cmd with the command SetDuplicationCount and wrote a batch file to set the count to 2 for five different folders under the parent "shares" folder. I did get feedback for each setting that the count was set to 2 successfully, but is there an easy way to confirm which folders are being duplicated at any time in the future? Or do I have to check the PoolPart folders of each HDD manually?

Well, I'm using WHS2011 and I'm still running DP 1.3.7553, so I guess I'll have to update it to get the functionality you have. Did you set up the duplication via the Dashboard or navigate to the folders with a command window or Windows Explorer?

Well, let me ask this at least: To use the SetDuplicationCount command, do I just type it in a command window and follow the directions? Or do I navigate (in a command window) to any folder I wish to apply it to and 'run' it from there?

About a week ago I had a 2TB HDD decide to never spin up again and lost a fair amount of data. The data loss was primarily because I didn't have the time to set up duplication of the most critical folders and I had no done a complete backup in over a month. The problem is that I have a relatively large number of video files that I don't really have space to efficiently back up, yet the folders containing these files are under shares that also contain folders for our photos and numerous other documents that we want to duplicate. I've done this to minimize the number of drives that need to be mapped to easily access these folders from client PC's that already have a significant number of mapped drives (on my personal PC, I really only have one drive letter available to map!). I've come close to writing a robocopy batch file for the most important folders to run through the Windows Scheduler, but I don't think this would ensure that duplicate files get placed on separate physical drives, so I've been hoping for something a little more "built-in" like was available with Lenovo's flavor of WHSv1. I understand there's something in the Drivepool Command Utility called SetDuplicationCount, but I haven't seen any instructions for the proper syntax to use with it. Any advice would be greatly appreciated. Thanks!