Add a Dell PowerProtect Data Manager Data Collector policy
Before adding the policy: A Data Collector must exist in the Portal, to which you will add the Data Collector policy.
For specific prerequisites and supported configurations for a specific vendor, see the Certified Configurations Guide.
After adding the policy: For some policies, you can run collection on-demand using the Run button on the Collector Administration 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 similar to that of a scheduled run and also collects logging information for troubleshooting purposes. For probe descriptions, refer to the policy.
To add a Dell PowerProtect Data Manager policy:
- Select Admin > Data Collection > Collector Administration. Currently configured Portal Data Collectors are displayed.
- Select a Data collector from the list. Search for a collector if required.
- Click Add Policy and then select Dell PowerProtect Data Manager from the menu.
- Enter the policy parameters based on the description below and click OK to create and save the policy.
Table: Dell PowerProtect Data Manager Data Collector policy
|
Field |
Description |
|---|---|
|
Collector Domain |
The domain of the collector to which the collector backup policy is being added. 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 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 My Profile from the menu. Your Domain name is displayed in your profile settings. |
|
Management Server Addresses* |
Hostname or IP Address of the Dell PowerProtect Data Manager Server. Comma-separated host names are supported. |
|
Port* |
Server port number for REST API communication. The default port number is 8443 for SSL communications. |
|
User ID* |
Specify the user which has administrator role. |
|
Password* |
The password associated with the User ID. |
|
Protection Sources |
This probe focuses on APIs related to the collection of data protection information like System Configuration, Licenses, Node, Disks, Protection Policies, Protection Rules, Policies for disaster recovery and etc. By default, it is collected at 02:00 daily. |
|
Protection Details |
This probe focuses on APIs that help in collecting the information about Assets, Hosts, Activities, etc. By default, it is collected every 15 mintes. |
|
Schedules |
Click the clock icon to create a schedule. By default, it is collected at 02:00 daily and every 15mins daily. Every Minute, Hourly, Daily, Weekly, and Monthly schedules may be created. Advanced use of native CRON strings is also available. Examples of CRON expressions:
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. |
|
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 to be 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 > Collector Administration. 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. |