When using TimeFinder SnapVX, why would a redirect-on-write be changed to a copy-on-write?
When using TimeFinder SnapVX, why would a redirect-on-write be changed to a copy-on-write?
A redirect-on-write might be changed to a copy-on-write to prevent a new write from being demoted to a lower performance tier. Redirect-on-write optimizes for performance but can risk moving data to less optimal storage areas. Switching to copy-on-write ensures that the performance of writes remains consistent by avoiding redirection to potentially slower or less efficient tiers.
Even though ROW provides many benefits, there are situations where the traditional Asynchronous Copy on First Write (ACOFW) mechanism that has been used by TimeFinder for many years is the ideal option. For example, to prevent source data from being redirected to a less than ideal performance or compression tier.
https://infohub.delltechnologies.com/en-US/l/dell-emc-powermax-and-vmax-all-flash-timefinder-snapvx-local-replication-1/redirect-on-write/