I think the corruption itself isn't avoidable from the Qlik side because it's caused from too much workload / consumption of system resources and/or any other processes (security tools, windows shadow copies, ...) which conflicts with the storing and what makes it difficult is that there is no error-message.
A possibility to minimize the risk is to slice your qvd's maybe on a monthly level instead of using one big qvd. This will of course add some overhead but it might be also an advantage if you applies any incremental approaches.
Another way would be to check the number of records after the storing with qvdnoofrecords() and if they are lesser than in your resident-table or the function failed (because of the corruption) you could store the table again.
- Marcus
