Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Cannot perform a differential backup for database "ReportServer" Expand / Collapse
Author
Message
Posted Thursday, February 14, 2013 12:19 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Today @ 8:04 AM
Points: 41, Visits: 166
Good day,

Please assist Im getting the error below:

"Cannot perform a differential backup for database "ReportServer"
because a current database backup does not exist.
Perform a full database backup by reissuing BACKUP DATABASE omitting the WITH DIFFERENTIAL option.
BACKUP DATABASE is terminating abnormally."

I have created a package for diff and full backups. My full runs once a week and diff runs daily as SQL Server Agent jobs. When I run the diff job manually it runs successfully and in the PoC it also runs successfully. I do have a full ReportServer backup. The log suggests that the full database backup does not exist but it does. I have created backup folders for diff and full but in the save drive.

I'm not sure as to what else to check. Please assist.

Thanks.
Post #1419838
Posted Thursday, February 14, 2013 12:20 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Today @ 8:04 AM
Points: 41, Visits: 166
I'm using SQL Server 2008.
Post #1419839
Posted Thursday, February 14, 2013 12:38 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, May 30, 2014 8:15 AM
Points: 1,056, Visits: 2,687
The error clearly says full backup is not availale.

check any log truncation or shrink happened before the backup starts.

try doing the fullbackup and then differenctial in sequence again.



Regards
Durai Nagarajan
Post #1419842
Posted Thursday, February 14, 2013 2:11 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Today @ 8:04 AM
Points: 41, Visits: 166
yesterday I changed the schedule so they can run sequentially full first then diff and it executed successfully using sql server agent. I then changed the times back to original ones and the diff failed. I do have a full backup.
Post #1419880
Posted Thursday, February 14, 2013 2:21 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 12:11 PM
Points: 42,470, Visits: 35,541
durai nagarajan (2/14/2013)
check any log truncation or shrink happened before the backup starts.


Neither of those will affect a differential backup base.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1419883
Posted Thursday, February 14, 2013 2:22 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 12:11 PM
Points: 42,470, Visits: 35,541
You have some third party tool backing up the databases as well as the native backups. My guess would be backupexec. The native and the 3rd part backups are interfering with each other causing this error.

Ensure that you have native backups or 3rd party database backups, not a mix of both. Either will work fine, a mix won't.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1419885
Posted Thursday, February 14, 2013 2:44 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Today @ 8:04 AM
Points: 41, Visits: 166
Im not using any 3rd party. I created packages using SSIS 2008 tested successfully in dev, deployed to file system, this was running for 2 weeks every day without any issues, no changes have been made on the SQL box. All other jobs are running without any errors

I have ran out of ideas, therefore, I have redeployed to SQL Server and modified my job steps to point to SQL Server instead of File System am now waiting for the job to execute.
Post #1419898
Posted Thursday, February 14, 2013 2:58 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 12:11 PM
Points: 42,470, Visits: 35,541
Check the error log, check the backup history tables, you have some 3rd party tool backing up your databases. Probably something one of your server admins put in place thinking it's a great idea.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1419904
Posted Thursday, February 14, 2013 3:01 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, May 30, 2014 8:15 AM
Points: 1,056, Visits: 2,687
GilaMonster (2/14/2013)
durai nagarajan (2/14/2013)
check any log truncation or shrink happened before the backup starts.


Neither of those will affect a differential backup base.


thanks that a good catch


Regards
Durai Nagarajan
Post #1419909
Posted Thursday, February 14, 2013 9:46 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Saturday, July 26, 2014 8:10 PM
Points: 2,826, Visits: 8,463
GilaMonster (2/14/2013)
You have some third party tool backing up the databases as well as the native backups. My guess would be backupexec. The native and the 3rd part backups are interfering with each other causing this error.

Ensure that you have native backups or 3rd party database backups, not a mix of both. Either will work fine, a mix won't.


I'm pretty sure that at a previous place we had a huge database FULL backup directly to tape with BackupExec, and on occasion a native DIFF backup to disk without problems. Why would 2 different methods of full backup cause a problem ?



Post #1420160
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse