Our QV site contain large models and as so, large QVDs (10-20 GB each), which contains historical data updated with incremental process.
Apparently the DR process that replicates the server (which backs up changes) sees the QVDs as completely changed, so it is backing up about 200 GB daily!
I was asked by my system administrator to find the best practice for DR on QV server.
I guess I could split the historical QVD... (although in some cases I need to look in the history with peek functions..)
I would love to get any input on that issue, including QV side solutions, as well as DR tools and process solution.