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 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. |
Avamar Servers* | You can add Avamar servers by clicking Add. You can also import multiple servers using a .CSV file. You can also do this using the Inventory. The Avamar Servers table is populated using any of these methods. The servers added to this table using EMC Avamar Data Collector Policy screen are also displayed under Inventory. You must indicate which servers are active. |
Active | Click Active to indicate the Avamar server(s) to use in the data collection policy. For Avamar, this is the Utility Node. If additional fields must be configured, the Configure Server dialog is automatically displayed when you make your selection. |
Add | Click Add to add an Avamar server type. The added servers are also displayed under Inventory. Note: Data Collector policies can be in place for multiple servers, but a server cannot have multiple policies. |
Configure | Click Configure to revise or add information to the Avamar server you selected. See also Adding/Configuring an Avamar Server within the Data Collector Policy Window. |
Import | Click Import to browse for the CSV file in which you entered the Avamar server configuration details. See also Importing EMC Avamar Server Information. |
Export | Click Export to create and download a comma-separated values (CSV) file containing all the server information listed in the Avamar Servers table. See also Exporting EMC Avamar Server Information. |
Active Probes | Click the clock icon to set a schedule frequency. You can schedule the collection frequency by minute, hour, day, week and month. Advanced use of native CRON strings is also available. You can set a schedule to collect on: • Activity Details • Configuration Changes • Operational Data • Static Data 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. |
Activity Details | Collects backup events/activities from the Avamar server. |
Configuration Changes | Collects datasets, retention policies, schedules, Avamar clients, groups and group members from the Avamar server. |
Operational Data | Collects node utilization, node space, events, DPN statistics, Garbage Collection (GC) status, current Global Storage Area Network (GSAN) status from the Avamar. |
Static Data | Collects the Axion systems, event catalog and plugin catalog entries from the Avamar server. |
Utility Node Details | Collects chassis information for the Avamar Utility Node. |
Field | Description |
Avamar Server Name | The Avamar Utility Node server name. This is displayed on the Inventory page under the Host Name column. This is displayed on the Host Administration dialog under Internal Name. This is a required field. |
Utility Node IP Address | IP address of the Avamar Utility Node. This is management server with which the Data Collector will communicate. This is displayed on the Host Management page under the Primary IP column. This is a required field. |
Software Location | Directory under which all Avamar binaries and configuration files are kept. This field is pre-populated with a default location: /usr/local/avamar. You can edit the field, but it must contain a value. |
Utility Node User ID | The login credentials must have admin or dpn access to the Avamar utility node so that the Data Collector can invoke command-line programs in the /usr/local/avamar/bin directory. |
Password | Password for the utility node username that has root-level access to the Avamar utility node. This is a required field. |
Database Address | Hostname or IP address used to connect to the Avamar Management Console database. This field is pre-populated with a default address: the Utility Node IP address. You can edit the field, but it must contain a value. |
Database User ID | User name to log into the EMC Avamar Management Console database for reporting access. This field is pre-populated with a default Avamar user ID: viewuser. You can edit the field, but it must contain a value. |
Password | Password for credentials required to log into the EMC Avamar management console database for reporting access. This field is pre-populated with a default Avamar user password: viewuser1. You can edit the field, but it must contain a value. |