Sizing the OpsMgr Database

,

Depending on several factors, such as the type of data collected, the length of time that collected data will be kept, or the amount of database grooming that is scheduled, the size of the OpsMgr database grows or shrinks accordingly.

Tip

It is important to monitor the size of the database to ensure that it does not increase beyond the bounds of acceptable size. OpsMgr can be configured to monitor itself, supplying advance notice of database problems and capacity thresholds. This type of strategy is highly recommended because OpsMgr can easily collect event information faster than it can get rid of it.

The size of the operations database can be estimated through the following formula:

(Number of agents × 5 MB × retention days) + 1,024 overhead = estimated database size

For example, an OpsMgr environment monitoring 1,000 servers with the default seven-day retention period has an estimated 35 GB operations database:

(1,000 * 5 * 7) + 1,024 = 36,024 MB

The size of the reporting database can be estimated through the following formula:

(Number of agents × 3 MB × retention days) + 1,024 overhead = estimated database size

The same environment monitoring 1,000 servers with the default 400-day retention period has an estimated 1.1 TB reporting database:

(1,000 * 3 * 400) + 1,024 = 1,201,024 MB

Caution

It is important to understand that these estimates are rough guidelines only and can vary widely depending on the types of servers monitored, the monitoring configuration, the degree of customization, and other factors.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset