2010-06-07 08:04 AM
We have integrated SnapManager for SQL Server with Protection Manager and successfully use the feature to run the verification on the secondary storage.
Recently we had a problem on the DFM server, so the archiving of the snapshot did not take place.
Surprisingly SMSQL failed back for verification to the local snapshot, mounted this one and ran verification on the primary storage.
Under normal circumstances I would be happy with this design, but in this special case, there should be no verification at all if the secondary storage or the archiving-feature is not available.
Is there a way to prevent a local verification if the secondary storage is not available?
2010-06-08 01:46 AM
What you can do is to change your scheduled backup job to not to perform backup verification.
Yes, this is one possibility. Next we schedule a dedicated verification job, because we need the backups to be verified. The question would then be: is that "verify-only"-job acting the same way? That is: if the secondary storage is not available it mounts the snapshot of the primary?
We have to test it....