management pack for microsoft system center operations manager · pdf filefor microsoft system...

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

EMC® SourceOne™Management Pack

for Microsoft System Center Operations ManagerVersion 7.1

Installation and User Guide302-000-178

REV 01

EMC SourceOne Management Pack for Microsoft SCOM Version 7.1 Installation and User Guide2

Copyright © 2013 EMC Corporation. All rights reserved.

Published September, 2013

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

http://support.emc.com

http://support.emc.com

EMC SourceOne Management Pack for Microsoft SCOM Version 7.1 Installation and User Guide 3

Chapter 1 OverviewMicrosoft System Center Operations Manager overview........... 10EMC SourceOne Management Pack features ............................... 11EMC SourceOne system organization ........................................... 12

Typical EMC SourceOne architecture .....................................13Front end and back end designations......................................14Operations Manager agents ......................................................15

Supporting multiple EMC SourceOne instances.......................... 16EMC SourceOne system views in Operations Manager .......16EMC SourceOne instance organization...................................17Requirements for supporting multiple instances ..................18

Chapter 2 InstallationInstall and configure prerequisites ................................................. 22

Operations Manager infrastructure .........................................22EMC SourceOne installation.....................................................23Preparing the environment .......................................................24

Install the EMC SourceOne Management Pack............................ 34Downloading the EMC SourceOne Management Pack ........35Importing the EMC SourceOne Management Pack ..............36Configure Run As profile ..........................................................39

Special considerations ...................................................................... 42Multiple instance support .........................................................42Optional overrides for Exchange journal mailbox monitoring59

Chapter 3 Monitoring the SystemOperations Manager console overview......................................... 66

Contents

EMC SourceOne Management Pack for Microsoft SCOM Version 7.1 Installation and User Guide4

Contents

Global features of Operations Manager .................................. 66Operations Manager panes ....................................................... 66

Using SourceOne Monitoring views.............................................. 67SourceOne Servers view............................................................ 67SourceOne Solution view .......................................................... 71Alert Views.................................................................................. 72Performance Views .................................................................... 76State Views .................................................................................. 83

Using Health Explorer ..................................................................... 89Using EMC SourceOne Reports...................................................... 91

EMC SourceOne Management Pack reports .......................... 91Navigation options..................................................................... 91Configuring EMC SourceOne reports ..................................... 97

Self-adapt the system ..................................................................... 103Low Disk Space......................................................................... 103Connectivity Issues .................................................................. 105SourceOne file version............................................................. 105


Preface

As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features.

Contact your EMC technical support professional if a product does not function properly or does not function as described in this document.

Purpose This document describes how to prepare for, install and use the EMC SourceOne Management Pack for Microsoft System Center Operations Manager.

Audience This document is part of the EMC® SourceOne™ documentation set, and is intended for use by installers of the product, EMC SourceOne system administrators, and mail server administrators.

Relateddocumentation

Related documents include:

◆ EMC SourceOne Email Management Installation Guide

◆ EMC SourceOne Email Management Administration Guide

◆ EMC SourceOne Email Management Release Notes

◆ EMC SourceOne Products Compatibility Guide

6 EMC SourceOne Management Pack for Microsoft SCOM Version 7.1 Installation and User Guide

Preface

Conventions used inthis document

EMC uses the following conventions for special notices.

Note: A note presents information that is important, but not hazard-related.

CAUTION!A caution contains information essential to avoid data loss or damage to the system or equipment.

IMPORTANT!An important notice contains information essential to operation of the software.

Typographical conventionsEMC uses the following type style conventions in this document:

Normal Used in running (nonprocedural) text for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• Names of resources, attributes, pools, Boolean expressions,

buttons, DQL statements, keywords, clauses, environment variables, filenames, functions, utilities

• URLs, pathnames, filenames, directory names, computer names, links, groups, service keys, file systems, notifications

Bold: Used in running (nonprocedural) text for:• Names of commands, daemons, options, programs,

processes, services, applications, utilities, kernels, notifications, system call, man pages

Used in procedures for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• What user specifically selects, clicks, presses, or types

Italic: Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis (for example a new term)• Variables

Courier: Used for:• System output, such as an error message or script • URLs, complete paths, filenames, prompts, and syntax when

shown outside of running text

Courier bold: Used for:• Specific user input (such as commands)


Preface

Where to get helpEMC support, product, and licensing information can be obtained as follows:

Product information — For documentation, release notes, software updates, or information about EMC products, licensing, and service, go to the EMC Online Support website (registration required) at:

https://support.emc.com/

Technical support — For technical support, go to EMC online support and select Support. On the Support page, you will see several options, including one to create a service request. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.

Online communities — Visit EMC Community Network at https://community.EMC.com/ for peer contacts, conversations, and content on product support and solutions. Interactively engage online with customers, partners, and certified professions for all EMC products.

Your commentsYour suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to:

[email protected]

Courier italic: Used in procedures for:• Variables on command line• User input variables

< > Angle brackets enclose parameter or variable values supplied by the user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces indicate content that you must specify (that is, x or y or z)

... Ellipses indicate nonessential information omitted from the example

https://support.emc.com/


Preface

Overview 9

1

This chapter provides an overview of the EMC SourceOne Management Pack for Microsoft System Center Operations Manager and is organized as follows:

◆ Microsoft System Center Operations Manager overview............ 10◆ EMC SourceOne Management Pack features ................................ 11◆ EMC SourceOne system organization ............................................ 12◆ Supporting multiple EMC SourceOne instances........................... 16

Overview


Overview

Microsoft System Center Operations Manager overviewMicrosoft System Center Operations Manager (referred to throughout this document as Operations Manager) provides a common interface for administrators to proactively monitor and manage the health and performance of an infrastructure’s devices and applications.

The EMC SourceOne Management Pack is supported on the following versions of Operations Manager:

◆ System Center Operations Manager 2012

◆ System Center Operations Manager 2007 R2

You can find details about Operations Manager architecture and implementation using the documentation that accompanies the version of the product you are using.

The following table provides useful Web links for Operations Manager information.

Table 1 Operations Manager Web resources

Topic Resource

What is SCOM? http://www.microsoft.com/en-in/server-cloud/system-center/operations-manager-overview.aspx

Key concepts http://technet.microsoft.com/library/hh230741.aspx

System Center 2012 Overview http://technet.microsoft.com/en-us/systemcenter/hh880681

System Center 2007 R2 Overview http://technet.microsoft.com/en-us/systemcenter/bb498233

Technical Documentation Download for System Center Operations Manager 2012

http://www.microsoft.com/en-us/download/details.aspx?id=29256

Technical Documentation Download for System Center Operations Manager 2007 R2

http://technet.microsoft.com/en-us/systemcenter/bb498235.aspx

http://www.microsoft.com/en-in/server-cloud/system-center/operations-manager-overview.aspx

http://technet.microsoft.com/library/hh230741.aspx

http://technet.microsoft.com/en-us/systemcenter/hh880681

http://technet.microsoft.com/en-us/systemcenter/bb498233

http://www.microsoft.com/en-us/download/details.aspx?id=29256

http://technet.microsoft.com/en-us/systemcenter/bb498235.aspx

EMC SourceOne Management Pack features 11

Overview

EMC SourceOne Management Pack featuresThe EMC SourceOne Management Pack provides specific functionality to support administrators of EMC SourceOne systems, infrastructure, and operations.

Using the EMC SourceOne Management Pack, administrators can measure the system health from a single user interface, collect performance data, detect errors, set thresholds which trigger alerts, and develop knowledge about common issues and solutions which can be captured using Operations Manager’s native features.

Key features include:

◆ Monitoring of EMC SourceOne system health from a single interface using agent-based communication.

◆ Simple access to overall system health using performance and hardware monitoring to provide information pertinent to EMC SourceOne.

◆ Drill-down monitoring of EMC SourceOne, enabling you to monitor EMC SourceOne at the system, instance, server, and component levels.

◆ Support for multiple instances of EMC SourceOne, enabling you to monitor separate EMC SourceOne instances based on the association for servers and components.

