Book Image

Getting Started with Microsoft System Center Operations Manager

By : Kevin Greene
Book Image

Getting Started with Microsoft System Center Operations Manager

By: Kevin Greene

Overview of this book

Most modern IT environments comprise a heterogeneous mixture of servers, network devices, virtual hypervisors, storage solutions, cross-platform operating systems and applications. All this complexity brings a requirement to deliver a centralized monitoring and reporting solution that can help IT administrators quickly identify where the problems are and how best to resolve them. Using System Center Operations Manager (OpsMgr), administrators get a full monitoring overview of the IT services they have responsibility for across the organization - along with some useful management capabilities to help them remediate any issues they've been alerted to. This book begins with an introduction to OpsMgr and its core concepts and then walks you through designing and deploying the various roles. After a chapter on exploring the consoles, you will learn how to deploy agents, work with management packs, configure network monitoring and model your IT services using distributed applications. There’s a chapter dedicated to alert tuning and another that demonstrates how to visualize your IT using dashboards. The final chapters in the book discuss how to create alert subscriptions, manage reports, backup and recover OpsMgr, perform maintenance and troubleshoot common problems.
Table of Contents (18 chapters)
Getting Started with Microsoft System Center Operations Manager
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Database grooming and maintenance


A key maintenance task for OpsMgr environments is ensuring the size of the databases is kept under control. This requirement can be achieved through understanding how data retention is configured and managed for both the Operational database and the Data Warehouse database. Data retention settings are defined to let OpsMgr know how long each database should hold onto information related to the different monitoring datasets. These settings will also have a direct effect on the size of your backup jobs and ongoing storage requirements.

Operational database free space requirements

Microsoft recommends that the Operational database should always have at least 50% free space available to support growth and indexing. This requirement refers to the amount of free space inside the database file itself and not on the volume that hosts the database.

A nice visual way to check the free space of a database is to launch the Disk Usage report from the SQL Management Studio...