Recovery Manager for AD 10.2.2 - User Guide

Health dashboards

In the SCOM Operations console, Recovery Manager for Active Directory (RMAD) components are represented as three health state views (separate for each type of objects) and two multi-level diagrams. There are three types of RMAD objects in these diagrams: Recovery Manager Console instances, Computer Collections existing in the Recovery Manager Console and Computers explicitly or implicitly added to Computer Collections. Each object has properties and health state determined by these properties.

In the multi-level diagrams All Components in Computer Collections and All Recovery Manager Console Instances under Monitoring | Quest Recovery Manager for Active Directory, health of upper-level components depends on the health of lower-level components.

RMAD object properties monitored by RMAD Management Pack

Recovery Manager Console

Regular Management Pack

• TargetComputer Display name of a RMAD console instance

• Version Version of a RMAD console instance

Limited Management Pack

• TargetComputer Display name of a RMAD console instance

• Version Version of a RMAD console instance

Computer Collection

Regular Management Pack

• DisplayName Display name of a computer collection

• ID Computer collection ID

• AgentSideBackupPath Remote storage

• ConsoleSideBackupPath Location of the backup storage on the RMAD Console side

• CollectFEMetaData Indicates what metadata is collected

• HasCollectionItems Indicates whether a computer collection has collection items

Limited Management Pack

• DisplayName Display name of a computer collection

• ID Computer collection ID

• AgentSideBackupPath Remote storage

• ConsoleSideBackupPath Location of the backup storage on the RMAD Console side

• CollectFEMetaData Indicates what metadata is collected

• HasCollectionItems Indicates whether a computer collection has collection items

Computer

Regular Management Pack

• TargetComputer Name of a domain controller

• LastSessionResult Result of the last backup session

• LastSessionDate Time stamp of the last backup session

• BackupExists Indicates whether a backup was created in the last 30 days

Limited Management Pack

• TargetComputer Name of a domain controller

Health checks performed by RMAD Management Pack

Recovery Manager Console

Regular Management Pack

• Checks whether there are computer collection in the RMAD console instance.

Limited Management Pack

• Does not perform any checks.

Computer Collection

Regular Management Pack

• Checks whether a computer collection has collection items.

Limited Management Pack

• Checks whether a computer collection has at least one domain controller.

• There are no alerts about empty collections or collections which have no backups in the last 30 days.

Computer

Regular Management Pack

• Checks whether a backup was created in the last 30 days. If there are no backups, the Management Pack generates the warning message.

-OR-

• Checks the result of the last backup session.

Limited Management Pack

• Does not request any data about completed backups or backup sessions.

• Does not check whether a backup was created in the last 30 days.

Using Management Shell

• About Management Shell

About Management Shell

The Recovery Manager for Active Directory Management Shell, built on Microsoft Windows® PowerShell® technology, provides a command-line interface that enables automation of backup/recovery-related administrative tasks. With this Management Shell, administrators can manage Computer Collections, backup/recovery sessions, compare and start backup/recovery jobs.

The Management Shell command-line tools (cmdlets), like all the Windows® PowerShell® cmdlets, are designed to deal with objects—structured information that is more than just a string of characters appearing on the screen. The cmdlets do not use text as the basis for interaction with the system, but use an object model that is based on the Microsoft .NET platform. In contrast to traditional, text-based commands, the cmdlets do not require the use of text-processing tools to extract specific information. Rather, you can access portions of the data directly by using standard Windows® PowerShell® object manipulation commands.

For a list of all available PowerShell® commands, see the Management Shell Guide supplied with this release of the product.

Collecting diagnostic data for technical support

There may be a situation where technical support requests you to gather and supply diagnostic data from your computer collection. For this purpose, you can use a special tool provided in the Recovery Manager Console. This tool is called Diagnostic Data Collector.

When gathering diagnostic data, the Diagnostic Data Collector collects the following:

• From Recovery Manager Console machine

  • Collects the Recovery Manager Console log

  • Collects the Recovery Manager for Active Directory event logs

  • .db3 database files

  • Recovery Manager for Active Directory configuration files

• From Domain Controller

  • Collects Backup and Restore agent logs

  • Collects system event logs

  • Windows debug logs

  • Runs Microsoft Netdiag, Dcdiag, Nltest, MsInfo32 and Repadmin tools (in diagnostic mode only), and then collects the output provided by these tools. The tools are started by Collectdcdata.cmd and you can modify the list of collected logs.

To gather diagnostic data for your recovery project by using the Diagnostic Data Collector, you need to complete the following steps:

• Step 1: Use Diagnostic Data Collector to automatically gather data. In this step, you use the Diagnostic Data Collector to automatically gather diagnostic data from each domain controller in your recovery project and save the data to the folder you specify. You can perform this step regardless of whether or not a recovery operation is currently running on the recovery project. If this step completes successfully for all domain controllers, Step 2 is not needed.

• Step 2: Gather remaining data manually. You need to perform this step only for those domain controllers from which you could not successfully collect data in Step 1. In Step 2, you copy several files supplied with RMAD to the target domain controller, and then run one of the copied files. As a result, diagnostic data is collected from the domain controller and saved to a new folder created in the location from which you ran the file.

The next sections provide instructions on how to complete each of these steps.