◆ Customized, configurable EMC SourceOne reports which use Operations Manager reporting features to enable you to add, schedule and distribute EMC SourceOne-specific reports to your reporting infrastructure.

◆ Support for customized knowledge about common events and trouble spots, enabling you to build, maintain and utilize your organization’s knowledge of EMC SourceOne system operations.


Overview

EMC SourceOne system organizationA standard EMC SourceOne environment can consist of the following types of EMC SourceOne servers:

◆ Master server

◆ Console server

◆ Worker server

◆ Web server (e.g., Web Services, Search, Mobile)

◆ Native Archive server

Other servers related to EMC SourceOne, but not directly monitored by the EMC SourceOne Management Pack include:

◆ Database servers

◆ Mail servers

◆ SharePoint servers

◆ File servers

In addition to native Operations Manager features, Microsoft provides management packs that can be used to monitor these servers and components.

EMC SourceOne system organization 13

Overview

Typical EMC SourceOne architectureFigure 1shows an example of a typical EMC SourceOne environment.

Figure 1 Typical EMC SourceOne architecture


Overview

Front end and back end designationsThe EMC SourceOne Management Pack logically organizes the EMC SourceOne servers into one of two groups:

◆ Front end servers – Includes EMC SourceOne Master, Worker, Search and Console servers.

◆ Back end servers – Includes only EMC SourceOne Native Archive servers

Figure 2 Front end and back end server organization

Since you can install multiple components on a single physical (or virtual) server, you can monitor the server itself, and you can also drill down using the Operations Manager interface into the multiple components installed on the server. For example, a small deployment may include two physical servers:

◆ A front end server with multiple EMC SourceOne software components installed (for example, Master Services, Worker Services, Console, Web Services, Search, Mobile Services).

◆ A back end server with Native Archive software installed.

In this case, the view from the Operations Manager interface would depict each installed software component as a separate icon under the server as shown in the following diagram. Each icon therefore represents an entity capable of being monitored in Operations Manager.

EMC SourceOne system organization 15

Overview

Operations Manager agentsEach EMC SourceOne server installation includes agent software which reports event, alert and performance counter information which communicates with the Operations Manager server based on pre-defined settings in the EMC SourceOne Management pack. This relationship forms the scope of the EMC SourceOne instance being monitored.


Overview

Supporting multiple EMC SourceOne instancesYou can use Operations Manager to monitor multiple EMC SourceOne instances, which expands the concept a typical, or single instance, EMC SourceOne environment described in “EMC SourceOne system organization” on page 12.

EMC SourceOne system views in Operations ManagerAt the highest level, the EMC SourceOne Management Pack provides a graphical overview of the EMC SourceOne system in two views:

◆ SourceOne Servers View - Includes all monitored EMC SourceOne servers and components in a single view.

◆ SourceOne Solution View - Can be used in environments with multiple instances of EMC SourceOne to display the relationship between distinct groups of front end servers and back end servers as separate instances. This relationship is technically based on the association of each server with a particular EMC SourceOne Activity database.

Figure 3 SourceOne system views

In a single instance environment (with one Activity database with which all servers are associated), the SourceOne Servers View and SourceOne Solution View essentially displays the same servers and components in either view.

In the case in which an additional instance of EMC SourceOne exists, the management pack enables you to monitor separate EMC SourceOne instances within the same environment by uniquely identifying the server relationships between front and back end servers.

Supporting multiple EMC SourceOne instances 17

Overview

EMC SourceOne instance organizationFigure 4 shows an example of the SourceOne Solution view comprised of multiple instances.

Figure 4 Solution View with multiple instances


Overview

The following table describes how the EMC SourceOne solution is organized in the example shown in Figure 4.

Requirements for supporting multiple instancesTo support multiple instance monitoring in Operations Manager:

◆ When deploying EMC SourceOne, the server relationship must be configured using server principal names. Simply using DNS host computer names cannot support the identification of the relationship between front end and back end servers.

◆ The EMC SourceOne Activity database is the key element which uniquely defines an instance. When you install Worker Services software, the installer registers that Worker with the specified Activity database. Therefore, to support this Worker-to-Activity database relationship which defines the instance, you must install the Worker Services software on all front end servers except for the Master. Note the following:

• If you do not want a front end server to function as a Worker, you can simply disable all Worker functions (for example, the ability to accept and process jobs).

Table 2 Instance organization by node

Node Description

SourceOne Solution node A fixed node representing entire EMC SourceOne system.

Instance node One or more instance node, identified by EMC SourceOne Activity database. Instance name is Master Server host name.

Front End and Back End node Each instance includes:• One Front End node (named Front End)• One Back End node (named Native Archive)

Native Archive connections In cases in which more than one Native Archive connection exists, separate nodes are displayed under the Native Archive node. Each node is named based on the name of the Native Archive connection configured in the EMC SourceOne console.

Component nodes All monitored EMC SourceOne components or other monitored components such as OS and system drives.

Supporting multiple EMC SourceOne instances 19

Overview

• If a front end server does not have Worker Services software installed, Operations Manager cannot identify the instance relationship for it and the server is displayed under "Unconnected servers". You can fix this situation by installing Worker Services software on the server and it will then display under the instance for the specified Activity database.

• If a server includes both front end software (for example, Worker Services software) and back end software (like Native Archive Services software), a duplicate node for this computer will display under the front end and back end nodes in the SourceOne Solution View.

• If your environment includes more than one back end server (for example, a "day-forward" Native Archive server, and an In Place Migrated Native Archive server), both servers will display under the back end node in the SourceOne Solution View.

• EMC EmailXtender servers in coexistence mode are not supported by the EMC SourceOne Management Pack.


Overview

Installation 21

2

This chapter describes how to prepare for and install the EMC SourceOne Management Pack and is organized as follows:

◆ Install and configure prerequisites .................................................. 22◆ Install the EMC SourceOne Management Pack............................. 34◆ Special considerations ....................................................................... 42

Installation


Installation

Install and configure prerequisitesPerform the following prerequisites in the order presented. This section includes the following topics:

◆ “Operations Manager infrastructure” on page 22

◆ “EMC SourceOne installation” on page 23

◆ “Preparing the environment” on page 24

Operations Manager infrastructureThis document assumes you have installed and are currently running a valid Microsoft System Center Operations Manager environment. The EMC SourceOne Management Pack is supported on the following Operations Manager versions:

◆ System Center Operations Manager 2012

◆ System Center Operations Manager 2007 R2

Refer to the following additional resources:

◆ For details on establishing your Operations Manager environment, refer to the Microsoft documentation that accompanies the software.

◆ For a list of useful links to Operations Manager information on the Web, refer to Table 1 on page 10.

◆ For compatibililty support for EMC SourceOne components, refer to the EMC SourceOne Products Compatibility Guide.

Management groupInstalling Operations Manager creates a management group. The management group is the basic unit of functionality. At a minimum, a management group consists of a management server, the operational database, and the reporting data warehouse database.

Management serverThe management server is the focal point for administering the management group and communicating with the database. When you open the Operations console and connect to a management group, you connect to a management server for that management group.

Install and configure prerequisites 23

Installation

Depending on the size of your computing environment, a management group can contain a single management server or multiple management servers.

The role of the management server is to administer the management group configuration, administer and communicate with agents, and to communicate with the databases in the management group.

Agent communicationAgent-based communication which occurs between EMC SourceOne host computers and Operations Manager is provided by an agent service which is installed and activated when a Windows host computer is discovered by Operations Manager. The agent collects data, compares sampled data to predefined values, creates alerts, and runs responses. A management server receives and distributes configurations to agents on monitored computers.

SQL Server Reporting ServicesThe EMC SourceOne Management Pack includes reporting features which leverages historical data stored in the Operations Manager reporting data warehouse database provided by Microsoft SQL Server Reporting Services.

By installing Operations Manager reporting functionality, the Reporting server is added to the Operations Manager management group which builds and presents reports from data in the data warehouse database.

EMC SourceOne installationThis document also assumes that you have installed EMC SourceOne Email Management, version 7.0 or higher.

