Shane

That is odd. Still, if there's no files in D:\ when you look at it in explorer then you should be able to safely Remove the E:\ "disk" from the D:\ pool and thus delete the D:\ pool without affecting the E:\ pool.

I'm out of ideas. Probably need to open that support ticket, sorry. Let us know how it goes?

1. Do you encounter the problem when you copy from a local disk on the pool computer to the pool via the pool's network share (e.g. "\\poolcomputer\poolshare\") instead of via the pool's drive letter (e.g. "P:\")? 2. Is there any difference between copying over the network from another computer to the pool via a mapped network drive (e.g. "P:\") versus the UNC share (e.g. "\\poolcomputer\poolshare\")? 3. On the source/target computers, has there been a network driver update (or any other update) around or shortly before the time this started happening? (check the Windows Update histo

No typo; it makes the offer anyway. I assume it's just a default "there's a duplication problem, here's a thing I can try" response, and if you tell it to go ahead it doesn't succeed since in this case there is no older file. If the content is different, then yes. Correct, DrivePool makes no decisions based on file content. You could request that the developer add that feature (deleting the different file) as an option?

SnapRAID is popular with some users of DrivePool for this reason since the two can be used together. As gtaus mentions, MultiPar is another option. Testing 3x duplication recheck (on 2.3.0.1244 BETA): date modified is different file content is identical -> DrivePool does nothing file content or size is different -> DrivePool alerts the user and offer to delete the older version date modified is identical file size is different -> DrivePool will alert the user and offer to delete the older version file size is i

Not that I'm aware of. A workaround might be to keep a record on the pool of the files that are on each backup drive? 1. backup the files 2. if all goes well, then do something like "dir backupdrive:\ /s /b > pooldrive:\backuplog\backupdriveserial.%date%%time%.log" 3. remove backup drive

Hmm. What happens if you tick Bypass File System Filters under Manage Pool -> Performance? Have you changed or updated your antivirus software, if any? (note: antivirus software may continue to interact at the driver level even when supposedly "off" according to the user interface; you may need to uninstall the antivirus software completely for it to be actually off).

DrivePool's duplication is primarily intended to help with losing a drive; if individual files are being corrupted it may or may not be able to help depending on the situation. In this case where you know the corruption is limited to files on a single drive, if you're using pool-level duplication then the safest thing to do is let DrivePool re-duplicate the pulled drive using the rest of the drives: "Remove" the missing drive and it should proceed to re-duplicate (if not, you can use Cog icon -> Troubleshooting -> Recheck Duplication). Once you've got the pool fully duplicated again

Other registry changes to try (separately or together): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management PagedPoolSize (REG_DWORD, Hexadecimal) to ffffffff (that's eight 'f' characters) DisablePagedPoolHint (REG_DWORD, Decimal) to 1 These changes should be reverted if they don't help. You could also try resetting security permissions on the pool (yes, that sounds weird but yes, it may fix it).

You can wait for it to eventually detect the excess duplication and correct it automatically, or you can use the Troubleshooting menu (from the Cog icon) to manually Recheck Duplication immediately. Either way it should reclaim the free space. Another concern to check however is whether you made any changes to files on the pool between removing the disk and later reconnecting it? If so, you could potentially have issues (e.g. if you removed a drive, deleted a file from the pool that was on that drive, then reconnected the drive, the file would effectively be un-deleted; similarly if you m

Yes, that's correct.

Perhaps you could work around the problem with a third-party copier (e.g. UltraCopier, FastCopy or Copy Handler) or file manager (e.g. Double Commander), as some use their own copying code (to varying degrees) rather than rely on Windows?

You'd need a plugin to accomplish this. You could try a feature request via the contact form?

If it is not already present, try adding PoolUsageMaximum (REG_DWORD, Decimal, 60) to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management in the registry. If it is already present but higher than 60, record its value and try changing it to 60. In both cases a restart will be required.

DrivePool has the dpcmd CLI tool, but I couldn't find any options re indicating missing disks. You could test by copying a file to the pool - if it succeeds, there are no missing disks (since pools become read-only while disks are detected missing). I see another problem however - if it is critical that disks not be missing, and if there is no checking during the sync operation itself, then there is no protection against the risk of a disk going missing during the sync operation? Therefore if a disk going missing means the sync will remove files from the cloud, that indicates yo