Since SCOM 2012 beta released, and a key feature is make everything Highly Available:
1. Make SCOM itself Highly Available. By remove RMS and make MS works peer to peer, unless all MS shutdown your SCOM still works.
2. Make Monitoring Highly Available. By add new concept Resource Pool, make remote monitoring highly Available.
Remote Monitoring is you specify a SCOM Agent monitoring a Device or WebSite that doesn’t depend on this Agent. In SCOM 2007 if the Agent shutdown, your MonitoringObject is not reachable by SCOM.
Now SCOM 2012 bring this new feature: Resource Pool, Resource pool contains Members, Observers, Member and Observer must be HealthService. If the MonitoringObject running in the pool, unless all pool member shutdown, your MonitoringObject is reachable by SCOM. Kind of like the Failover Cluster.
Pool Member provides monitoring service, all MonitoringObject actually running on the Members, Resource Pool also balance work load between Members.
Pool Observer works if the Pool has less than 3 Members, Observer votes in the failover, vote which member is alive. Recommend use default Observer.
Now you may want know how to implement this, all you need to do is insert Manages relationship between Pool and your MonitoringObject.
Note: if your MonitoringObject inherit from System.Device, this won’t works, you need find some other way.
<Discovery ID=“MonitoringObjectManagesByPool.Discovery” Enabled=“true” Target=“SC!Microsoft.SystemCenter.AllManagementServersResourcePool” ConfirmDelivery=“true” Remotable=“true” Priority=“Normal“>
<DiscoveryRelationship TypeID=“SC!Microsoft.SystemCenter.ManagementActionPointShouldManageEntity“ />
<DataSource ID=“GroupPopulator” TypeID=“SC!Microsoft.SystemCenter.GroupPopulator“>