11-22-2011 05:32 AM
I need your help. We make Backup2Disk to an Deduplication Storage.
After the Backup, it starts a duplication to Tape.
And there is the Problem. I get this error:
Final error: 0xe0000605 - The requested media is loaded, but has been deleted and does not contain any backup sets.
Final error category: Backup Media Errors
11-22-2011 05:43 AM
If you're not using BE 2010 R3 I'd suggest upgrading to that and patching with all available updates. Once done, try the duplicate job again.
11-22-2011 05:50 AM
Sorry, I am running Backup Exec 2010 R3 - SP1 and ALL HotFixes.
It it Windows 2008 R2 - 64 Bit
Thank you for your help
11-22-2011 06:02 AM
Look for the option "Use Write Once Read Many media" option under Device and Media options for backup jobs and templates. If it is selected, deselect it and see if that helps.
11-22-2011 06:43 AM
I do not use this option. In no backup job.
11-22-2011 06:46 AM
Was WORM media ever used in the past ?
11-22-2011 07:04 AM
No Never, they were created automatically.
I think you should now that this is a very new Installation. It is about 1 Month ould.
11-22-2011 07:11 AM
Seems similar to https://www.symantec.com/docs/TECH152714
11-22-2011 07:17 AM
I think this could be the solution. I deleted all Jobs (created with a policy) and made new jobs.
My it helps. I have to give it a try. Thank you.
12-05-2011 05:45 AM
So now the problems is, hmmmm, better :)
Duplication from Disk to Tape work, but sometimes it fails. If I look at the Disk Medias. There was 2 WORM Medias.
But there is no Job with WORM Media.? Thats very strange!!
12-05-2011 06:16 AM
Hi I have the same problem ex605... I have talked about it with 2nd support level.. They told me that engeneers work on it.. and fix will be upload soon.. I am waiting one week and nothing happends.. i have the same version 2010 R3 SP1 but in live update i can see SP1 fix.. and if i start this update it would popup a error... so i dont know if the SP1 package dont block new fix what i am wainting for....
12-05-2011 10:33 PM
...fixes aren't just written right off the bat to suit someone's issue. It's probably going to be tracked across a number of instances of the same issue, and once it's ready to be fixed, then Symantex would have to take through all the quality gates before releasing to the public.