If your Rubrik backups are displaying unexpected results in Backup Radar — such as missing device names or duplicate entries — the issue is likely related to your report column settings in the Rubrik console. This article covers common Rubrik integration issues and how to resolve them.
For details on setting up your Rubrik integration, see Integrating with Rubrik Emails.
Who can use this feature?
Users with Admin access in Backup Radar who can also modify report configurations in the Rubrik console.
Note: This article captures third-party steps and/or an interface that may have since been updated.
Use the table below to identify your issue and jump to the relevant section:
Symptom |
Likely cause |
|---|---|
Devices displaying "(Empty)" as the device name |
The report includes a Location column with empty values |
Duplicate backup entries appearing |
The SLA Domain column isn't selected in the report |
Devices displaying "(Empty)" as the device name
Problem
When you import a Rubrik report that includes a Location column, Backup Radar uses the Location value as the device name. If the Location value is "(Empty)", your devices appear with "(Empty)" as the name — even when the report contains a usable Object Name value. Backup Radar doesn't automatically fall back to Object Name when the Location column is present but empty.
Steps to resolve
-
In the Rubrik console, open the report you are importing into Backup Radar and remove the Location column.
Refer to Rubrik's documentation for guidance on modifying report columns, as the exact steps may vary depending on your Rubrik version and configuration.
Re-import the updated report into Backup Radar and verify that your devices now display the correct names.
With the Location column removed, the parser uses the Object Name column as the device name.
Duplicate backup entries from missing SLA Domain column
Problem
Backup Radar's Rubrik parser builds the Job Name from a combination of the SLA Domain and Task Type columns. If the SLA Domain column isn't selected in your Rubrik report settings, the parser uses only the Task Type as the Job Name. This can result in new, unintended backup entries that appear as duplicates.
Steps to resolve
In the Rubrik console, open the report you are importing into Backup Radar.
-
Verify that the SLA Domain column is selected in your report settings.
Refer to Rubrik's documentation for guidance on modifying report columns, as the exact steps may vary depending on your Rubrik version and configuration.
Re-import the updated report into Backup Radar and verify that the duplicate entries no longer appear.
With the SLA Domain column re-selected, the parser uses the full combination of SLA Domain and Task Type as the Job Name, preventing duplicate entries.
Any questions?
If you're still experiencing issues with your Rubrik integration after completing the steps above, or if you have any other questions, reach out to our friendly, neighborhood support team by submitting a support ticket — we're happy to help!
