Database suspect during backup but not actually in a suspect state

Question

Database suspect during backup but not actually in a suspect state

Y.B.

SSChampion

Points: 11642
More actions
March 11, 2019 at 11:10 am

#416856

Hi folks,
This morning I noticed one of my DIFF backups jobs failed. (I'm using Ola's scripts) Problem is when I checked the Command Log table none of the actual backups in the job had actually failed. So then I went to the output file and all the separate job outcomes were successful. However, I did spot an error that was raised that said a DB was in a suspect state. I checked the DB in question and it's online and perfectly accessible. I've also run a checkdb against it and no issues were found. So, I decided to run the job again to make sure it wasn't an anomaly but the exact same thing happened. Backups are ok, suspect database error but the DB is actually fine.
I'm stumped on this one and I'm hoping for some advice on what to check for next?
FYI - the database is woefully behind on patches...update is in the works.
Thanks,
SELECT quote FROM brain WHERE original = 1
0 rows returned

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Sue_H SSC Guru Points: 90860 More actions · Answer 1

Y.B. - Monday, March 11, 2019 11:10 AM
Hi folks,
This morning I noticed one of my DIFF backups jobs failed. (I'm using Ola's scripts) Problem is when I checked the Command Log table none of the actual backups in the job had actually failed. So then I went to the output file and all the separate job outcomes were successful. However, I did spot an error that was raised that said a DB was in a suspect state. I checked the DB in question and it's online and perfectly accessible. I've also run a checkdb against it and no issues were found. So, I decided to run the job again to make sure it wasn't an anomaly but the exact same thing happened. Backups are ok, suspect database error but the DB is actually fine.
I'm stumped on this one and I'm hoping for some advice on what to check for next?
FYI - the database is woefully behind on patches...update is in the works.
Thanks,

Did you check if you have any rows in the suspect_pages table in msdb?

Sue

Y.B. SSChampion Points: 11642 More actions · Answer 2

Sue_H - Tuesday, March 12, 2019 3:02 PM
Y.B. - Monday, March 11, 2019 11:10 AM
Hi folks,
This morning I noticed one of my DIFF backups jobs failed. (I'm using Ola's scripts) Problem is when I checked the Command Log table none of the actual backups in the job had actually failed. So then I went to the output file and all the separate job outcomes were successful. However, I did spot an error that was raised that said a DB was in a suspect state. I checked the DB in question and it's online and perfectly accessible. I've also run a checkdb against it and no issues were found. So, I decided to run the job again to make sure it wasn't an anomaly but the exact same thing happened. Backups are ok, suspect database error but the DB is actually fine.
I'm stumped on this one and I'm hoping for some advice on what to check for next?
FYI - the database is woefully behind on patches...update is in the works.
Thanks,
Did you check if you have any rows in the suspect_pages table in msdb?
Sue

That was a great idea, thanks. Unfortunately, there were no rows in the table to indicate suspect pages. Very strange indeed. That being said the last 3 runs of my backup had no issues. I hope it's just a glitch but I'd rather be proactive.

SELECT quote FROM brain WHERE original = 1
0 rows returned

Sue_H SSC Guru Points: 90860 More actions · Answer 3

Y.B. - Wednesday, March 13, 2019 6:42 AM
Sue_H - Tuesday, March 12, 2019 3:02 PM
Y.B. - Monday, March 11, 2019 11:10 AM
Hi folks,
This morning I noticed one of my DIFF backups jobs failed. (I'm using Ola's scripts) Problem is when I checked the Command Log table none of the actual backups in the job had actually failed. So then I went to the output file and all the separate job outcomes were successful. However, I did spot an error that was raised that said a DB was in a suspect state. I checked the DB in question and it's online and perfectly accessible. I've also run a checkdb against it and no issues were found. So, I decided to run the job again to make sure it wasn't an anomaly but the exact same thing happened. Backups are ok, suspect database error but the DB is actually fine.
I'm stumped on this one and I'm hoping for some advice on what to check for next?
FYI - the database is woefully behind on patches...update is in the works.
Thanks,
Did you check if you have any rows in the suspect_pages table in msdb?
Sue
That was a great idea, thanks. Unfortunately, there were no rows in the table to indicate suspect pages. Very strange indeed. That being said the last 3 runs of my backup had no issues. I hope it's just a glitch but I'd rather be proactive.

Hopefully but you may want to make sure you have alerts setup for errors 823, 824, 825 just in case. Here is an interesting read on 825 if you haven't run across it yet:
A little-known sign of impending doom: error 825

Sue