Post reply

Differential Backup Failed

  • August 16, 2013 at 4:03 am

    #395317

    Hi,

    I've scheduled M-Plan to perform Full & Diff. backups, till yesterday those plans were ran fine, but Today Diff. backup job failed with the reason below --

    Executing the query "BACKUP DATABASE "" TO DISK = N'..." failed with the following error: "Cannot perform a differential backup for database "", 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.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly (Error -- "-1073548784")

    I already performed Full backup job, but still failing with the same reason...please help me..it is an emergency...

  • August 16, 2013 at 4:18 am

    #1642061

    any new DB added to the backup list witout full backup?

    Regards
    Durai Nagarajan

  • August 16, 2013 at 4:34 am

    #1642067

    No DBs were created recently. If yes, it should be included when I ran Full backup job successfully.

  • August 16, 2013 at 4:43 am

    #1642075

    Run below code to see which databases does and does not have a full backup. Check the date to see if the last full backup is recent enough.

    select db.name, database_id, database_name, type, backup_finish_date

    from master.sys.databases db

    left outer join

    (select database_name, type, MAX(backup_finish_date) as backup_finish_date from msdb..backupset bs group by database_name, type) bs

    on db.name = bs.database_name

    where type is null or type = 'D'

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

  • August 16, 2013 at 4:48 am

    #1642077

    Table shwoing all the Databases are fully backed up and recent date was Today's. After this Full backup also, I tried to run Diff. job, but no luck with same msg...

  • August 16, 2013 at 4:54 am

    #1642083

    Can you pin point the error to a specific database?

    Can you manually perform a FULL and DIFF back-up on that database?

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

  • August 16, 2013 at 5:01 am

    #1642084

    Performed manual Full backup of a DB and when trying to take manual Diff. backup, same error appeared...

    Msg 3035, Level 16, State 1, Line 1

    Cannot perform a differential backup for database "",

    because a current database backup does not exist.

    Perform a full database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option.

    Msg 3013, Level 16, State 1, Line 1

    BACKUP DATABASE is terminating abnormally.

    Please help me...I've tried couple of options, but none of them worked well.

  • August 16, 2013 at 5:40 am

    #1642099

    Check that there isn't some snapshot backup tool running against your databases. BackupExec, DPM or something like that.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    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

  • August 16, 2013 at 8:01 am

    #1642187

    Have a look at this thread:

    http://serverfault.com/questions/147459/cannot-perform-a-differential-backup-for-database-mydb-because-a-current-dat/147499#147499

  • August 16, 2013 at 9:00 am

    #1642214

    I can't see how snapshot backups could cause the error message reported by the OP. I can see how you can break the expected differential chain by doing a snapshot backup in between, but the error message is effectively saying there is no differential base at all.

    Does the below return the database you're having issues with creating a differential for:

    SELECT DB_NAME(database_id) FROM sys.master_files

    WHERE differential_base_lsn IS NULL

    AND type_desc='ROWS'

    AND DB_NAME(database_id)!='TempDB'

    The code posted earlier that queried msdb..backupset isn't sound if the database has been restored since that backup was taken. Is this database restored nightly or something like that? What does this show for the database in question:

    SELECT create_date FROM sys.databases

    WHERE name='<yourDBNamegoeshere>'

  • August 16, 2013 at 9:21 am

    #1642220

    HowardW (8/16/2013)

    I can't see how snapshot backups could cause the error message reported by the OP.

    They can. Seen it a number of times before here.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    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

  • August 19, 2013 at 8:21 am

    #1642714

    Hi Ajay,

    Did you perfom the Backup by maintainceplan job or manually (i mean manually means by selecting backup option from right click on the DB, )

    I tried this kind of backup when i get the same error with the DB.

    (i never used diff bkps i used only tlogs after full bkp)

    i am just adding a idea so that it may help you...

    :hehe:

Viewing 12 posts - 1 through 11 (of 11 total)

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