When adding more than one networked drive to a Drive Bender pool and you are using duplication, the user needs to ensure the underlying hard drive is unique for each networked pooled drive.
Normally Drive Bender uses the drive number assigned by Windows to determine the placement of duplicated files. For example if you have hard disk 1, which contains 2 partitions, A and B and both A and B partitions are added to a pool, Drive Bender is aware that it cannot treat both A and B partition as separate drives, and will duplicate accordingly.
However with networked drives, Drive Bender cannot determine the underlying hard disk, so it treats each networked drive as a separate drive. So for example you have mapped "\\MyServer\Mapped1" to Disk 1, and then mapped "\\MyServer\Mapped2" to Disk 2, the failure of either underlying drive (Disk 1 or Disk 2) will not impact file recovery. However if you also mapped "\\MyServer\Mapped2" to Disk 1, and Disk 1 fails, you will not have 100% file redundancy, and you may not be able to recover all files.
If you do not understand this concept, we recommend that you do not use networked drives on a pool that employs duplication.