Previous Topic: Configure Agent Behavior for Databases Ineligible for BackupNext Topic: Microsoft SQL Server Disaster Recovery


Additional Database Status Considerations

Database Status -- Mirror

When the entire instance is selected, Mirror databases do not appear on the database list, and are ignored. For a Mirror database to be explicitly selected for backup, it would have been selected while it was the Principal (Active) member of the Mirroring partnership, and entered the Mirror state due to a subsequent fail-over.

Database Status -- Suspect

When a database using the Full or Bulk-Logged Recovery Model is in the Suspect state, the Agent automatically attempts to perform a Transaction Log Backup with No Truncation. If this matches the backup options selected, then the results of this backup are the only indicator. If a different backup method is selected, a Warning is posted that a Transaction Log Backup with No Truncation is being attempted instead of using the selected options.

Database Status -- Missing

Because the database list is enumerated dynamically when the entire instance is selected, the Agent for Microsoft SQL Server has no knowledge of databases that have been removed from the SQL Server instance.