Since I start my DBA career, as the best practice, I always verify backup to make sure it is complete and entire backup is readable. But, actually, I never ran into the situation(Let's name it ProblemX) that backup is successfully done while verify shows failures. I have some questions
1. Did you ever ran into this issue?
2. If yes, what's the root cause?
Microsoft doc says, 'However, RESTORE VERIFYONLY does not attempt to verify the structure of the data contained in the backup volumes.'. It impresses me that it's helpful, but not so much.
Recently, I invested tons of time on some programming to consolidate backup & restore. One of my confusion is, whether it's necessary to implement backup and Verify in parallel (means, verify without need to wait backup to be done). Technically, the process is
1. fetch a slice (byte array) from backup stream
2. Make a copy. Totally have two identical copies (original and new copy) now.
3. One copy for thread 1 which do the verify job
4. The other copy for thread 2 which writes data to backup file
But, if root cause of ProblemX is right in step 4, the verify does NOT make any sense.
Please let me know your thoughts on it. Thanks.
GASQL.com - Focus on Database and Cloud