BackupDiskFile::OpenMedia: Backup device

Question

BackupDiskFile::OpenMedia: Backup device

Krasavita

SSC-Insane

Points: 23138
More actions
June 2, 2010 at 1:45 pm

#140637

What this means anyone knows?
BackupDiskFile::OpenMedia: Backup device 'F:\TransactionJobs\uuu_ccc\uuu_ccc_backup_201005311500.trn' failed to open. Operating system error 2(The system cannot find the file specified.).

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

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

jimmycjen Default port Points: 1457 More actions · Answer 1

I'm having the same error except my was a differential backup. The error comes from a job that executes a maintenance plan which deletes BAK files older then 24 hrs and then do the diff. backup.

We have Windows Server 2003 64-bit Enterprise and SQL 2008 SP2.

Does anybody has this problem before ?

Steve Jones - SSC Editor SSC Guru Points: 736270 More actions · Answer 2

Are you trying to append to a file? Or perhaps permissions? This is an OS level error bubbling up. Either paths are wrong, permissions are wrong, or maybe the file is locked.

chetanr.jain Hall of Fame Points: 3938 More actions · Answer 3

Hi,

i can think of issue with file path or permission.

try to have backup at some other path and check if that is getting successfull or not?

Michael L John One Orange Chip Points: 27056 More actions · Answer 4

This error can be a couple things, none of which are obvious.

You didn't say if this happens every time, or is intermittent. What is the OS? If it's Windows 2008, then I would look into permissions first. Before you start granting permissions to individual drives, folders, etc, try to make the SQL Service account a local admin. See if that clears the issue. If so, grant the specific permissions, and lower the rights for the service account.

The following seems to be related:

BackupDiskFile::RequestDurableMedia: failure on backup device '\\RemoteBackup\msdb_FULL_20110306_001156.bak'. Operating system error 64(The specified network name is no longer available.).

I have struggled with this, as well as the error you are getting, on 30 different servers. There is no pattern, it's not the same servers. I have cleared both errors on a couple servers with the following, although it seems to be trial and error.

1. Set the max memory for SQL Server to allow more memory to the OS.

2. Check the backup drive for virus scanning. We were scanning every drive on a few of the SQL Servers. Once this was set to exclude the data, log and backup drives, both errors went away.

3. Check is any defragging software is running. Same as #2.

4. Are backups running? Check the timing.

5. Is this a cluster? Or a stand alone server? There was a job set up by the previous DBA on the clusters that failed them over every night. This ran right in the middle of the backups. Check other jobs that may be running also.

Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/

jimmycjen Default port Points: 1457 More actions · Answer 5

Thank you all for responding my question. I really appreciate it.

The problem started last week. From OS level, we were getting either "...file being used by another process" or "...cannot find the file specified". From SQL Server, sp_rename were failing. All these were too mysterious to me and all of them were coming from jobs.

Both my coworker and I were looking into these problems until my coworker found out all the backups were duplicated, then I suddenly realized it was caused by our disaster recovery server. What happened was that previous Sunday we had a disaster recovery drill in which we had to mimic our production server (let's call it Production). We copied all the MDF and LDF files and re-attached at disaster recovery site - let's call it ProductionDR. We also restored the MSDB and enanled SQL Server Agent -- that's the problem, because both Production and ProductionDR are running the same jobs, especially those calling DTS/SSIS which connects to Production. That's why we were getting all those errors.

Lesson learned:

(1) Do not enabled SQL Agent on ProductionDR if you don't plan to test jobs

(2) If you do plan to test jobs, make sure you change the DTS/SSIS to point the correct server

(3) Disable SQL Agent after the drill

Steve Jones - SSC Editor SSC Guru Points: 736270 More actions · Answer 6

Thanks for the update, and a good catch.

I might set a script to do all these things before and after the DR test, so that you have a set start and finish to your test with these scripts. you could easily use Powershell or VBScript to start/stop Agent on the appropriate servers.