Overview
When backing up Microsoft SQL Server using Druva, you may notice that the master database does not appear in the recovery point viewer on specific dates.
This behavior is expected. It is caused by native Microsoft SQL Server architectural limitations combined with standard backup scheduling, rather than a Druva application error or backup failure. No data loss has occurred.
Microsoft SQL Server Design Behavior
The master database is a vital system database that records all system-level configuration information for a SQL Server instance (including logins, linked servers, and endpoints).
Because of its critical role in instance initialization, Microsoft design dictates specific backup constraints:
✅ Supported: Full Backups
❌ Not Supported: Differential Backups
❌ Not Supported: Transaction Log Backups
⚠️ Note: These limitations are hardcoded into Microsoft SQL Server and are not restrictions imposed by Druva.
Why the Master Database is Missing from Some Recovery Points
If your Druva backup policy is configured to run a Weekly Full backup alongside daily Incremental or Transaction Log backups:
The
masterdatabase is only backed up—and therefore only visible—during Full backup recovery points.Recovery points generated on days utilizing Incremental or Log backups will not display the
masterdatabase because it cannot legally be included in those backup types.
Example Scenario
Consider a server named SQLSERVER1 on the following schedule:
Feb 1 (Full Backup): The
masterdatabase is visible and available for restore.Feb 2–Feb 6 (Incremental / Log Backups): The
masterdatabase is not visible.Next Full Backup: The
masterdatabase becomes visible again.
Conclusion
No Action Required: The backup environment is functioning entirely as designed.
Data Protection: The
masterdatabase is safely secured and compliant with Microsoft-supported backup standards.Restoration: You can successfully restore the
masterdatabase at any time by selecting a recovery point created during a Full backup cycle.