Disable L1 cache use per-drive in a Cache Task? Topic is solved

[Jaga]

Couldn't figure out quite how to accomplish this, so I thought I'd post it here in the hopes that it might become a future feature.

I'm currently caching a server's boot drive (C:) with a L1/L2 setup, read & write strategy. I'd like to add a data drive to this cache task and set it to only use the L2 in a write strategy, but deny it access to using the L1 (so that both volumes share the L2). I think it would end up flushing the L1 due to the larger files stored on the data drive, and I want the L1 to stay dedicated to the boot drive only.

It would be similar to the L2 toggle on/off in the Volume Specifications area in the Cache Task configuration, but we'd be able to toggle the L1 on/off when the L2 was present (for each volume listed).

The only other way I can figure out how to do it is to partition the drive that currently handles the L2 into 2 separate volumes: one for the boot L2, the other for the data L2, each in it's own cache task. It's a slightly less efficient use of the large resources that a SSD can give.

[Support]

I'm sorry that currently this feature is not available. I remember that this feature is not implemented because of a design issue. But we do have a plan to support it in future.

[Jaga]

Thanks for the info, crossing fingers that it makes the cut someday.

[Support]

Supported in v3.0.9.
Thanks.

[Jaga]

Thank you!