So, i can not make that DrivePool relocating feature save some data on a drive that is not part of the pool?
this drive pool virtual drive (or how to call the drive that is result of DrivePool pool) would not be a system drive, it is rather data drive for videos, images and a few apps (not Program Files) (one is using files with .db extension). So i do not think it shoudl cause some conflict, unless DrivePool does not have this feature to save some data outside of the pooled drives or fails to properly create hardlink(?) from original location to new one? Or you mean to say that DrivePool's relocating feature would places all .db files no matter in which directory they were located into one common directory without using subdirectories?
Yes, this seem to be good option, but currently my system drive is fully encrypted using Truecrypt and main bootable partition can not be shrinked from within Windows Drive manager. So i guess option is to create encrypted VeraCrypt/TrueCrypt container (file) on my system drive and mount this file using VeraCrypt/Truecrypt as a new drive.
if i understand right, i think i can not do this, because that SW which is making .db files is maintaining some structure and i can not tell it not to do it, as i am not a programmer:
data/folder1/subfolder/randomfilename.db
data/folder2/subfolder/randomfilename.db
..
(all folder and file names except "data" are randomly created and i can not guess its name)
.db files is like maybe 100-5000 and total its size is maybe 30 GB atm, though can be growing.
Moreover that software is using very large amount of data not fitting todays SSD's capacity, though .db files are of relatively small size as mentioned.