Overview

LogicMonitor’s CommVault monitoring package leverages the CommVault API to monitor and alert on the status of backup jobs and other health and performance metrics.

Compatibility

As of November 2020, LogicMonitor’s CommVault package is known to be compatible with:

Setup Requirements

Add Resources Into Monitoring

Add your CommVault hosts into monitoring. For more information on adding resources into monitoring, see Adding Devices.

Assign Properties to Resources

The following custom properties must be set on the CommVault resource within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.

Property Value
commvault.user The name of the CommCell Console user. For Active Directory (AD) users, an email address can be used.
commvault.pass Password for the specified user.
commvault.domain (optional) If the user logging in is a domain user, the domain parameter must be set to the domain associated with the user.
commvault.port (optional) Defaults to port 81 if not set.
commvault.data.days (optional) Used in CommVault Subclients, CommVault VMware Subclients, and CommVault VMware Subclient VMs DataSources to set the number of days to look back for backup jobs. This determines which jobs are added into monitoring. Defaults to 1 day if not set.
system.categories “CommVault” (this value will be added automatically by the addCategory_CommVault PropertySource)

Import LogicModules

From the LogicMonitor public repository, import all CommVault LogicModules, which are listed next. If these LogicModules are already present, ensure you have the most recent versions.

Once the LogicModules are imported (assuming all previous setup requirements have been met), data collection will automatically commence.​

LogicModules in Package

LogicMonitor’s package for CommVault consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.

Display Name Type Description
addCategory_CommVault PropertySource Sets appropriate system.categories to set up CommVault monitoring.
CommVault Storage PoolsDataSource Reports size and utilization of CommVault storage pools.
CommVault ServicesDataSource Monitors state of CommVault Services on a Windows host.
CommVault Management ConsoleDataSource Monitors CommVault Management Console web page availability.
CommVault Job BackupsDataSource Monitors the results of the last executed CommVault job for each client or application type.

When setting static datapoint thresholds on the various metrics tracked by this package’s DataSources, LogicMonitor follows CommVault’s best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.

Overview

Dell EMC Avamar is a data backup and recovery system, providing full daily full backups for virtual environments, remote offices, enterprise applications, network-attached storage (NAS) servers, and desktops/laptops. Using LogicMonitor’s EMC Avamar package, you can monitor client backup activities, checkpoints, client dataset configurations, and more.

Setup Requirements

Dependencies

The Management Console Command Line Interface (MCCLI) must be installed on the Collector host in order to connect to the Dell EMC Avamar server. See the
Dell EMC Avamar Management Console Command Line Interface
(MCCLI) Guide
for the system requirements that must be met by the Collector host.

Credentials

LogicMonitor must provide the appropriate credentials in order to successfully access the resource. These credentials must belong to a Dell EMC Avamar system user account (must be a local account, an LDAP account cannot be used) that has been assigned the following minimum permissions:

Role

Description

Read-only The Dell EMC Avamar Administration Guide defines this role as “operator

Once a user account is established, the following properties must be set on the EMC Avamar resource within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.

Property

Value

avamar.user Avamar MCCLI username
avamar.pass Avamar MCCLI password

LogicModules in Package

LogicMonitor’s out-of-the-box package for Dell EMC Avamar contains the following LogicModules. Please ensure that all of these LogicModules are imported into your LogicMonitor platform.

Display Name

Type

Description

addCategory_EMC_Avamar PropertySource Identifies if the host is an EMC Avamar device and sets system category of ‘EMC_Avamar’ and which version of MCCLI is currently installed on the Linux Collector.
Avamar Checkpoints DataSource Checkpoints are system-wide backups that are taken for the purpose of assisting with disaster recovery.
Avamar Client Backups DataSource Monitors all Avamar client backup activities.
Avamar Data Domains DataSource Monitors Data Domain system backup status and performance metrics.
Avamar Datasets DataSource Monitors Avamar client dataset configurations.
Avamar Groups DataSource Monitors Avamar group enabled state.
Avamar Server Garbage Collection DataSource Monitors the server garbage collection status and performance metrics.
Avamar Server Nodes DataSource Monitors individual Avamar node performance metrics.
Avamar Servers DataSource Monitors the Avamar server global services and resource utilization metrics.
Avamar Troubleshooter DataSource Assists in ensuring the Avamar host is configured appropriately.

