Adding a policy
Validation before adding the policy
A Data Collector must exist in the Portal for the Data Collector Policies.
For specific prerequisites and supported configurations, see the Certified Configurations Guide.
After adding the policy
For some policies, the collections can be run on-demand using the Run at Collector Administration page action bar, provided that if the policy vendor is supported. On-demand collection lets you 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.
Note:
Refer to the policy for probe descriptions.
Navigate to Admin > Data Collection > Collector Administration. Currently configured Portal Data Collectors are displayed.
Search for a Collector if required.
Select the Data Collector from the list.
Click , and then select the vendor-specific entry in the menu.
Specify the parameters. The mandatory parameters are denoted by an asterisk(*) symbol.
Field
Description
Collector Domain
The domain of the collector to which the collector backup policy is added. The Collector Domain is a read-only field.
By default, the domain for a new policy is 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 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 which is 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 should have a unique domain with its own host group hierarchy.
To find your Domain name, click your logon name and select My Profile from the menu. Your Domain name is displayed in your profile settings.
Example: yourdomain
Management Server Addresses*
One or more NEC Storage HS (HYDRAstor) Floating IP addresses or host names to probe. Comma-separated addresses are supported.
For example 192.168.1.10, myhost
Username*
Administrator username for the NEC Storage HS (HYDRAstor).
Password*
Administrator password for the NEC Storage HS (HYDRAstor).
Array Details Probe
Array details such as system, file system, user 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.
If NEC Storage HS (HYDRAstor) has no data (Data Reduction ratio is N/A), NASFileServer operation and SystemCapacity operation fail.
SystemCapacity operation can collect data for "data and metadata" and "parity", but not for "data" and "parity and metadata".
Note:
The explicit schedules that are 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.
Array Performance
The data that is associated with the performance of the NEC Storage HS (HYDRAstor) system to be collected. 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-System capacity detail will be collected once a day.
Notes
Specify 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 the credentials 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 can be a delayed connection to the subsystem. Likewise, there can be a delayed 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 initiates a high-level validation of the installation at the individual policy level, including the domain, host group, URL, Data Collector policy, and database connectivity. You can also select individual probes and servers to test the collection run.
Click to save the policy.
On the Data Collector server, add entries to the local hosts file, both resolving to the Portal server IP address.
