When Backup Radar receives a backup result from an email or API integration, it compares the result with existing backup records. Backup Radar uses a set of unique identifiers to decide whether to add the result to an existing backup or create a new backup record.

Understanding these identifiers can help you prevent duplicate backups and keep your backup data organized.

What are unique identifiers?

Unique identifiers are data points that Backup Radar uses to distinguish one backup from another. Together, these values act as a fingerprint for a backup.

When Backup Radar receives a new result, it compares the values in the result with the identifiers on existing backups. If the values match, Backup Radar ingests the result into the existing backup. If a value changes, Backup Radar can treat the result as a new backup.

Unique identifiers used by Backup Radar

Backup Radar uses the following values to identify a backup:

• Device Name: The name of the device associated with the backup.

• Job Name: The name of the backup job.

• Backup Method: The method used to receive or process the backup result.

• Vendor: The backup vendor that reports the result.

• Application: The backup application that reports the result.

• Source: The source of the result, such as an email or API integration.

• Backup Client ID: The client identifier provided by the backup application. This value can represent the company name received in an email or through an API integration. For email notifications that do not include client data, see Using Plus Addressing.

What happens when an identifier changes?

If one or more unique identifiers change in the information Backup Radar receives, Backup Radar can create a new backup record instead of adding the result to the existing backup.

A new backup record can be created when a unique identifier changes in your backup vendor’s system or in the information the vendor sends to Backup Radar.

For example, a new backup record can be created when you:

• Change a job name.

• Change a company name that is sent as the Backup Client ID.

• Rename a backup device.

• Change the destination for an off-site backup job.

• Transition from Veeam email-based reporting to the Veeam Service Provider Console (VSPC) API integration, or switch back from the API integration to email-based reporting.

The original backup stops receiving results, while the new backup record receives future results. This can make the two records appear as duplicate backups.

How to clean up duplicate backups

When a changed identifier creates a duplicate backup, you have two options.

Merge the backups

Merge the old backup into the new active backup when you want to preserve the backup history in one record. Merging combines the records and is permanent, so verify the backup details before you continue.

For more details, see Merging your Backups.

Retire or delete the old backup

Retire the old backup when it no longer needs active monitoring and you want to preserve its history. Retired backups no longer appear in active views, and incoming results are muted.

Delete the old backup only when you want to permanently remove its data. Deleting a backup removes its historical data after the nightly purge and cannot be undone.

For more details, see Retiring or Deleting Your Backups.