Post reply

Large DB backup stumper

  • June 16, 2005 at 6:52 am

    #110556

    I have a 65GB database with 2 filegroups, each one containing 1 file. When I try to do a full backup, whether thru a maintenance plan or not, I get the following error:

     BackupMedium::ReportIoError: write failure on backup device 'K:\MSSQL7\BACKUP\mbs\MBS_db_200506152300.BAK'. Operating system error 33(The process cannot access the file because another process has locked a portion of the file.).

    The backup job runs for 4 or 5 hours then dies with the above error. I rebuilt the database recently due to table structure changes but I had the problem with the old db also. The very first backup I did on this new database worked but now subsequent ones will not.

    I am not getting any specific help from MS KB.

    Has anyone else seen this?

    Is there some service that runs on Win2K that is known to cause this problem?

    My other backups on various dbs < 10GB work fine.

    Thanks for any help.

  • June 16, 2005 at 7:05 am

    #566058

    If I recall correctly we had a similar issue that was caused by our netbackup system.  We wound up scheduling the SQL backups and the NetBackup so that the SQL backups completed before Netbackup started and we never saw that issue again.

    /*****************

    If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek

    *****************/

  • June 16, 2005 at 10:08 am

    #566186

    I'd agree 100% with this, we had the exact same problem and resolved it by rescheduling the second backup to a time after the first one had finished

  • June 16, 2005 at 11:09 am

    #566216

    I rescheduled the backups to run this weekend well after the system backups are finished.

    Thanks for the suggestions.

  • June 17, 2005 at 4:33 am

    #566352

    Watch out for Virus scanners as well, DB, log, trace, etc. files should always be excluded.

    Andy

  • June 17, 2005 at 4:37 am

    #566355

    But who in their right mind wouldn't have already excluded all of these things from the virus scanners

    Quick appologies to anyone willing to admit it

  • June 17, 2005 at 5:07 am

    #566363

    I agree for SQL Server, but now that every tom dick an harry app is installing MSDE...

    Andy

  • June 17, 2005 at 7:30 am

    #566400

    Mike

    I'll only admit I ran into the error before .

    Definitely either scheduled backups and virus scanning [will] cause this error. Depending on the scanning package, you may have trouble writing to the 'locked' file again after the error.

  • June 20, 2005 at 11:30 am

    #566823

    Wow.

    I don't know much about virus scanners. Our Network Admin installs them and handles firewall issues.

    We are running eTrust on that server.

    Is there any whitepaper or kb article that explains this so I have some ammo to take to them?

    Thanks.

     

  • June 20, 2005 at 12:39 pm

    #566839

    SQL Server Security: Dealing with Anti-Virus Programs

    http://qa.sqlservercentral.com/columnists/bkelley/sqlserversecuritydealingwithantivirusprograms.asp

    This is the best that I have seen.

    Andy

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

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