Alert Media is write protected but it is not.
Updated: 21 May 2010 | 13 comments
This issue has been solved. See solution.
Write protected problem
Specs:
w2k3 server SP2 , backupexec 10.1 SP3 rev 5629, LTO2 400Gb tapes, HP Storageworks Ultrium 448.
Always used the same tape with the same drive and now all of a sudden I get the alert that my tape is write protected and that I should remove the write protect tab.
Of course the write protect tab is not used.
I' am able of doing an inventory but a quick erase or write to the tape results in the alert.
Please can anyone tell me what is going on?
Thanks!
discussion Filed Under:
Comments
It must be placed in a media
It must be placed in a media set which has overwrite protection period. Please go to the media tab in Backup Exec and check the media set under which the tape is present currently. Move it to scratch media if you would like the tape to be available for overwrite. You can use following document to understand ADAMM in detail:
http://support.veritas.com/docs/192265
Please mark it a solution, if this is useful.
Thanks
RE: Alert Media is write protected but it is not.
if you cannot even Quick Erase the tape, it probably has nothing to do with the media sets
Have you run a pass or two of the manufacturer's diagnostics against the drive?
If this response answers your concern, please mark it as a "solution"
Thanks Ken and
Thanks Ken and Hemant,
Running a diagnostic of the manufacuter of the drive is a good idea.
I will try that right away.
The diagnostic came up with
The diagnostic came up with some issues. One of them was updating the firmware which I did.
Lets see and wait.
Problem still not solved
Updating the firmware didn't do much.
Last friday I used a tape from nov 2007 which was mounted 21 times since then. And again the tape was seen as write protected.
Could the problem be that they are too old? Because when I use a brand new one backup will go smoothly.
What is the expiration date of Ultrium LTO2 tapes anyway?
Any one an idea?
RE: Problem still not solved
So new tapes Overwrite OK, but old tapes do not? That kinda shoots anything involving the hardware then.
If you drag one of these old tapes to the Scratch set, do you still have problems?
If this response answers your concern, please mark it as a "solution"
Well, it is simply to do with
Well, it is simply to do with ovewrite protection period imposed by media set properties. I dont think it has anything to do with firmware. Check the properties of the media set to which the job is directed. It is making it overwrite protected. Move the media to scratch media and you should have it overwritable.
Thanks
Thanks for the input,
Thanks for the input, gentlemen.
We use the following media set: Daily
The properties are:
Overwrite protection period: None
Append period:None Infinite - Allow Append
That's it. Very basic really.
So it should be overwritable.
Quit a challenge I think.
Thanks.
Overwrite protection period:
Overwrite protection period: None
Append period:None Infinite - Allow Append
With this setup, the tape will not expire until xx days after the last Append. That is, if you Overwrite the tape on Monday, then APPEND Tues, Weds, Thurs and Fri, with a 7 day OPP, you will not be able to overwrite the tape until the FOLLOWING Saturday
If this response answers your concern, please mark it as a "solution"
Hi, Did you ever reach a
Hi, Did you ever reach a resolution on this?
- I am having what sounds like the exact same issue. I have posted a forum post here: https://www-secure.symantec.com/connect/forums/bac...
If you have any feedback please update this thread (or my one)!
Thanks!
No, I never reached a
No, I never reached a resolution on this.
After I have read your forum posts my feelings are exactly the same about that it might be somekind of hardware problem.
So if you have some kind of answer about this problem please let me know.
Thanks.
Hi fpeek, We
Hi fpeek,
We advised client that this was a likely hardware issue. They ordered a new drive, swapped out the old and in with the new, using new cable (provided) and seperate SCSI channel (more from a cabling perspective - it fit better in the box etc).
After that, all has been working correctly, without issue.
NB: I don't believe cable or seperate SCSI channel has made any difference, it was simply more convenient as the cable was quite long and it fit better into the space etc..
Cheers.
Problem solved
Hello all,
thanks for your replies.
We did exactly what CLakey did withou changing the cables, just the drive.
The defect was very much likely to be the drive it self. There is a little pin in the drive which detects if the tape is write protected or not.
That was not working right.
So, problem solved.
Would you like to reply?
Login or Register to post your comment.