Add an EMC data domain backup Data Collector policy
Before adding the policy: A Data Collector must exist in the Portal, to which you will add Data Collector Policies.
For specific prerequisites and supported configurations for a specific vendor, see the Certified Configurations Guide.
After adding the policy: For some policies, collections can be run on-demand using the button on the Collector Administration page action bar. The button is only displayed if the policy vendor is supported.
On-demand collection allows you to select which probes and devices to run collection against. This action collects data the same as a scheduled run, plus logging information for troubleshooting purposes. For probe descriptions, refer to the policy.
To add an EMC data domain backup Data Collector policy
- Select Admin > Data Collection > Collector Administration. Currently configured Portal Data Collectors are displayed.
- Search for a Collector if required.
- Select a Data Collector from the list.
- Click Add Policy, and then select the vendor-specific entry in the menu.
- Optionally, add an EMC Data Domain server from the policy screen. This action can also be completed in the Inventory.
See Adding/Configuring an EMC data domain server within the Data Collector policy window.
- When selecting the File-Level Compression probe, additional configuration is required, as follows:
Select a Data Domain Server.
Select the File-Level Compression probe.
Click Configure.
See Configure a data domain server for file-level compression collection.
- Enter or select the parameters. Mandatory parameters are denoted by an asterisk (*).
See See Table: Policy Parameters.
Table: Policy Parameters
| Field | Description |
|---|---|
|
Collector Domain |
The domain of the collector to which the collector backup policy is being added. This is a read-only field. By default, the domain for a new policy will be the same as the domain for the collector. This field is set when you add a collector. |
|
Policy Domain |
The Collector Domain is the domain that was supplied during the Data Collector installation process. The Policy Domain is the domain of the policy that is being configured for the Data Collector. The Policy Domain must be set to the same value as the Collector Domain. The domain identifies the top level of your host group hierarchy. All newly discovered hosts are added to the root host group associated with the Policy Domain. Typically, only one Policy Domain will be available in the drop-down list. If you are a Managed Services Provider, each of your customers will have a unique domain with its own host group hierarchy. To find your Domain name, click your login name and select from the menu. Your Domain name is displayed in your profile settings. Example: yourdomain |
|
Data Domain Servers* |
When you check for a server shown in the list, a dialog window prompts for the SSH credentials. Alternatively, select a server and click . You must indicate which servers are active. You must configure each server with a of . |
|
Add |
Click to add a Data Domain servers. The added servers are also displayed under . See Adding/Configuring an EMC data domain server within the Data Collector policy window. Note: If the hosts already exists, IT Analytics displays a confirmation dialog box to update the Host Details (including the Host Type). Click Ok to update Host details / Host Type. |
|
Configure |
Select a Data Domain server and click to enter the SSH credentials that will be used to access the server. This allows provides access to setting up file-level compression. Refer to the following for additional setup information. See Configure a data domain server for file-level compression collection. |
|
Export |
Click to retrieve a list of all the Data Domain servers in a comma-separated values file. |
|
Inventory Probe |
Inventory details such as system, disk, tape, and VTL details are collected by default. Click the clock icon to create a schedule. You can schedule the collection frequency by minute, hour, day, week and month. Advanced use of native CRON strings is also available. Note: Explicit schedules set for a Collector policy are relative to the time on the Collector server. Schedules with frequencies are relative to the time that the Data Collector was restarted. |
|
VTL Performance |
Data associated with the performance of the Data Domain system virtual tape libraries (VTL) is collected by default. Click the clock icon to create a schedule. You can schedule the collection frequency by minute, hour, day, week and month. Advanced use of native CRON strings is also available. |
|
File-Level Compression Probe |
When this probe is selected, MTrees can be entered into the File-Level Compression list configured for a Data Domain Server. The Data Domain Servers will then display an Include/Exclude column, with negative numbers indicating MTrees are excluded and positive numbers indicating MTrees are included. Hover your mouse over the Incl/Excl column to view the MTrees.If the column displays +0, it indicates no Mtrees have been included in the collection, and -0 indicates no Mtrees have been excluded, so all Mtrees will be collected from. For additional setup information refer to the following section. This section also contains information about RMAN and NetBackup jobs. See Configure a data domain server for file-level compression collection. |
|
Notes |
Enter or edit notes for your data collector policy. The maximum number of characters is 1024. Policy notes are retained along with the policy information for the specific vendor and displayed on the Collector Administration page as a column making them searchable as well. |
|
Test Connection |
Test Connection initiates a Data Collector process that attempts to connect to the subsystem using the IP addresses and credentials supplied in the policy. This validation process returns either a success message or a list of specific connection errors. Test Connection requires that Agent Services are running. Several factors affect the response time of the validation request, causing some requests to take longer than others. For example, there could be a delay when connecting to the subsystem. Likewise, there could be a delay when getting the response, due to other processing threads running on the Data Collector. You can also test the collection of data using the functionality available in . This On-Demand data collection run initiates a high-level check of the installation at the individual policy level, including a check for the domain, host group, URL, Data Collector policy and database connectivity. You can also select individual probes and servers to test the collection run. |