Historian pruning customization to move data instead of drop them

A customer would like to keep only 2 years of data on historian and pushing older data on a "Cold" storage infrastructure.
Purpose of this "Cold" storage is in case of using Machine Learning one day, that would need data as much as possible.

Keeping only 2 years of data is purpose of pruning but this will drop all partitions. Can we customize the pruning process to copy before drop them ?


No. Push this storage logic to your DB or some external application.


There is such a thing as a tag history splitter, that would allow you to simultaneously have a redundant database with different pruning and partition settings.