Our production system runs on Blade servers managed by NetApp filers.
Like many NetApp users, SnapManager is the most prominent part of our disaster recovery plan - this tool allows you to configure, schedule and manage SnapShot backups.
One option in the SnapManager backup step is the ability to mount a copy of the newly taken snapshot, and run DBCC checkdb to verify the snapshot backup of the database. After this step completes, SnapManager detaches the database and destroys the temporary LUN it was mounted on.
SnapManager backup jobs (with verification) fail when they run concurrent with SQLResponse because SQLResponse polls and accesses ALL the databases on the server, thereby blocking the detach action of the new database by SnapManager. Once this happens, all subsequent SnapManager backup jobs fail.
If only I could configure SQL Response to only poll certain databases - OR if we could schedule the polling periods for SQLResponse to exclude certain timespans we could work around this. But, I can't seem to locate these configuration options...
It's impractical for me to manually start and stop the service around SnapShot times - and I really lose the value of the product if it's not going most of the time to feed me alerts as they occur.
Do you have any suggestions?
Thanks, Normajean Bowen