sIs anyone using Hyper-V Production Checkpoints as an enhancement to Storage Replica? My thinking is that since Storage Replica is only crash consistent if we take hourly Production Checkpoints on the source server/cluster and keep them for 24 hours we will add the capability to fall back to a Production Checkpoint (or go back in time 24 hours) from our replica server, useful in a DR situation if the crash consistent copy turns out to be problematic. This would match the snapshot ability of Hyper-V Replica.
Has anyone done this, or read about anyone else doing this, in production?
EDIT: For clarity what I am talking about is the following:-
Server A is a Hyper-V host that has a main volume that has all the VM data stored on it including the checkpoint files. Server B has an identical volume which is kept synchronised with the main volume on Server A using Storage Replica. In order to provide for VSS application consistent recovery in the event of a DR situation a script is used to create Production Checkpoints say every hour on Server A. The same script deletes any checkpoint older than 24 hours, which will cause it to be merged in. In the event of a DR event where Server A is lost if Server B is brought online and the crash consistent Storage Replica of a particular VMs drives causes issues (say there is a database application with corruption causing DB not to mount etc.) then the Production Checkpoint can be used to restore the VM to an earlier time with a fully consistent VSS image.
The replication of checkpoints might significant increase the churn so real world testing would be needed to see how well this performs. Adding the Production Checkpoints to this Storage Replica scenario would match the features offered by Hyper-V Replica.
Has anyone tested this, done this, or read about any one doing this?