Pre-Installation Setup for EMC Data Domain Backup > Adding an EMC Data Domain Backup Data Collector Policy
  
Version 10.2.00
Adding 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. See Adding/Editing Data Collectors. For specific prerequisites and supported configurations for a specific vendor, see the APTARE StorageConsole Certified Configurations Guide.
• After adding the policy: For some policies, collections can be run on-demand using the Run button on the Collectors page action bar. The Run 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 and see for details about Run.
To add the policy
1. Select Admin > Data Collection > Collectors. The list of currently configured Portal Data Collectors is displayed.
2. Search for a Collector if required. See To Add a Data Collector.
3. Select a Data Collector from the list.
4. Click Add Policy, and then select the vendor-specific entry in the menu.
5. When selecting the File-Level Compression probe, additional configuration is required, as shown below.
a. Select a Data Domain Server.
b. Select the File-Level Compression probe.
c. Click Configure. See also, File-Level Compression Probe and Configure a Data Domain Server for File-Level Compression Collection.
6. Enter or select the parameters. Mandatory parameters are denoted by an asterisk (*):
Field
Description
Sample Value
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 select Admin > Domains > Domains.
yourdomain
Data Domain Servers*
When you check Active for a server shown in the list, a dialog window prompts for the SSH credentials. Alternatively, select a server and click Configure.
In order for Data Domain Servers to be listed in the policy window, they must have been created via the Inventory and configured with a Backup Type of Data Domain Server. See Add EMC Data Domain Servers.
 
SSH User ID*
The command-line interface (CLI) via SSH is used to gather Data Domain system data. This requires a view-only Data Domain User ID that must be a member of the Data Domain system Admin group. This User ID must be the same for all addresses listed in the System Addresses entry field for the Data Domain systems.
Administrator
Password
The password associated with the User ID.
Pwd1
Configure
Select a Data Domain server and click Configure to enter the SSH credentials that will be used to access the server.
 
Export
Click Export 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.
Aggregated global and local compression rates for all NetBackup backup images are collected for all MTrees that are connected to the Active Data Domain servers via DDBOOST and where the NetBackup Data Collector is active and has successfully completed an initial data collection.
Warning: Choosing to exclude collection with an empty MTree list may cause collection to take several hours to complete.
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.
 
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 Run functionality available in Admin>Data Collection>Collectors. 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. See for details.
 
7. Click OK to save the policy.
8. On the Data Collector server, add entries to the local hosts file, both resolving to the Portal server IP address.