Error while database backup

  • Hi,

    I am trying to backup a database but getting below error:

    "System.Data.SqlClient.SqlError: Backup and file manipulation operations (such as ALTER DATABASE ADD FILE) on a database must be serialized and

    encryption changes must be serialized. Reissue.."

    Any help/suggestions will be appreciated.

    Thanks

  • Operations that cannot run during a database or transaction log backup include:

    1) File management operations such as the ALTER DATABASE statement with either the ADD FILE or REMOVE FILE options.

    2) Shrink database or shrink file operations. This includes auto-shrink operations.

    Please cross-check on above points.

  • Checked. Still not working..

  • kirti.malukani (11/21/2011)


    Checked. Still not working..

    What code are you running and what's the exact error?

    Any opened transactions or operations on the server (activity monitor)?

  • kirti.malukani (11/21/2011)


    Checked. Still not working..

    You didn't get me. Please answer following.

    Are you / anybody doing any ADD FILE / REMOVE FILE operation?

    Is there any job scheduled for Database / File Shrinking?

    Does your database have 'auto-shrink' enabled / set as TRUE?

  • Error 3023 Severity Level 16

    Message Text

    Backup and file manipulation operations (such as ALTER DATABASE ADD FILE) on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed.

    Explanation

    These operations may not be performed at the same time as a backup operation:

    •File management operations such as the ALTER DATABASE statement with either the ADD FILE or REMOVE FILE clauses.

    •The file truncation phase of shrink database or shrink file.

    If a backup is started when either an add or remove file operation is in progress, the backup will wait for a timeout period, then fail. If a backup is running and one of these operations is attempted, the operation fails immediately.

    If a shrink operation tries to truncate a file while a backup is running, the shrink stops without truncating the file, however data pages have been relocated. If a backup is started just as a file is being truncated, backup normally waits long enough for the file truncation to complete.

    Action

    Reissue the operation after the conflicting operation has completed.

    If a shrink operation fails, reissue the shrink command with the TRUNCATE_ONLY option after the backup completes.

  • I noticed that my Transaction Log for a Database was over 25 GB.

    Then I checked and saw that the full backup had been running for over 10 Hours.

    Then I noticed that a differential backup is still running.

    I can't shrink the log or change the recovery model.

    I was having connectivity issues going on where multiple SSIS Jobs were failing.

    I need to shrink the log and get a full backup.

    Any help would be greatly appreciated.

    For better, quicker answers on T-SQL questions, click on the following...
    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/

  • Please post new questions in a new thread.

    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
  • Oops ....2 years old thread.

    -------Bhuvnesh----------
    I work only to learn Sql Server...though my company pays me for getting their stuff done;-)

  • Hi.

    I understand your question is related to the current post..

    Any advise on resolving the issue?

    Thanks

Viewing 10 posts - 1 through 9 (of 9 total)

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