Integrating with Unitrends Emails

James Burke
James Burke
  • Updated

Backup Radar supports two Unitrends reports through email reporting:

  • Schedule Report, listed under Email reports, for local backup activity.

  • Backup Copies - Past 24 Hours report, listed under Backup Copy reports, for offsite copy activity.

Configure both reports through Unitrends appliance email reporting and send them to your Backup Radar mailbox to monitor local backups and their offsite copies. Backup Radar parses the report fields to determine the device name, job name, and result status.

Note: This article captures third-party steps and/or an interface that may have since been updated.

Who can use this feature?

  • Unitrends administrators who can configure appliance email reporting.

  • Backup Radar administrators who can access the Backup Radar mailbox and review incoming results.

What you’ll need

  • Your Backup Radar mailbox address.

  • Administrator access to the Unitrends appliance.

  • Your Unitrends SMTP server details, if SMTP email reporting is not already configured.

Configure Unitrends email reporting

Unitrends can email reports automatically to designated recipients. To send both supported reports to Backup Radar:

  1. In Unitrends, navigate to Configure > Appliances.

  2. Select the appliance that generates the reports and click Edit.

  3. Open the Email tab and enable email reporting.

  4. Enter or confirm the SMTP server details.

  5. Add your Backup Radar mailbox as a report recipient.

  6. Select the Jobs and Appliance report types.

    • Jobs sends the Schedule Report.

      • Appliance sends the Backup Copies - Past 24 Hours report.

  7. Save the email reporting configuration.

For more details about generating and emailing reports, see Working with reports. For an overview of Unitrends report categories, see Types of reports.

Schedule Report

The Schedule Report is generated daily and summarizes scheduled backup jobs from the preceding 24 hours. Unitrends sends this report when you select the Jobs report type for email reporting. For more details, see Schedule report.

How Backup Radar parses the Schedule Report

Backup Radar reads each schedule event and its backup rows. It uses the following fields:

Unitrends field

Backup Radar field

Parsing behavior

Client Name

Device Name

For client-based backup rows, Backup Radar uses the value in the Client Name column.

Virtual Machine

Device Name

For virtual machine backup rows, Backup Radar uses the value in the Virtual Machine column.

Description and Application name

Job Name / Description

Backup Radar combines the Description and Application name in this format: Description - Application name.

Status

Result status

Backup Radar uses the status reported for the backup row.

For example, a Schedule Report row with these values:

  • Client Name: Example-Client

  • Description: Example File Backup

  • Application name: file-level

  • Status: Successful

appears in Backup Radar as:

  • Device Name: Example-Client

  • Job Name / Description: Example File Backup - file-level

  • Result: Successful

The same logic applies to virtual machine rows. Backup Radar uses the individual Virtual Machine value as the Device Name and combines the schedule Description with the Application name for the Job Name / Description.

Figure 1: Generic Schedule Report with device and job values replaced for documentation.

Figure 2: Generic Backup Radar result created from a Schedule Report row.

Backup Copies - Past 24 Hours report

The Backup Copies - Past 24 Hours report represents an offsite copy of a local backup. It does not represent the local backup shown in the Schedule Report. The offsite copy can target a cloud node or another upstream appliance.

Unitrends lists this report under Backup Copy reports. Backup Radar receives it when you select the Appliance report type for email reporting.

How Backup Radar parses the Backup Copies - Past 24 Hours report

Backup Radar reads the identifier in the report header and the completion status for the activity.

Backup Copies - Past 24 Hours report value

Backup Radar field

Parsing behavior

Text before the first pipe (|) in the header identifier

Device Name

Backup Radar uses the initial identifier as the Device Name.

Complete header identifier

Job Name / Description

Backup Radar prefixes the identifier with Offsite Copy - .

Completed

Result status

A completed offsite copy is recorded as a completed successful result.

For example, if the report header contains:

Recovery-Example | Appliance-Example | Source-Device --> Target-Node

Backup Radar creates or updates the offsite copy result as:

  • Device Name: Recovery-Example

  • Job Name / Description: Offsite Copy - Recovery-Example | Appliance-Example | Source-Device --> Target-Node

  • Result: Completed

Figure 3: Generic Backup Copies - Past 24 Hours report with device and job values replaced for documentation.

Figure 4: Generic Backup Radar record created from a Backup Copies - Past 24 Hours report.

Because this report represents offsite activity, do not expect it to be parsed as the local backup job from the Schedule Report. When both reports are configured, the Schedule Report represents the local backup and the Backup Copies - Past 24 Hours report represents the corresponding offsite copy.

Verify report delivery and parsing

Use these checks when results do not appear as expected in Backup Radar:

  1. Confirm that Unitrends sends the Jobs report type for the Schedule Report.

  2. Confirm that Unitrends sends the Appliance report type for the Backup Copies - Past 24 Hours report.

  3. Confirm that both emails arrive in the Backup Radar mailbox.

  4. In Backup Radar, navigate to Integration -> Mailboxes and confirm that the emails were received.

  5. If an email was received but no result was created, confirm that the email body is a Schedule Report or Backup Copies - Past 24 Hours report. Other Unitrends email reports use different formats and are not covered by this parsing behavior.

  6. If the emails do not arrive, verify the Unitrends sender domain and SMTP relay configuration. An invalid appliance domain can cause email rejection or spam filtering.

✉️ Any questions? Reach out to our friendly, neighborhood support team by submitting a support ticket.
🎙️ Interested in attending a live Q&A session with our Product Adoption team? Sign up to attend Backup Radar Office Hours and get real-time answers to your questions.

Related to

Was this article helpful?

Yes! No