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 incorrect or unexpected names |
The report includes a Location column with values that don't match the expected device names |
Duplicate backup entries appearing |
The SLA Domain column isn't selected in the report |
Log backup or log archival results showing No Result |
The Log Task report is not configured, or the SLA Domain column is missing from the report |
Devices displaying incorrect or unexpected names
Problem
Backup Radar's Rubrik parser determines the device name using the following priority:
For certain object types, the parser uses the Object Name column as the device name regardless of whether a Location column is present. These object types are:
vSphere VM
EC2 Instance
Managed Volume
vCD vApp
VmwareVirtualMachine
NutanixVirtualMachine
Azure VM
AHV VM
Hyper-V VM
For all other object types, the parser uses the Location column as the device name if the column is present in the report. If the Location column is not present, the parser falls back to the Object Name column.
This means that if your Rubrik report includes a Location column and your backups use an object type that isn't in the list above, Backup Radar uses the Location value as the device name. If that Location value is irrelevant to your backup — such as "(Empty)", a cluster name, or any other value that doesn't represent the actual device — your devices appear with incorrect names in Backup Radar.
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 for all object types.
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.
Log backup or log archival results showing No Result
Problem
Rubrik previously included log-related task types (Log Backup and Log Archival) in the Protected Task Details report, but has since moved them to a separate Log Task report.
If your log backup or log archival results are showing No Result in Backup Radar — despite completing successfully in Rubrik — the issue is likely one of the following:
The Log Task report has not been created and scheduled to your Backup Radar mailbox.
The Log Task report is being sent, but the SLA Domain column is not included.
Backup Radar's Rubrik parser uses the SLA Domain column to map log task results to existing backup jobs. Without it, the parser cannot associate the incoming results with the correct backups, causing them to show as No Result.
Steps to resolve
In Rubrik Security Cloud, verify whether a Log Task report exists and is scheduled to send to your Backup Radar mailbox. If one does not exist, create it by navigating to Reports, clicking Create Report, and selecting Log Task Report.
Open the Log Task report and verify that the SLA Domain column is selected in the report settings.
Set the time range to Past 24 hours and ensure the report is scheduled to send daily as a .CSV attachment.
Refer to Rubrik's documentation for guidance on modifying report columns, as the exact steps may vary depending on your Rubrik version and configuration.
After the next scheduled report is received, verify in Backup Radar that your log backup and log archival results are now displaying correctly.
With the SLA Domain column included, the parser uses the combination of SLA Domain and Task Type to correctly map results to existing backup jobs.
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!
