I have 2 SharePoint farms that I admin and monitor with SCOM. We use a product called "HP Data Protector Granular Recovery" to do the restoration of documents and whatnot for our end users.
When the product does a restore of a database it mounts a local copy of the content database from whatever date you want to have restored with the same name but ending in a date. For example to restore files from a content database named "WSS_Content_DB" the product would mount a second database named "WSS_Content_DB_07_30_2013". So we now have 2 databases on the system and while SharePoint doesn't care that there is a second database, SCOM sure gets angry when that database is left long enough to get added to monitoring and the removed a day or two later.
Is there a way to be more selective about which databases SCOM is monitoring instead of it just monitoring every single database on the server?