Return
-
Title
Remote last backup date is not populated in SQL Server where databases are backed up by third party software -
Description
The Remote Last Backup Date column in the SQL Server databases panel is null or empty even though the databases are being backed up by third party backup software. -
Cause
remote_last_backup_date is the date on the partner database where this is applicable. -
Resolution
The logic of the databases collection for remote backups is as follows.
Find out if the other instance is monitored
1). The agent determines- if the instance is mirrored (databases/is_mirrored=1) or has log shipping (databases/is_log_shipping=1) configured
- and the current databases/last_backup_time is NULL
- then the agent confirms that an agent is monitoring the instance specified on databases/hadr_location.
- last_backup_time should be "Unknown" and a tooltip will indicate that "Database has a mirror configured for log shipping but there is no Foglight agent that monitors the partner instance. Click on the hadr_location instance to add the agent"
4). If the database is mirrored or has log_shipping then,- check the topology of the hadr_location for the last_backup_date and provide this in "Remote Last Backup Date" column.
- If there is no backup, display "no backup found"
- specify the backup date as "No preferred replica"
- when the database is_always_on, the location should be the hadr_location which is the availability group name.