zeroibis

Ok solution is that you need to manually create the virtual drive in powershell after making the pool:
1)      Create a storage pool in the GUI but hit cancel when it asks to create a storage space

2)      Rename the pool to something to identify this raid set.

3)      Run the following command in PowerShell (run with admin power) editing as needed:
New-VirtualDisk -FriendlyName VirtualDriveName -StoragePoolFriendlyName NameOfPoolToUse -NumberOfColumns 2 -ResiliencySettingName simple -UseMaximumSize

Yea the goal is to not need to pull a 20TB recovery when you could have just done a 10TB recovery it would literally take twice as long. Also you have a higher probability of failure.
 
In my case:
A+B = Duplication Pool 1
C+D = Duplication Pool 2
E+F = Duplication Pool 3
Duplication Pool 1+2+3 = Pool of Pools
In the above example you can sustain more than 2 drive failures before you lose data depending on what drives fail. In the event of a failure where data loss occurred you will need to restore 1 drives worth of data.
Next example:
A+B+C+D+E+F = One large pool with 2x duplication.
In the above case you will have data loss whenever 2 drives die; however, you will need to pull two drives worth of data from your backups in order to restore. Even if you skip files that you did not lose you still need to actually generate the remote pull action to get the data to then restore from your remote backup server/service.
Next example:
A+B = Pool 1
C+D = Pool 2
E+F = Pool 3
G+H = Pool 4
Pool 1+2+3+4 = Pool of Pools with duplication applied here. Once again like above if any 2 drives die you will need to restore data and the restore operation will be at least the size of two drives.
 
The other issue is how you are presenting data for backup. If you are just backing up your entire large pool then in order to run a restore operation you need to pull the entire backup because you do not know what files you lost. By having your data sorted in such a way as that you know exactly what backup goes to what drive set you can reduce the scale of the restore operation.
 
For those trying to use this at home things like this may not really matter for for business usage the way that your structuring your backups and your time to restore are major factors in how your going to deploy.
 
Anyway none of this really matters to the actual issue at hand here which appears to be a bug in the software. From what I can tell the software is unable to correctly balance a pool of pools when the underline pools have file duplication enabled on them. Given that the ability to pool pools together is a key feature of Drive Pool along with the ability to then balance data across these pools this is a bug. As stated in my previous post a simple fix would be to recode the balance operation to check after no more than 50% completion if balance is still needed. Until then the only work around is to disable automatic drive balancing and only run the operation manually and then stop it at exactly 50% and your good. From there you should not need to run it if you have file placement balance turned on.
 
 

I think I found where my issue was occurring, I am being bottle necked by the windows OS cache because I am running the OS off a SATA SSD. I need to move that over to part of the 970 EVO. I am going to attempt that OS reinstall move later and test again.
Now the problem makes a lot more sense and is why the speeds looked great in benchmarks but did not manifest in real world file transfers.

I think I found where my issue was occurring, I am being bottle necked by the windows OS cache because I am running the OS off a SATA SSD. I need to move that over to part of the 970 EVO. I am going to attempt that OS reinstall move later and test again.
Now the problem makes a lot more sense and is why the speeds looked great in benchmarks but did not manifest in real world file transfers.

Ok solution is that you need to manually create the virtual drive in powershell after making the pool:
1)      Create a storage pool in the GUI but hit cancel when it asks to create a storage space

2)      Rename the pool to something to identify this raid set.

3)      Run the following command in PowerShell (run with admin power) editing as needed:
New-VirtualDisk -FriendlyName VirtualDriveName -StoragePoolFriendlyName NameOfPoolToUse -NumberOfColumns 2 -ResiliencySettingName simple -UseMaximumSize