For information on environment and system requirements and specific information on software compatibility, refer to the EMC SourceOne Products Compatibility Guide


Installation

Preparing the environmentAssuming that the appropriate Operations Manager and EMC SourceOne environment prerequisites are established, you can prepare the environment to support the EMC SourceOne Management Pack installation. Preparation steps include:

◆ “Ensure EMC SourceOne computers are discovered and agent-managed” on page 25

◆ “Identify the monitoring account” on page 26

◆ “Grant proxy access permission on Master server(s)” on page 26

◆ “Configure the EMC SourceOne service account as a Run As Account in Operations Manager” on page 27

◆ “Enable Microsoft Exchange access” on page 32

◆ “Enable performance-related services on 64-bit EMC SourceOne computers” on page 34

About multiple instancesThe procedures in this section are designed for a typical EMC SourceOne environment which consists of a single instance of EMC SourceOne. If you are implementing the EMC SourceOne Management Pack in a multiple instance environment, you should review the information provided in “Multiple instance support” on page 42 before performing the procedures in this section, as there are some special environment preparation considerations for this type of environment.

Refer to the following sections for more information:

◆ Conceptual information about multiple instance support - “EMC SourceOne instance organization” on page 17

◆ Special considerations and configuration procedures for multiple instance support - “Multiple instance support” on page 42

◆ Information on how a multiple instance environment is reflected in Operations Manager - “SourceOne Solution view” on page 71


Installation

Ensure EMC SourceOne computers are discovered and agent-managedOperations Manager uses agent-based communication to interact with EMC SourceOne host computers. This communication is established when you use native Operations Manager functionality to discover host computers on which EMC SourceOne software is installed.

Reviewing agent-managed devicesTo review the current list of agent-managed computers from the Operations Manager console:

1. Select Administration.

2. In the navigation pane, select Agent Managed.

3. Review the list of computers and ensure that all expected EMC SourceOne host computers are included.

Discovering devicesIf all expected EMC SourceOne host computers are not listed in the Agent Managed list, you can discover, and install the agent service, by doing the following from the Operations Manager console:


2. Right-click the left pane and select Discovery Wizard. The Computer and Device Management Wizard displays.

3. Select Windows Computers.

4. Click Next. The Auto or Advanced page displays.

5. Select one of the following:

• Automatic computer discovery - This option scans the domain for all Windows-based computers.

• Advanced discovery - This option allows you to manually specify the scope.

6. Click Next. Depending on your selection in the previous step, a list of Windows computers is displayed.

7. Select the computers on which EMC SourceOne components are installed and click Next. The Summary page displays.

8. Click Finish.

9. Select Administration >Device Management >Agent Managed to confirm that all EMC SourceOne computers are listed.


Installation

Identify the monitoring accountIdentify one or more monitoring accounts that you will use depending on your environment. Refer to the following topics:

◆ “Single instance environments” on page 26

◆ “Multiple instance environments” on page 26

Single instance environmentsIn an EMC SourceOne environment, the primary service account already includes the appropriate permissions needed to monitor EMC SourceOne systems and storage locations. You should plan to use this account as the monitoring account when configuring Operations Manager as described in “Configure the EMC SourceOne service account as a Run As Account in Operations Manager” on page 27.

Multiple instance environmentsIf you have separate EMC SourceOne instances, it is assumed that you have separate primary service accounts which support each instance. You should plan on also using the service account for the second instance when configuring the Run As Account in Operations Manager. This will result in two Run As profiles. After you have created groups of EMC SourceOne servers belonging to each instance, you can then associate the appropriate Run As profile with each group.

If you plan on supporting an environment consisting of multiple EMC SourceOne instances, ensure that you review the information provided in “Multiple instance support” on page 42.

Grant proxy access permission on Master server(s)On the Master server, enable the Agent Proxy setting. This allows the agent on the Master server to act as a proxy and discover managed objects on other computers. You can then associate the EMC SourceOne monitoring account.

From Operations Manager console:



3. Double-click the entry for the Master server in the FQDN column.


Installation

4. Click the Security tab.

Figure 5 Agent Properties tab - enable proxy access

5. Enable Allow this agent to act as a proxy and discover managed objects on other computers.

6. Click OK.

Configure the EMC SourceOne service account as a Run As Account in Operations Manager

Perform this procedure to associate the EMC SourceOne primary service account (“Identify the monitoring account” on page 26) as the Run As account in Operations Manager. From Operations Manager:


2. In the Administration navigation pane, under Run As Configuration, right click Account and select Create Run As Account.

The Create Run As Account Wizard displays.

3. Click Next to display the General Properties page.


Installation

Figure 6 Create Run As Account Wizard - General Properties page

4. Specify the account properties:

• Run As Account type - Select Windows.

• Display name - Type a display name for the Run As account.

• Description - Type an optional description for the Run As account.

5. Click Next. The Credentials page displays.

Figure 7 Create Run As Account Wizard - Credentials page


Installation

6. Specify the account credentials:

• User name - Type the primary service account name for the second instance.

• Password and Confirm password - Type a valid password for the service account.

• Domain - Ensure the correct domain is selected.

7. Click Next. The Distribution Security page displays.

Figure 8 Create Run As Account Wizard - Distribution Security page

8. Click More secure - I want to manually select the computers to which the credentials will be distributed.

9. Click Create to display the Completion page.

10. Click Close.

11. In the Accounts pane, right-click the EMC SourceOne monitoring account and select Properties.

12. Click the Distribution tab.

13. In the Selected computers section, click Add.


Installation

Figure 9 Distribution tab

14. Add all EMC SourceOne computers to which credentials will be distributed.


Installation

Figure 10 Distribution tab - add computers

15. When complete, click OK.


Installation

Enable Microsoft Exchange accessTo support monitoring of Exchange journaling mailboxes used by EMC SourceOne, you must perform some steps to facilitate communication between Operations Manager and Exchange. The specific options and procedures depend on your Exchange environment. Refer to the appropriate section:

◆ “Exchange 2003 environments” on page 32



◆ “Mixed Exchange environments (2003 and 2007)” on page 33

Exchange 2003 environmentsIn "pure" Exchange 2003 environments (for example, Exchange 2003 is the only version of Microsoft Exchange you are using), the only option is to enable the a Web service extension called WebDAV (Web Distributed Authoring and Versioning). From an Exchange server:

1. Open IIS Manager.

2. Select the Web Service Extensions node.

3. Enable WebDAV.

4. Restart IIS.

5. Repeat this procedure on remaining Exchange servers.

Exchange 2007 environmentsIn "pure" Exchange 2007 environments (for example, Exchange 2007 is the only version of Microsoft Exchange you are using), you can choose to use the WebDAV option described in “Exchange 2003 environments” on page 32. However, this option provides less security than the following option, which is to provide impersonation credentials to the EMC SourceOne primary service account to access the Exchange Web Services interface on your Exchange servers.

The Microsoft article entitled "Configuring Exchange Impersonation (Exchange Web Services)" describes how to configure the EMC SourceOne primary service account with Exchange Impersonation permissions for both the server and mailbox database:

http://msdn.microsoft.com/en-us/library/bb204095(EXCHG.80).aspx




Installation

The article provides the prerequisites and permissions needed to perform this procedure. Use the following specific procedures in the article to configure Exchange Impersonation for the EMC SourceOne primary service account:

◆ Exchange server – Refer to "To configure Exchange Impersonation on a server for a user", providing the EMC SourceOne primary service account as the user.

◆ Exchange mailbox database – Refer to "To configure Exchange Impersonation for a user on a database", providing the EMC SourceOne primary service account as the user.

Note: Performing this procedure on a single Exchange server enables impersonation access for all Exchange servers in the environment.

Exchange 2010 environmentsIn "pure" Exchange 2010 environments (for example, Exchange 2010 is the only version of Microsoft Exchange you are using), you can choose to use the WebDAV option described in “Exchange 2003 environments” on page 32. However, this option provides less security than the following option, which is to provide impersonation credentials to the EMC SourceOne primary service account to access the Exchange Web Services interface on your Exchange servers.