When setting static datapoint thresholds on the various metrics tracked by this integration package, LogicMonitor follows the technology owner’s best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.

Overview

Veeam Backup & Replication is a proprietary backup app developed by Veeam for virtual environments built on VMware vSphere and Microsoft Hyper-V hypervisors. The software provides backup, restore, and replication functionality for virtual machines, physical servers and workstations as well as cloud-based workloads.

Using LogicMonitor’s Veeam Backup & Replication package, you can monitor the health of this application’s backup, synchronization, and replication operations, as well as the operational state, availability, and maximum task counts of the VMware and Hyper-V proxy hosts.

Compatibility

​​The Veeam Backup & Replication package has been confirmed to be compatible with versions 9.0 – 12.0.0.1420.

Setup Requirements

Follow these steps to set up monitoring for Veeam Backup & Replication.

PowerShell Remoting

If Veeam Backup & Replication is not installed on the Collector host, then PowerShell remoting must be enabled between the Collector host and target resource. To learn more about enabling PowerShell remoting, see PowerShell Tips & Tricks.

See Veeam’s PowerShell Reference for more information on the PowerShell commands supported by Veeam Backup & Replication.

Entering Credentials as Properties

The LogicMonitor Collector must provide the appropriate credentials in order to successfully access the Veeam Backup & Replication resource. These credentials can either represent:

Regardless of which user is chosen, the user must be able to create a remote PowerShell session AND access the Veeam Backup & Replication console.

Note: If Veeam Backup & Replication is installed on the Collector host, a remote PowerShell session will not be initiated and the script will instead run locally—no credentials necessary.

​If credentials need to be provided, one of the following sets of properties must be set on the Veeam Backup & Configuration resource within LogicMonitor. If both sets of properties are provided, precedence is given to the Veeam properties. For more information on setting properties, see Device Properties.

Property Value
veeam.user Veeam username
veeam.pass Veeam password
wmi.user WMI username
wmi.pass WMI password

Considerations: Preventing Instance Merging

If you have hosts with virtual machines in multiple Veeam jobs of the same type (for example, backup, copy, replication), you may end up with merged instances because of duplicate machine names. To improve handling of duplicate names and avoid instance merging, set the veeam.instanceformat property on the Veeam Backup & Replication host to the value “dedupe”.​

LogicModules in Package

​LogicMonitor’s package for Veeam Backup & Replication contains the following LogicModules. Please ensure that all of these LogicModules are imported into your LogicMonitor platform.

Display NameTypeDescription
Veeam HyperV Proxy ServersDataSourceMonitors Veeam Backup HyperV Proxy Server performance metrics.
Veeam Jobs: Backup SessionsDataSourceVeeam Backup Job session metrics.
Veeam Jobs: BackupsDataSourceVeeam Backup Job metrics.
Veeam Jobs: Configuration BackupDataSourceVeeam Configuration Backup Job metrics.
Veeam Jobs: CopyDataSourceMonitors Veeam Copy (File and VM) Job metrics.
Veeam Jobs: Managed Agent BackupsDataSourceModule monitors Veeam Agent backup jobs, containing what data to back up and how, when and where to back up data. This modules monitors both types of Veeam Agent backup jobs; backup jobs and backup policies.
Veeam Jobs: SyncDataSourceMonitors Veeam Sync (File and VM) Job metrics.
Veeam Jobs: Windows AgentDataSourceWindows Agent backup metrics for Veeam Backup and Replication.
Veeam RepositoriesDataSourceVeeam Backup Repositories performance metrics. For Cloud repositories CachedFreeSpace and CachedTotalSpace is -1.
Veeam VMware Proxy ServersDataSourceVeeam Backup VMware Proxy Server performance metrics.
addCategory_Veeam_BackupAndReplication_PowerShellPropertySourceDetermines if the device exposes the Veeam Backup and Recovery PowerShell cmdlet. Requirements: – Veeam admin rights are required to run Veeam PowerShell Backup Snap-in – PowerShell remoting must also be enabled from the collector to the target device. – Collector user must have permissions or credentials must be provided as properties. – Veeam (veeam.user and veeam.pass) – WMI (wmi.user and wmi.pass) – The username cannot contain “veeam.user” or “wmi.user” Precedence is given to the Veeam properties if both are defined.

When setting alert thresholds on the various metrics tracked by this package, LogicMonitor follows the technology owner’s best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning alert thresholds, see Tuning Alert Thresholds for Datapoints.