This feature is being planned, will update once we start working on this.Hector Linares commented
Are you referring to replications storms between VMM Library servers with DFS-R and Remote Differential Compression (RDC) enabled?
UR3 fixed an issue in the Library refresher logic which re-wrote the same unique ID in the file's alternate data stream after every refresh.
Changes to the file's primary data stream, alternate data stream, or security stream will stage the file for replication and replicate the changes chunks. We got reports from customers where this was causing the CPU to spike to 100% on the Library server with many files. With the fix, the refresher does not modify the alt-stream.
a. The VMM engineering team agrees that the impact is serious enough to warrant a fix but that does not change our DFS-R support statement – VMM does not support DFS-R. The fix addresses VMMID overwriting which makes no sense with every library share refresh.
b. VMM team can look into DFS-R support for a future release but no changes to the plan of record for R2 or vNext.