The Microsoft article entitled "Configuring Exchange Impersonation" describes how to configure the EMC SourceOne primary service account with Exchange Impersonation permissions for all users in an organization

:http://msdn.microsoft.com/en-us/library/bb204095.aspx

The article provides the prerequisites and permissions needed to perform this procedure. Use the procedure entitled "To configure Exchange Impersonation for all users in an organization", providing the EMC SourceOne primary service account as the user.

Note: Performing this procedure on a single Exchange server enables impersonation access for all of your Exchange servers.

Mixed Exchange environments (2003 and 2007)

If your environment includes a mix of Exchange 2003 and 2007, you must use the WebDAV option described in “Exchange 2003 environments” on page 32. For this scenario, after installing the EMC SourceOne Management Pack, you must also configure an override within the management pack to set the ExchangeVersion to "2003". After installing the



Installation

management pack, refer to “Optional overrides for Exchange journal mailbox monitoring” on page 59.

Enable performance-related services on 64-bit EMC SourceOne computersFor all EMC SourceOne host computers running on a 64-bit operating system (for example, Windows 2008), you must configure the following performance-related services to automatically start:

◆ Performance Counter DLL Host

◆ Performance Logs & Alerts

To configure the services:

1. Open the Windows Services console.

2. Navigate to the Performance Counter DLL Host service and set the service type to Automatic. Ensure the service Status is Started.

3. Navigate to Performance Logs & Alerts and set the service type to Automatic. Ensure the service Status is Started.

4. Close the Services console.

5. Repeat this procedure on remaining EMC SourceOne 64-bit host computers.

Install the EMC SourceOne Management PackOperations Manager provides the native ability to import custom Management Packs from the Operations console. This section describes how to download and install the EMC SourceOne Management Pack and includes the following topics:

◆ “Downloading the EMC SourceOne Management Pack” on page 35

◆ “In the navigation pane, right-click Management Packs and select Import Management Packs..” on page 36

◆ “Configure Run As profile” on page 39

Install the EMC SourceOne Management Pack 35

Installation

Downloading the EMC SourceOne Management PackChoose the appropriate language Management Pack and copy it to a local directory on the Operations console host computer.

The following is an example of an English file:

EMC.SourceOne.mp

Figure 11 Language Management Packs


Installation

Importing the EMC SourceOne Management PackTo import the management pack:

1. In the Operations console, click Administration.

2. In the navigation pane, right-click Management Packs and select Import Management Packs..

Figure 12 Import Management Pack

3. On the Select Management Pack page, click Add > Add from disk.


Installation

4. If the Online Catalog Connection dialog box displays, click No. There are no online catalog dependencies for the EMC SourceOne Management Pack.

5. Navigate to the temporary directory to which you copied the EMC SourceOne Management Pack file (EMC.SourceOne.mp).

Figure 13 Select Management Packs to import dialog box

6. Select the EMC.SourceOne.mp file and click Open.

7. The EMC SourceOne Monitoring Management Pack is added to the Import list.


Installation

Figure 14 Select and install the Management Pack

8. Click the EMC SourceOne Monitoring Management Pack and click Install. The Management Pack is installed.

9. After installation, click Close.


Installation

Configure Run As profileInstalling the Management Pack creates a default profile called "SourceOne Monitoring Account". You must associate the EMC SourceOne primary service account that you configured as a Run As account in “Configure the EMC SourceOne service account as a Run As Account in Operations Manager” on page 27 with the SourceOne Monitoring Account profile.

To configure the profile:


2. In the navigation pane, under Run As Configuration, click Profiles.

Figure 15 Profiles menu option

3. In the detail pane, right-click SourceOne Monitoring Account and select Properties. The Run As Profile Wizard displays.

Figure 16 Profile properties


Installation

4. Click Next. The General Properties page displays. The information on this page is provided with the Management Pack and is not editable.

Figure 17 Run As Profile Wizard - General Properties page

5. Click Next. The Run As Accounts page displays. Do the following:

a. Click Add. The Add a Run As Account dialog box displays.

b. Select the EMC SourceOne primary service account as the Run As account.

Note: If you are configuring multiple instances, ensure that you select the appropriate account for the instance you are configuring. Refer to “Multiple instance support” on page 42 for details.


Installation

6. In the This Run As Account will be used to manage the following objects area, select All targeted objects.

Figure 18 Add a Run As Account dialog box

7. Click OK.

8. Click Save. The Run As profile is created.

9. Click Close.


Installation

Special considerationsThere may be special considerations when implementing the EMC SourceOne Management Pack in certain environments. This section details the following considerations and associated actions:

◆ “Multiple instance support” on page 42

◆ “Optional overrides for Exchange journal mailbox monitoring” on page 59

Multiple instance supportAs described in “Supporting multiple EMC SourceOne instances” on page 16, you may want to monitor an environment which consists of more than one EMC SourceOne instance. In this scenario, there are some additional configuration considerations:

◆ “Create the Run As account for the second instance” on page 42

◆ “Grant proxy access permission on the Master server for the second instance” on page 46

◆ “Creating groups of EMC SourceOne servers to support multiple instances” on page 47

◆ “Configure a unique Run As profile for the second instance” on page 53

◆ “Configured instances are now visible in the SourceOne Solution view as described in “SourceOne Solution view” on page 71.” on page 58

Create the Run As account for the second instanceIf you have separate EMC SourceOne instances, it is assumed that you have separate primary service accounts which support each instance. Identify the primary service account for the second instance. You will specify this account in subsequent configuration procedures for the second instance.

To create a Run As account for the second instance from the Operations Manager console:


Special considerations 43

Installation

2. In the Administration navigation pane, under Run As Configuration, right click Account and select Create Run As Account. The Create Run As Account Wizard displays.

3. Click Next to display the General Properties page.

Figure 19 Create Run As Account Wizard - General Properties page

4. Specify the account properties:

• Run As Account type - Select Windows.



5. Click Next. The Credentials page displays.

Figure 20 Create Run As Account Wizard - Credentials page


Installation

6. Specify the account credentials:

• User name - Type the primary service account name for the second instance.

• Password and Confirm password - Type a valid password for the service account.

• Domain - Ensure the correct domain is selected.

7. Click Next. The Distribution Security page displays.

Figure 21 Create Run As Account Wizard - Distribution Security page

8. Click More secure - I want to manually select the computers to which the credentials will be distributed.

9. Click Create to display the Completion page.

10. Click Close.

11. In the Accounts pane, right-click the EMC SourceOne monitoring account for the second instance and select Properties.


Installation

Figure 22 Select account properties

The Properties page displays.

12. Click the Distribution tab.

13. In the Selected computers section, click Add.

Figure 23 Distribution tab


Installation

14. Add all EMC SourceOne computers that belong to the second instance to which credentials will be distributed.

Figure 24 Distribution tab - add computers

15. When complete, click OK.

Grant proxy access permission on the Master server for the second instanceOn the Master server associated with the second instance, enable the Agent Proxy setting. This allows the agent on this instance’s Master server to act as a proxy and discover managed objects on other computers. You can then associate the EMC SourceOne monitoring account for the second instance.

From Operations Manager console:



3. Double-click the entry for the Master server in the FQDN column.

4. Click the Security tab.


Installation

Figure 25 Agent Properties - enable proxy access

5. Agent Properties - enable proxy access

6. Enable Allow this agent to act as a proxy and discover managed objects on other computers.

7. Click OK.

Creating groups of EMC SourceOne servers to support multiple instancesIf the environment you intend to monitor includes more than one EMC SourceOne instance, you must logically arrange the EMC SourceOne servers that belong to each instance in a group in Operations Manager.

To create a group, from Operations Manager console:

1. Select Authoring.

2. In the navigation pane, right-click Groups and select Create a new group.


Installation

Figure 26 Create Group Wizard

3. Enter a contextual Name and Description for the group.

4. In the Select destination management pack area, select New. The General Properties page displays.

IMPORTANT!You should elect to create a new management pack as a destination for this group. If you select the Default Management Pack, you run the risk that a future upgrade of Operations Manager and its default management pack will negate this change.


