sp_check: SQL Server Database Checks

Split backup chain

What's the issue?

One or more databases appear to have a split backup chain, meaning backup files are being written to multiple locations.

Why is this a problem?

A split backup chain complicates the restoring process, since you will have to figure out where the most recent backup files were written. Additionally, a split backup chain could be due to unknown scheduled backups or ad hoc backups that were written without using the COPY_ONLY option, which would not affect the backup chain.

What should you do about this?

Review the backup locations using @Mode = 3 in sp_CheckBackup to see the different locations where backup files have been written. You may also find it helpful to use @Mode=2 in sp_CheckBackup to see when the different kinds of backups have been occurring and what login was used to create the backups.

What do the Vulnerability Levels mean?

0 - Information only. This is stuff you should know about your instances like version and service account used, but if you don't know it…well, now you do.

1 - High vulnerability requiring action. These are the issues that could most likely lead to your company being front page news for all the wrong reasons. If your instances have any results at this level then we recommend cancelling that 3-martini lunch and instead huddling with your team to figure out when to address these issues.

2 - High vulnerability to review. These include settings and assigned permissions you should review soon, if not immediately. These findings may not necessarily indicate a clear vulnerability, but we've found unexpected vulnerabilities in these categories at many, many clients.

3 - Potential vulnerability to review. These are configurations or assigned permissions you may be using that could lead to problems for users. Or maybe they're just required for your applications. Either way, we recommend reviewing these to make sure these are correct.

4 – Low vulnerability with recommended action. These are typically security inconsistencies that should be addressed. They aren't likely to cause problems, but you should clean up the mess.