October 6, 2010 at 11:20 am
I have two servers (with 3 instances each) on which we recently performed an in-place upgrade from SQL 2005 to SQL 2008.
Each instance has a maintenance plan that performs a full backup of user databases on Sundays, and differential backups Monday-Saturday.
The full backups on Sundays are working fine, as are the differential backups Monday and Tues.
However, starting on Wednesday, various instances will fail on the differential backups.
The Maintenance Plan report files show:
Failed:(-1073548784) Executing the query "BACKUP DATABASE [MyDB] TO DISK = N'D:\\Backups\\CC..." failed with the following error: "Cannot perform a differential backup for database "MyDB", because a current database backup does not exist. Perform a full database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option.
This is acting as if the databases don't have a full backup, but they are there. I also checked the maintenance plans to ensure that the full backups aren't set to expire (they weren't).
Any ideas of what is causing this, or how to correct it?
Thanks,
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
October 6, 2010 at 11:35 am
October 6, 2010 at 1:26 pm
Is NTBackup scheduled to run on Wednesday? This can be a possibility.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 6, 2010 at 1:28 pm
or some job is switching the RECOVERY model to SIMPLE and back to FULL?
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 7, 2010 at 1:46 am
Adiga (10/6/2010)
or some job is switching the RECOVERY model to SIMPLE and back to FULL?
Differential backup can work with all recovery models, so I don't think that switching recovery model, should invalidate the backup. The only thing that I can think about is that the database was dropped and created (or reattached) since the last full backup. Can you check the database's creation date?
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
October 7, 2010 at 6:51 am
Okay, I am seeing the IO frozen/thawed messages in the sql log, so it does appear that NT backup is the culprit. Time to work with the SAs to fix this.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply