1st of all, thanks for this great program & the amount of customer support it has.
I have learnt a lot about these programs (scanner & drivepool) from reading many forum posts but unfortunately with 7 days left on my trial I am unable to find an answer to this & can't seem to solve it myself.
Anyway, short story long...
I have set some file placement rules to move small regularly accessed files to the pooled C: drive since it does not spin down.
I decided to use the SSD Optimizer on a HDD (C:) to stop multiple small writes throughout the day on drives that have spun down & instead rebalance at night. But before I installed the plugin I read that it will evacuate the drive chosen as SSD unless I disable the "unless the drive is being emptied" option, but I'm concerned that if I disable that option then if Scanner detects a failing drive it won't be able to evacuate the drive to other drives (I have specific drives assigned to specific folders). So instead I repartitioned the C: drive to make an extra 50GB partition to set as the Cache, but when I tested it, it just wrote directly to one of the other HDDs (one that was not assigned to the location that I placed the test file in!?). After several attempts at trying to figure out what I was doing wrong I disabled the SSD balancer & assigned a rule to place files in a specific cache folder onto the 50GB cache partition, but when I dropped a file into that folder it just saved it to an incorrect disk again even though I checked the option to "never allow files to be placed on any other disks"!
For the record, the 50GB cache is a logical partition, I currently have no duplicated files & real-time duplication is disabled. Also the incorrect drive that is being written to is only assigned to a "backups" folder, so shouldn't be getting any other files. If anything, the file should have gone to my "other" drive as it has a placement rule of "*" at the bottom of the placement rules.
Thanks for taking the time to read my lengthy post.
Sorry that I didn't simplify it, I just wanted you to get the full story so we can hopefully get to the bottom of this.
Thanks,
Scott
I have learnt a lot about these programs (scanner & drivepool) from reading many forum posts but unfortunately with 7 days left on my trial I am unable to find an answer to this & can't seem to solve it myself.
Anyway, short story long...
I have set some file placement rules to move small regularly accessed files to the pooled C: drive since it does not spin down.
I decided to use the SSD Optimizer on a HDD (C:) to stop multiple small writes throughout the day on drives that have spun down & instead rebalance at night. But before I installed the plugin I read that it will evacuate the drive chosen as SSD unless I disable the "unless the drive is being emptied" option, but I'm concerned that if I disable that option then if Scanner detects a failing drive it won't be able to evacuate the drive to other drives (I have specific drives assigned to specific folders). So instead I repartitioned the C: drive to make an extra 50GB partition to set as the Cache, but when I tested it, it just wrote directly to one of the other HDDs (one that was not assigned to the location that I placed the test file in!?). After several attempts at trying to figure out what I was doing wrong I disabled the SSD balancer & assigned a rule to place files in a specific cache folder onto the 50GB cache partition, but when I dropped a file into that folder it just saved it to an incorrect disk again even though I checked the option to "never allow files to be placed on any other disks"!
For the record, the 50GB cache is a logical partition, I currently have no duplicated files & real-time duplication is disabled. Also the incorrect drive that is being written to is only assigned to a "backups" folder, so shouldn't be getting any other files. If anything, the file should have gone to my "other" drive as it has a placement rule of "*" at the bottom of the placement rules.
Thanks for taking the time to read my lengthy post.
Sorry that I didn't simplify it, I just wanted you to get the full story so we can hopefully get to the bottom of this.
Thanks,
Scott