Installation

5. In the General Properties page, enter a Name, Version and Description for the new management pack.

Figure 27 Management Pack General Properties page

6. Click Next.

7. Provide any additional information using the Knowledge page.

8. Click Create. You are returned to the General Properties page of the Create Group Wizard.

9. Click Next. The Explicit Members page displays.


Installation

Figure 28 Explicit Members page

10. Click Add/Remove Objects. The Create Group Wizard - Object Selection dialog box displays. Do the following:

a. In the Search for list, select Windows Server.

b. Click Search. A list of servers displays in the Available items area.

Figure 29 Object Selection - Available items


Installation

c. From the Available items list, select one or more EMC SourceOne servers that belong to the instance for which you are configuring the group and click Add. The selected servers are added to the Selected objects list.

Figure 30 Object Selection - Selected objects

d. Click OK. The Choose Members from a List page displays with the selected servers included in the Group members list.

Figure 31 Choose Members from a List page


Installation

11. Click Next. The optional Dynamic Members page displays.

12. Click Next. The optional Subgroups page displays.

13. Click Next. The Excluded Members page displays.

14. Click Create. The group is created and added to the list of groups.

Figure 32 Groups list


Installation

Configure a unique Run As profile for the second instanceConfigure a second Run As profile and associate it with the Run As account that you created for the second instance (“Create the Run As account for the second instance” on page 42).


2. In the navigation pane, under Run As Configuration, right-click Profiles and select Create Run As Profile.

Figure 33 Create Run As Profile

The Run As Profile Wizard displays.

3. Click Next. The General Properties page displays.


Installation

Figure 34 Run As Profile Wizard - General Properties page

4. Type the following information:



• Select destination management pack - Select the custom management pack you created earlier when creating the Run As account (“Creating groups of EMC SourceOne servers to support multiple instances” on page 47).

Figure 35 Select destination management pack

5. Click Next. The Run As Accounts page displays.

6. Click Add. The Add a Run As Account dialog box displays.


Installation

Figure 36 Add Run As Account dialog box

7. In the Run As account field, select the Run As account you created in “Create the Run As account for the second instance” on page 42.

Figure 37 Select Run As account


Installation

8. In the This Run As Account will be used to manage the following objects area, select A selected class, group, or object.

Figure 38 Select Run As account - managed objects

9. Click Select > Group.

Figure 39 Select Group

The Group Search dialog box displays.

10. In the Management pack dropdown list, select the custom management pack you created earlier when creating the Run As account (“Creating groups of EMC SourceOne servers to support multiple instances” on page 47). This is the management pack in which the group information is stored.


Installation

Figure 40 Group Search dialog box

11. Click Search. The group you configured for the second instance displays in the Available Groups area.

Figure 41 Group Search dialog box - Available Groups

12. Click the group containing computers for the second instance.

13. Click OK. The Add a Run As Account dialog box displays.


Installation

Figure 42 Add Run As Account dialog box - results

14. Review the information to ensure that the Run As account and group reflect the second instance and click OK.

The Run As Accounts page displays listing the Run As account for the second instance.

Figure 43 Run As Profile Wizard - account listed

15. Click Create to create Run As profile. The Completion page displays.

16. Click Close.

17. Verify that the profile is lised in the Profiles pane.

18. Configured instances are now visible in the SourceOne Solution view as described in “SourceOne Solution view” on page 71.


Installation

Optional overrides for Exchange journal mailbox monitoringAs described in “Enable Microsoft Exchange access” on page 32, to support monitoring of Exchange journaling mailboxes used by EMC SourceOne, you must perform some steps to facilitate communication between Operations Manager and Exchange.

After installing the EMC SourceOne Management Pack, and depending on your Exchange environment, you may need to configure overrides using the Authoring pane on parameters associated with the following management pack objects:

◆ Monitors

◆ Rules

Once configured, these overrides are stored in the Default Management Pack that is native to Operations Manager. This allows you to later upgrade the EMC SourceOne Management Pack without having to re-configure the override settings.

Configure overrides on the Monitors objectFrom Operations Manager console:


2. In the navigation pane, select Monitors.

Figure 44 Monitors node

3. In the Look for field, type SourceOne and click Find Now.

4. In the list of results, locate Master: Journal Mailbox Item Count Monitor.


Installation

Figure 45 Master: Journal Mailbox Item Count Monitor

5. Right-click Master: Journal Mailbox Item Counter Monitor and select Overrides > Override the Monitor > For all objects of class: Master. The Override Properties dialog box displays.

Figure 46 Override menu navigation


Installation

Figure 47 Override Properties dialog box (Monitor)

6. Select the ExchangeVersion and SSLEnabled parameters.

7. Configure the override values based on your environment as described in Table 3 on page 61.

Table 3 Override Values for Monitor based on Exchange environment (1 of 2)

Exchange Environment

ExchangeVersion Override Value SSLEnabled Override Value

2003 Set the Override Value to 2003

• If using SSL, set the Override Value to 1

• If not using SSL, set the Override Value to 0


Installation

8. Click OK.

Configure overrides on the Rules objectFrom Operations Manager console:


2. In the navigation pane, select Rules.

Figure 48 Rules node

2007 • If using Exchange Web Services, set the Override Value to 2007

• If using WebDAV, set the Override Value to 2003







Mixed If oldest Exchange version is Exchange 2003, set the Override Value to 2003. Otherwise, set the value to 2007 or 2010.



Table 3 Override Values for Monitor based on Exchange environment (2 of 2)




Installation

3. In the Look for field, type SourceOne and click Find Now.

4. In the list of results, locate Collect ES1:JournalMailbox\ItemCount.

Figure 49 Collect ES1:JournalMailbox\ItemCount Rule

5. Right-click Collect ES1:JournalMailbox\ItemCount and select Overrides > Override the Rule > For all objects of class: Master. The Override Properties dialog box displays.

Figure 50 Override menu navigation

Figure 51 Override Properties dialog box (Rule)


Installation

6. Select the ExchangeVersion and SSLEnabled parameters.

7. Configure the override values based on your environment as described in Table 4 on page 64.

8. Click OK.

Table 4 Override Values for Rule based on Exchange environment



2003 Set the Override Value to 2003 • If using SSL, set the Override Value to 1










Mixed If oldest Exchange version is Exchange 2003, set the Override Value to 2003. Otherwise, set the value to 2007 or 2010.



Monitoring the System 65

3

The EMC SourceOne Management Pack enhances the functionality of Operations Manager by providing more detailed information about the managed EMC SourceOne systems.

This chapter is organized as follows:

◆ Operations Manager console overview .......................................... 66◆ Using SourceOne Monitoring views ............................................... 67◆ Using Health Explorer....................................................................... 88◆ Using EMC SourceOne Reports....................................................... 90◆ Self-adapt the system....................................................................... 102

Monitoring the System



Operations Manager console overviewThe Operations Manager console provides a number of native monitoring and reporting functions. Adding the EMC SourceOne Management Pack provides specific views and details that are useful in monitoring EMC SourceOne to ensure a healthy, well-performing system.

Global features of Operations ManagerThis document provides details on using the features provided with the EMC SourceOne Management Pack. For the global features provided with Operations Manager (For example, features not specific to EMC SourceOne), refer to the Microsoft documentation and online help that accompanies Operations Manager.

Operations Manager panesThe Operations Manager panes used most often by an EMC SourceOne administrator are:

◆ Monitoring pane – The Monitoring pane enables administrators to identify and resolve issues by accessing views provided using nodes in the Monitoring node tree. This includes global monitoring views provided with Operations Manager as well as customized views provided with the EMC SourceOne Management Pack which are accessed using the SourceOne Monitoring node. Refer to “Using SourceOne Monitoring views” on page 67 for details on the EMC SourceOne Management Pack monitoring capabilities.

◆ Reporting pane – Like the Monitoring pane, the Reporting pane provides common reports provided by Operations Manager as well as SourceOne reports provided by the EMC SourceOne Management Pack. Refer to “Using EMC SourceOne Reports” on page 90 for details on the EMC SourceOne Management Pack reporting features.

