Failing backup can't create backup

  • I have a new SQL2005 database with several databases on it. I have a pretty de-facto backup (from using the backup wizard) that does a full backup of the user databases every night.

    Yesterday I added a new database and it won't backup. The errors are

    2009-11-11 15:09:32.70 Backup Error: 3041, Severity: 16, State: 1.

    2009-11-11 15:09:32.70 Backup BACKUP failed to complete the command BACKUP DATABASE Database. Check the backup application log for detailed messages.

    2009-11-11 15:11:18.57 spid99 Error: 18204, Severity: 16, State: 1.

    2009-11-11 15:11:18.57 spid99 BackupDiskFile::CreateMedia: Backup device 'N:\Backups\Userdatabases\Database\Database _backup_200911111511.bak' failed to create. Operating system error 3(error not found).

    2009-11-11 15:11:18.57 Backup Error: 3041, Severity: 16, State: 1.

    I've migrated another database on today and that backups up fine to the same area.

    The issue seems to be creating the files in the sub-directory \Userdatabases\Database\

    The job runs fine if it doesn't create the sub-directory for each database.

    Ideas?

    thanks

  • Does the directory N:\Backups\Userdatabases\Database\ exist?

    Do the SQL agent and SQL Server service accounts have permission to that directory?

    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
  • Is the database that is failing the backup actually called database? If so, it could be because your database name is set to a reserved word in SQL. That is not a recommended practice. If you change the name of the database does it backup then?

    Joie Andrew
    "Since 1982"

  • Thansk for the replies

    GilaMonster- initially the job creates the folder (create sub directories for each database), when it failed I tried it by creating the folder.

    The SQL agent and server has the correct permissions as its created folders and backup files on the same drive and directories.

    As this is a cluster the SQL has a dependancy on the drive.

    UnixBomber- No its not the real name of the database. I just masked it

  • Do you have any space in the database name? I noticed that a trailing space in the backup file from your post.

  • Ah sharp eyes there. Yes thats it, I must have added a space when creating the database.

    I'm going to follow the instructions at

    http://blogs.msdn.com/sqlserverfaq/archive/2008/07/27/maintenance-plans-with-backup-database-task-fails-when-the-create-a-sub-directory-for-each-database-option-is-checked.aspx

    to solve it

  • Yes that did indeed solve the problem.

    Thank you for your help

  • I know this is an old post but thanks! I had been going round in circles all day and the trailing space was my issue. Saved my sanity!

Viewing 8 posts - 1 through 7 (of 7 total)

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