Introduction

Dell EMC Avamar enables fast, efficient backup and recovery through its integrated variable-length non-redundant technology. Avamar is optimized for fast, daily full backups of physical and virtual environments, NAS servers, enterprise applications, remote offices and desktops/laptops.

OpsRamp integrates with Dell Avamar using SSH and CLI commands.

Prerequisites

  • OpsRamp Classic Gateway 10.0 and above (or) OpsRamp Cluster gateway

  • Ensure that “adapter integrations” add-on is enabled in client configuration. Once enabled you can see Dell Avamar integration under Setup » Integrations » Adapter section

Install the integration

  1. From All Clients, select a client.

  2. Go to Setup > Integrations > Integrations.

  3. From Available Integrations, select Adapter > Dell Avamar. The Install Dell Avamar Integration popup appears.
    Note: Ensure that Adapter addon is enabled at client and partner levels.

  1. Enter the following information:
    a. Name: Name of the integration
    b. Upload Logo: Optional logo for the integration.
    c. GateWay Profiles: Select a gateway management profile to associate with the client.

  2. Click Install. The Integration page displays the installed integration.

Configure the integration

  1. In CONFIGURATION section, click + Add.

  2. On Create Adapter Configuration, enter:

    • Name: Configuration name.
    • IP Address/Host Name: IP address/host name of the target.
    • Alert Configuration: Configure the alert filters, alert severity mappings, etc. based on your requirements.
    Default configuration:
        {"alertFilters":{"alertSeverity":["WARNING","ERROR"]},"alertSeverityMapping":{"ERROR":"Critical","WARNING":"Warning"}}
        
    • Notification Alerts: Select TRUE or FALSE.
      Notes:
      • By default False is selected.
      • If you select TRUE, application will handle Critical/Recovery failure alert notifications for Connectivity, Authentication Exceptions.
  3. In the Credentials section, select Custom and enter the Username and Password.

  4. In the Resource Types & Metrics section, select the metrics you want and configure for availability and alert conditions.

  5. In the Discovery Schedule section, select Recurrence Pattern to add one of the following patterns:

    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly

  6. In the Monitoring Schedule section, configure how frequently the monitoring action should trigger.

  1. Click Save.

The configuration is saved and displayed on the page.

After saving the integration, the Dell Avamar resource is discovered and monitoring is enabled as specified by the configuration profile.

You can perform the actions manually, like Discovery, Monitoring or even Disable the configuration.

The discovered resource is displayed in the Infrastructure page under Server.

View resource metrics

To confirm Dell Avamar monitoring, review the following:

  • Metric graphs: A graph is plotted for each metric that is enabled in the configuration.
  • Alerts: Alerts are generated for metrics that are configured as defined for integration.

Supported metrics

Metric NameMetric Display NameUnitsDescription
avamar_avagent_StatusAvamar Avagent StatusThe avagent status.
Possible values: 0-Other 1-Running
avamar_checkpoint_StatusAvamar Checkpoint StatusThe current status of checkpoint.
Possible values: 0-No response since 24hr or not yet completed 1-Completed
avamar_GC_StatusAvamar GC StatusGarbage collection status.
Possible values: 0-Idle 1-Other
avamar_HFS_StatusAvamar HFS StatusHierarchical File System (HFS) status.
Possible values: 0-Other 1-Completed
avamar_license_StatusAvamar License StatusLicense validity status.
Possible values: 0-InValid 1-Valid
avamar_jobs_waiting_state_CountAvamar Jobs Waiting State CountcountThe total count of jobs in waiting state
avamar_server_StatusAvamar Server StatusThe current status of server.
Possible values: 1-OK 0-Others
avamar_events_activeCountAvamar Active EventscountThe count of active events
avamar_unattended_startup_StatusAvamar Unattended Startup StatusUnattended Startup Status.
Possible values: 0-Disabled 1-Other
avamar_vcenter_connectivity_StatusAvamar Vcenter Connectivity StatusVirtual center Status.
Possible values: 0-Other 1-OK
avamar_powersupply_StatusAvamar Powersupply StatusPower supply status.
Possible values: 0-Other 1-Safe
avamar_long_running_JobsAvamar Long Running JobshTime taken to run or complete the job in hours
avamar_node_StatusAvamar Node StatusNode status.
Possible values: 0-Offline 1-Online
avamar_disk_StatusAvamar Disk StatusDisk status.
Possible values: 0-Offline 1-Online
avamar_filesystem_UtilizationAvamar Filesystem Utilization%Disk file system utilization
avamar_capacity_UsedAvamar Capacity UsedGBThe capacity of the server being used in GB
avamar_capacity_UtilizationAvamar Capacity Used in Percentage%The percentage of the server capacity used
avamar_server_cpu_UtilizationAvamar Server CPU Utilization%The percentage of the server CPU utilization
avamar_protected_BytesAvamar Protected BytesGBThe size of protected Bytes in GB
avamar_node_CountAvamar Node CountcountThe count of Online, Offline, ReadOnly and TimedOut Nodes
avamar_server_service_StatusAvamar Server Service StatusDisplays Avamar server service related status
avamar_load_AverageAvamar Load Average%Average Load on server
avamar_webrestore_diskspace_AvailableAvamar Webrestore Diskspace AvailablecountDisplays the disk space available
avamar_SNMP_sub_agent_StatusAvamar SNMP Sub-Agent StatusDisplays SNMP sub agent status
avamar_cpu_load_UtilizationAvamar CPU Load Utilization%Load on CPU in percentage
avamar_cpu_user_UtilizationAvamar CPU User Utilization%CPU users in percentage
avamar_cpu_system_UtilizationAvamar CPU System Utilization%CPU System in Percentage
avamar_disk_UtilizationAvamar Disk Utilization%Disk Utilization in Percentage
avamar_server_OperationsAvamar Server Operationscounts/sServer operations count per second

Risks, Limitations & Assumptions

  • Application can handle Critical/Recovery failure alert notifications for the below two cases when user enables Notification Alerts in configuration:
    • Connectivity Exception
    • Authentication Exception
  • Application will not send any duplicate/repeat failure alert notification until the already existing critical alert is recovered.
  • Application cannot control monitoring pause/resume actions based on the above alerts.
  • Component level threshold configuration is not possible.
  • Resource level metric threshold customization and frequency setting are not possible.
  • Usability issues in application configuration page while adding/editing.
  • Optional configuration parameters cannot be defined.
  • Application upgrade is manual process without version change.f

References

Dell EMC Avamar MCCLI commands guide: https://dl.dell.com/content/docu91838