Using SourceOne Monitoring views 67


Using SourceOne Monitoring viewsThe SourceOne Monitoring view is provided by the EMC SourceOne Management Pack which contains predefined monitoring settings enabling you to monitor EMC SourceOne servers, services and applications.

Figure 52 SourceOne Monitoring views

SourceOne Servers viewSelecting the SourceOne Servers node provides a graphical view of all SourceOne servers in your environment. This view displays all EMC SourceOne servers, regardless of the instance to which each server belongs.

Note: Refer to “EMC SourceOne system views in Operations Manager” on page 16 for details on single and multiple instance EMC SourceOne environments.



Figure 53 SourceOne Server view

This view displays the following server types:

◆ Native Archive servers

◆ Console servers

◆ Master servers

◆ Search servers

◆ Worker servers

Each server icon represents a physical (or virtualized) server with EMC SourceOne software installed.



Viewing server detailsYou can view server details by selecting a server icon to display the the Detail View pane. For example, Figure 54 on page 69 displays the server details for a server named ARCHIVE1.

Figure 54 Server Detail View example

The Detail View provides information such as server name information, IP address, network name and other details.

Expanding a server iconYou can expand a server icon by clicking the plus (+) sign adjacent to the server name. Expanding a server icon provides a graphical view of following components for a server:

◆ Operating system

◆ System drives

◆ Health services properties

◆ Installed EMC SourceOne components

For example, Figure 55 displays the components on a server named ARCHIVE1.



Figure 55 Expanded server icon example

In this example, ARCHIVE1 includes the following components:

◆ Two system drives (C: and D:)

◆ Microsoft Windows operating system

◆ EMC SourceOne Native Archive software

EMC SourceOne supports installing more than one EMC SourceOne software component on a single server (for example, an EMC SourceOne Master server may also have EMC SourceOne Console software installed on the same server). Therefore, all installed EMC SourceOne software components are graphically displayed when you expand the server icon.



Viewing component detailsYou can view component-level details by clicking on a component icon. For example, Figure 56 on page 71 displays the Detail View for the Native Archive software component on a server named ARCHIVE1.

Figure 56 Component Detail View example

The displayed details depend on the specific component you select. In this example, the details displayed include the name and version of Native Archive Services software installed.

SourceOne Solution viewThe SourceOne Solution view is similar to the SourceOne Server view described in “SourceOne Servers view” on page 67. The SourceOne Solution view arranges these servers logically by EMC SourceOne instance.

Refer to the following sections for more information:

◆ Conceptual information about multiple instance support - “EMC SourceOne instance organization” on page 17

◆ Special considerations and configuration procedures for multiple instance support - “Multiple instance support” on page 42



Alert ViewsThe Alert view provides a centralized view which enables you to review active alerts, manage and close active alerts, and review closed alerts. The following views are displayed:

◆ “Active Alerts” on page 72

◆ “Closed Alerts” on page 74

Active AlertsTo view active alerts:

1. Select SourceOne Monitoring > Alert Views > Active Alerts. The list of alerts grouped by severity level are displayed in the Active Alerts pane.

Figure 57 Active Alerts pane



2. Select an alert and view the Alert Details area for more information.

Figure 58 Alert details area

3. There are several options available to manage or close the alert. To access these options, right-click the alert.

Figure 59 Active Alert right-click options

4. Perform the desired action on the alert. Useful options include:

• Set Resolution State

• Close Alert

• Forward to

For details on managing alerts using Operations Manager, refer to the Microsoft System Center Operations Manager documentation set.



Closed AlertsTo view closed alerts:

1. Select SourceOne Monitoring > Alert Views > Closed Alerts. The list of closed alerts grouped by severity level are displayed in the Closed Alerts pane.

Figure 60 Active Alerts pane

2. Select an alert and view the Alert Details area for more information.

3. There are several options available to manage or re-open the alert. To access these options, right-click the alert.

Figure 61 Closed Alert right-click options

4. Perform the desired action on the alert. Useful options include:

• Set Resolution State

• Forward to

For details on managing alerts using Operations Manager, refer to the Microsoft System Center Operations Manager documentation set.



Performance ViewsThe Performance views are based on performance counters identified in the EMC SourceOne Management Pack. The views are categorized by product, platform and system views and are described in the following sections:

◆ “Email - Historical Archive Performance View” on page 76

◆ “Email - Journal Mailbox View” on page 76

◆ “Email - Journal Performance View” on page 76

◆ “Email - Shortcut Performance View” on page 76

◆ “File Systems - File Systems Performance View” on page 77

◆ “Monitors - Items and Size Monitors” on page 77

◆ “Platform - Index Sets Status View” on page 77

◆ “Platform - Job Scheduling Performance View” on page 78

◆ “Platform - Native Archive Index Performance View” on page 78

◆ “Platform - Native Archive Performance View” on page 78

◆ “Platform - Native Archive Volume Performance View” on page 78

◆ “Platform - Shared Folder Space View” on page 79

◆ “Platform - System Performance View” on page 80

◆ “SharePoint - SharePoint Performance View” on page 80

◆ “System - CPU Performance View” on page 80

◆ “System - Disk Performance View” on page 81

◆ “System - Memory Performance View” on page 81



Email - Historical Archive Performance View

Email - Journal Mailbox View

Email - Journal Performance View

Email - Shortcut Performance View

Table 5 Historical Archive performance counters

Counter Description

Msgs Failed Processing The number of message objects which failed to be processed by the historical archive activities.

Msgs Processed/sec The number of message objects processed by historical archive activities.

Table 6 Journal mailbox counters

Counter Description

ItemCount The number of items in each journal mailbox configured in journal activities.

Table 7 Journal performance counters

Counter Description

Msgs Processed/sec The number of message objects processed per second by journaling activities.

Msgs Failed Processing The number of message objects which failed to be processed by journaling activities.

Table 8 Shortcut performance counters

Counter Description

Msgs Failed Shortcutting

The number of messages that failed to be processed by shortcutting activities.

Msgs Shortcutted/sec The number of message objects processed per second by shortcutting activities.



File Systems - File Systems Performance View

Monitors - Items and Size Monitors

Platform - Index Sets Status View

Table 9 File Systems performance counters

Counter Description

Files Processed/sec The number of message objects processed per second by EMC SourceOne for File Systems activities.

Files Failed Processing The number of messages that failed to be processed by EMC SourceOne for File Systems activities.

Table 10 Items and size counters

Counter Description

Master: SMTP Journal DataSource Item Count Monitor

The number of items in each SMTP Journal DataSource.

Master: SMTP Journal DataSource Item Size Monitor

The size of items in each SMTP Journal DataSource.

Native Archive: Lost And Found Item Count Monitor The number of items in each Lost And Found folder.

Native Archive: Lost And Found Item Size Monitor The size of items in each Lost And Found folder.

Native Archive: Message Center Item Count Monitor The number of items in each Message Center folder.

Native Archive: Message Center Item Size Monitor The size of items in each Message Center folder.

Native Archive: Unpack Area Item Count Monitor The number of items in Unpack Area folder.

Native Archive: Unpack Area Item Size Monitor The size of items in Unpack Area folder.

Table 11 Index sets status counters

Counter Description

FlaggedCount The number of flagged index sets on the master server.

Total Count The total number of index sets on the master server.



Platform - Job Scheduling Performance View

Platform - Native Archive Index Performance View

Platform - Native Archive Performance View

Platform - Native Archive Volume Performance View

Table 12 Job scheduling counters

Counter Description

Jobs Running The number of jobs running on a worker server.

Table 13 Native Archive index performance counters

Counter Description

Indexed/sec The number of objects indexed per second on the Native Archive server.

Unindexable Documents

Number of documents that were added as unindexable.

Transaction Retries Number of times transaction files have retried.

Table 14 Native Archive performance counters

Counter Description

Failed Archive The number of objects that failed to be archived on the Native Archive server.

Archived/sec The number of objects archived per second on the Native Archive server.

