OpsMgr 2007 PKI and Gateway Scenarios Part 2: What happens if the Management Server or Gateway Fails

 

 

Another good question I received the other day:

Question: What happens to agent data if the Management Server fails? What if the Gateway fails? Do I lose data?

Answer: Great question! There is actually queuing at every level of this equation in Operations Manager 2007 that, to a point, will prevent data loss in the event of failure between components.

Agent: It’s important to know that an agent can queue data when the Gateway or Management Server to which it reports fails. This value is stored in the MaximumQueueSizeBytes property (which is 10485760 (100mb) by default) and could be easily updated if necessary across multiple agents via Powershell.

Gateway: The Gateway has a queue of 100mb by default and will queue agent data in the event it’s upstream Management Server fails. However, if the queue fills up and the agent queue subsequently fills up, additional data would be lost. Likewise, if the Gateway fails with data in queue, data loss can occur.

While I’d like to share how to increase the gateway queue, I have it straight from the source that the default value should NOT be modified  significantly from it’s default of 100mb. So if you need high availability and no data loss, build redundancy in at the Gateway and Management Server and database levels with redundant Gateways and Management Servers, and clustered or mirrored SQL databases.

Management Server: Finally, the Management Server will queue data in the event the Operations database or data warehouse are unavailable. The  queue here is 100mb by default. In the event this queue fills and subsequently the agent queue fills up, data loss can occur.

One Response to “OpsMgr 2007 PKI and Gateway Scenarios Part 2: What happens if the Management Server or Gateway Fails”

  1. System Center Forum - SCOM 2007 Gateway Addendum, Errata, Summary and additional FAQs Says:

    [...] Part 2 - What happens if the Management Server or Gateway Fails [...]

Leave a Reply

privacy policy | terms of use | copyright © 2008 pete zerger