Table 15 Native Archive volume performance counters

Counter Description

Volumes burnt The number of EMC SourceOne volumes successfully written to disk by the Native Archive server.

Volumes failed to burn The number of EMC SourceOne volumes that failed to be written to disk by the Native Archive server.

Volume burn time(sec) The amount of time (in seconds) to write a volume to disk by the Native Archive server.



Platform - Shared Folder Space ViewThis view shows the free space for shared storage locations used by EMC SourceOne.

Table 16 Shared folder space counters

Counter Description

Free space in GBytes Shows the free space (in GB) for the following EMC SourceOne storage locations:• Archive storage location (Native Archive server)• Index storage location (Native Archive server)• Message center storage (Native Archive server)• Job logs storage location (Worker server)



Platform - System Performance View

SharePoint - SharePoint Performance View

System - CPU Performance View

Table 17 System performance counters

Counter Description

Avg Msg Processing Time(ms)

The number of messages processed (in milliseconds) by a worker server.

Table 18 SharePoint performance counters

Counter Description

Documents Processed/sec

The number of documents processed (in seconds) by a worker server configured to process Microsoft SharePoint activities.

Documents Failed Processing

The number of documents that failed to be processed by a worker server configured to process Microsoft SharePoint activities.

Table 19 CPU performance counters

Counter Description

% Processor Time Determines the percentage of time the processor is busy by measuring the percentage of time the thread of the Idle process is running and then subtracting that from 100 percent. This measurement is the amount of processor utilization.



System - Disk Performance View

System - Memory Performance View

Table 20 Disk performance counters

Counter Description

% Free Space Percentage of total usable space on the selected logical disk drive that was free.

Current Disk Queue Length

The number of requests outstanding on the disk at the time the performance data is collected. It also includes requests in service at the time of the collection. This is a instantaneous snapshot, not an average over the time interval. Multi-spindle disk devices can have multiple requests that are active at one time, but other concurrent requests are awaiting service. This counter might reflect a transitory high or low queue length, but if there is a sustained load on the disk drive, it is likely that this will be consistently high. Requests experience delays proportional to the length of this queue minus the number of spindles on the disks. For good performance, this difference should average less than two.

Free Megabytes Displays the unallocated space, in megabytes, on the disk drive in megabytes. One megabyte is equal to 1,048,576 bytes.

Table 21 Memory performance counters

Counter Description

Available MBytes Available MBytes is the amount of physical memory, in Megabytes, immediately available for allocation to a process or for system use. It is equal to the sum of memory assigned to the standby (cached), free and zero page lists.

Committed Bytes Committed Bytes is the amount of committed virtual memory, in bytes. Committed memory is the physical memory which has space reserved on the disk paging file(s). There can be one or more paging files on each physical drive. This counter displays the last observed value only; it is not an average.



State ViewsThe EMC SourceOne Management Pack provides two types of state views:

◆ “Component State View” on page 82

◆ “Server State View” on page 85

Component State ViewThe component state view provides a list of each monitored EMC SourceOne components and the host computer on which the component is installed. Each component is displayed using the following format:

component (host)

Figure 62 shows an example of an EMC SourceOne environment.

Figure 62 Component State View



Monitored component typesTable 22 describes the monitored component types.

Table 22 Component types

Component Installed software

Console EMC SourceOne Console software

DMServer EMC SourceOne Discovery Manager Server software

FileArchiveBCE EMC SourceOne for File Systems Business Component Extensions software

Master EMC SourceOne Master Services software

Mobile EMC SourceOne Mobile Services software

MoverAgent Component installed with EMC SourceOne Master Services if you select Microsoft Office 365 support. This component moves Microsoft Office 365 journal report files to be used by the Journal activity.

Native Archive EMC SourceOne Native Archive Services software

SharePointBCE EMC SourceOne for Microsoft SharePoint Business Component Extensions software

WebSearch EMC SourceOne Search software

WebService EMC SourceOne Web Services software

Worker EMC SourceOne Worker Services software



Component statesTable 23 lists the possible component states.

Detail View areaYou can click a component and review details using the Detail View area of the Component State View pane.

Figure 63 Detail View

Table 23 Component states

Icon State Description

Healthy Based on the configured thresholds, the component is in a healthy state.

Warning There is a problem that may require attention.

Critical There is a problem that requires attention.

Not monitored The component is not monitored.



Server State ViewThe Server State View displays all monitored EMC SourceOne servers in your environment.

Figure 64 shows an example of an EMC SourceOne environment.

Figure 64 Server State View

Server statesTable 24 lists the possible component states.

Table 24 Server states


Healthy Based on the configured thresholds, the server is in a healthy state.



Detail View areaYou can click a server and review details using the Detail View area of the Server State View pane.

Figure 65 Detail View

Warning There is a problem that may require attention.

Critical There is a problem that requires attention.

Not monitored The component is not monitored.

Table 24 Server states




File State ViewThe File State View lists the SourceOne files and their version for all SourceOne servers as illustrated in the following figure.



Using Health ExplorerHealth Explorer is a feature of Operations Manager which enables you to view and take action on alerts, state changes and other significant issues generated by monitoring objects on your network.

You can access Health Explorer from most monitored objects in Operations Manager. For example, to access Health Explorer from the Component State View:

1. Right-click a component state.

2. Select Open > Health Explorer. Health Explorer for the selected object displays.

Figure 66 Accessing Health Explorer

Using Health Explorer 89


Figure 67 Health Explorer example

3. Use the Health Explorer to review the displayed health monitors for the selected object.

For details on using Health Explorer, refer to the Microsoft System Center Operations Manager documentation set.



Using EMC SourceOne ReportsThe Operations Manager interface provides multiple methods to access reports, depending on the view or node you select. You can use EMC SourceOne reports to provide a report with custom parameters and date ranges.

EMC SourceOne Management Pack reportsThe EMC SourceOne Management Pack includes the following EMC SourceOne reports:

◆ EMC SourceOne Performance Counters Summary Report

◆ EMC SourceOne Performance Counters Trend Report

◆ EMC SourceOne System Resource Analysis Report

Navigation optionsYou can access the EMC SourceOne reports from the following Operations Manager views:

“Accessing reports from the Monitoring view” on page 90

“Accessing reports from the Reporting view” on page 94

Accessing reports from the Monitoring viewIf you are using the Operations Manager Monitoring view, you can use the Actions pane to provide quick access from a selected node to EMC SourceOne reports. The available reports depend on the type of node you select.

Example - Accessing reports from the Component State ViewFor example, you can access both the EMC SourceOne Performance Counters Summary Report and EMC SourceOne Performance Counters Trend Report for a specific component listed in the Component State View.

Using EMC SourceOne Reports 91


From the Operations Manager Monitoring view:

1. Select SourceOne Monitoring > State Views > Component State View. The list of monitored components displays in the Components State View pane.

Figure 68 Component State View

2. Select a component.

3. Click the Actions button (or select Actions > component_name Reports). The Actions pane displays.



Figure 69 Actions pane

4. In the Reports area, select one of the following EMC SourceOne reports:

• EMC SourceOne Performance Counters Summary Report

• EMC SourceOne Performance Counters Trend Report

5. Refer to “Configuring EMC SourceOne reports” on page 96 for details on configuring report parameters and scheduling options.



Example - Accessing reports from the Server State ViewAs another example, you can access the EMC SourceOne System Resource Analysis Report for a specific server listed in the Server State View. From the Operations Manager Monitoring view:

1. Select SourceOne Monitoring > State Views > Server State View. The list of monitored servers displays in the Server State View pane.

Figure 70 Server State View

2. Select a server.

3. Click the Actions button (or select Actions > Windows Computer Reports). The Actions pane displays.



Figure 71 Actions pane

4. In the Reports area, select the EMC SourceOne System Resource Analysis Report.


Accessing reports from the Reporting viewYou can also access reports directly from the Operations Manager Reporting tab.

From the Operations Manager Reporting view:

1. Select Reporting > EMC SourceOne Monitoring. The EMC SourceOne Monitoring pane displays the available reports:

• EMC SourceOne Performance Counters Summary Report

• EMC SourceOne Performance Counters Trend Report

• EMC SourceOne System Resource Analysis Report



Figure 72 EMC SourceOne Monitoring reports

2. Select a report.

3. Click The Actions button to display report actions.

Figure 73 Report actions

4. Select an appropriate action. Actions for each report include:

• Open – Click Open to display the report configuration page.

• Schedule – Click Schedule to configure scheduling options for the report.




Configuring EMC SourceOne reports“Navigation options” on page 90 provides examples of ways that you can access EMC SourceOne reports from either the Monitoring view or Reporting view in Operations Manager.

Once you have accessed the configuration page for a report, the following sections provide details on the parameters you can to configure for each EMC SourceOne report:

◆ “Configure an EMC SourceOne Performance Counters Reports (Summary or Trends)” on page 96

◆ “Configure an EMC SourceOne System Resource Analysis Report” on page 99

Configure an EMC SourceOne Performance Counters Reports (Summary or Trends)There are two reports based on performance counter monitoring provided with the EMC SourceOne Management Pack:

◆ EMC SourceOne Performance Counters Summary Report

◆ EMC SourceOne Performance Counters Trend Report

Note: This procedure assumes you have accessed the report configuration page using one of the methods described in “Navigation options” on page 90.

To configure a report from the report configuration page:

1. Click the Category dropdown list and select a category. A category is a monitored entity, and corresponds to the views described in “Using SourceOne Monitoring views” on page 67.



Figure 74 Category list example

2. Click the Counter dropdown list and select a counter.

Each category has one or more associated counter values. For example, if you select ES1:Index Location which monitors the available disk space for the EMC SourceOne index storage location, you must select the Free space in Gbytes counter.

Figure 75 Counter list example



Once you select a counter, the Object and Instance dropdown lists become editable. Note the following:

• The values displayed in each of these lists corresponds to the values you selected in the Category and Counter lists.

• As an example, if you select the ES1:IndexLocation category and Free space in Gbytes counter, the Object list is limited to only the servers on which the index location storage is being monitored.

3. Click the Object dropdown list and select an object.

Figure 76 Object list example

4. Click the Instance dropdown list and select an instance.

Figure 77 Instance list example



5. Configure the Start Date and End Date criteria.

6. Configure the Time Unit (Daily or Hourly).

7. Click Run. The report is generated.

Figure 79 shows an example of a Performance Data Summary Report.

Figure 78 Performance Data Summary Report example

There are a number of reporting functions and convenience features you can utilize with EMC SourceOne reports such as exporting, scheduling, saving to favorites, and publishing. Refer to the Microsoft System Center Operations Manager documentation set for details.

Configure an EMC SourceOne System Resource Analysis ReportThis report provides details on system resources for the selected system.

Note: This procedure assumes you have accessed the report configuration page using one of the methods described in “Navigation options” on page 90.



To configure a report from the report configuration page:

1. Click the Select the type of resource to analyze dropdown list and select a resource type. Resources which can be analyzed include:

• CPU (% Processor Time)

• Memory (Committed Bytes)

• Disk (Current Disk Queue Length)

Note: These resources correspond to the monitoring views described in “Using SourceOne Monitoring views” on page 67.

Figure 79 Category list example

2. Click the Server dropdown list and select a server.

Figure 80 Counter list example

3. Configure the Start Date and End Date criteria.

4. Click Run. The report is generated.

Figure 82 shows an example of a System Resource Analysis Report.



Figure 81 System Resource Analysis Report example

There are a number of reporting functions and convenience features you can utilize with EMC SourceOne reports such as exporting, scheduling, saving to favorites, and publishing. Refer to the Microsoft System Center Operations Manager documentation set for details.



Self-adapt the systemThe following are conditions that will be detected:

◆ “Low Disk Space” on page 102

◆ “Connectivity Issues” on page 104

◆ “SourceOne file version” on page 105

Low Disk Space Free space will be monitored. When available disk space in Native Archive reaches a previously configured threshold an email alert is sent to the SourceOne administrator complete with both the problem and suggested solutions.

A configurable variable is set to determine the following:

◆ IntervalSeconds

◆ LowThreshold

◆ HighThreshold

The following locations are monitored for low disk space:

◆ Archive location

◆ Index location

◆ Message Center

◆ SourceOne work temp folder

◆ SourceOne index temp folder

◆ Log location

Based on the threshold level (high or low), the service model is divided into three states:

◆ Healthy

◆ Warning

◆ Error

Self-adapt the system 103


Recovery TasksThe following table lists the conditions and states for which recovery tasks occur.

The following table lists the self-adapting action variables currently supported.

Note: Monitor does not support all of the self-adapting actions. Some types of monitors only support some of them.

Table 25 Recovery task per State

Condition State Recovery Task

> High Threshold Healthy Resume if needed

< High Threshold && > Low Threshold Warning Send Admin email and alert

< Low Threshold Error Send Admin email and alertThrottle down activities/remove Server role/set worker to off-duty

Table 26 Supported self-adapting actions variables

Action ID Define const variable Description

0 ACTION_NONE No action

1 ACTION_RESUME_ACTIVITY Resume activity

2 ACTION_STOP_ACTIVITY_EXCEPT_JOURNAL Stop activity except the journal

3 ACTION_STOP_ACTIVITY_ALL Stop all activity

4 ACTION_UPDATE_ARCHIVE_ROLE Update the Archive role

5 ACTION_UPDATE_INDEX_ROLE Update the index role

6 ACTION_UPDATE_WORKER_STATE Update the worke state (available or unavailable)



Connectivity IssuesThe administrator is alerted if there is no connectivity to data sources based on the configuration from which it is archived. The data sources include the following:

◆ Microsoft Exchange

◆ File Servers

◆ SharePoint servers

In addition to data sources, the administrator is alerted if there is no connectivity or communication between components. Components include the front end and Native Archive, database connectivity, and file shares access. After a number of retries, the administrator is notified of the connectivity problem.

The following types of connectivity are monitored:

◆ Connectivity from Worker to Data Source:

• To the Mail Server: Microsoft Exchange

• To the SharePoint server

• To the Files server

◆ Connectivity from Worker to Native Archive

◆ Connectivity from SourceOne servers to Database:

• From Master

• From Worker

• From the Native Archive server

• From the Console

◆ Connectivity to share folders:

• From Worker to the Job Log location

• From the Native Archive server to the Archive location

• From the Native Archive server to the Index location

• From the Native Archive server to the Message Center

Self-adapt the system 105


SourceOne file version“File State View” on page 86 provides information on the SourceOne file version.

Configure variablesConfigure the variables in the override page of SCOM for every type of monitor (Low Disk Space, and Connectivity Issues):

1. In the Authoring tab, select the required ManagementPack object (Monitors, Object Discovery, rule).

2. Right click the selected monitor, and select Override > Override the Monitor > For all objects of class: Native Archive.

A data collection script measures the amount of free space for each location.

3. In the Override window, click the checkbox of the variable to modify:

• Interval in seconds

• Script Arguments:

– Low Disk Space: threshold and action values– Connectivity Issues: try-number and retry-interval

The following table lists the default threshold and action values for each Low Disk Monitor.

Table 27 The default threshold values and self-profiling actions for the status of each Low Disk Monitor (1 of 2)

Monitor

Default Value Supported Actions

(Action ID)--threshold critical --threshold warning --action critical --action warning

Index Work Dir free space monitor

1 5 5 0 5

Work Dir of archiving free space monitor

1 5 4 0 4

Index Location free space monitor

1 5 3 2 3, 2

Archive Location free space monito

1 5 3 2 3, 2



Message Center free space monitor

1 5 3 2 3, 2

Job Log location free space monitor

1 5 6 0 6

Work temp dir of workers free space monitor

1 5 6 0 6

Table 27 The default threshold values and self-profiling actions for the status of each Low Disk Monitor (2 of 2)

Monitor

Default Value Supported Actions

(Action ID)--threshold critical --threshold warning --action critical --action warning