Backup Exec media append and overwrite

Hi All,

I have a problem with backup exec. Its spitting the tapes out overnight and complaining that the media is write protected.

Each tape is replaced daily at the same time, the the overwrite protection is set to 1 day. The append period is set to infinite.

However on my backups, it writes the first job to the tape, but then tries to do the second, and ejects the tape saying;

 "Media 'Daily - Data - TD1 - Monday' is overwrite protected.

The media in drive 'TD1' is currently allocated and is not available for overwrite operations."

Looking at the statistics of the tape, I can see that of a total capacity. 141GB of data has been written to the tape. The used capacity is 80GB and the available capacity remaining is 115GB out of a total of 195GB. The tape is an LTO2 so with compression should fit at least 400GB on it. However its just not even trying to append to the media.

Its my understanding that it should write the second job to the tape by 'appending' to the media, and then once full eject the tape.

Is that correct, do I have something wrong, or is something wrong with backup exec?

It's version 2010 R3 for anyone who needs to know.

Many thanks,

Who is Participating?
Iamthecreator OMConnect With a Mentor Administrateur Systeme et ReseauxCommented:
Ok, the error is not pertinent to the issue.
Are you sure that you have specified the same Media Set for all the Jobs ?
Can you get me the screenshots for the device and media settings for the 2 jobs and the media set settings from the devices âne in BEWS ?
Also the append jobs are set to "Append to media , terminate job if no appendable media" ?
Why was the tape ejected after writing 272 MB , how much data are we backing up in the concerned job?
If everything is in order, remove the OPP (set to 0) , ensure that only the first job is set to overwrite, associate the tape to SCRATCH , ensure all jobs have the same media set specified.
APP set to infinte, run jobs and update.
If this doesnt work we will need to run SGMON to enable debugging and I will need the logs.
Iamthecreator OMAdministrateur Systeme et ReseauxCommented:
You will need to understand how media management works in BEWS and what factors come in play
please refer to the following articles.

An explanation of the "Overwrite Protection Period" and the "Append Period"
CDA_AdministratorAuthor Commented:
I'm sorry I've watched the video but still not sure I understand.

If I set the media to have a protection period of 0 days, with a append period of infinite - then it should work? But they say that's a bad idea and I should set an protection period. I want to ensure data on that tape can't be overwritten within 24 hours, but also allow data to be added onto the end of the disk.

For example. Job 1 runs at 10pm, job 2 runs at 11pm - should job 1 run and fill up the first, say 50GB of the drive, and then mark that first 50GB as protected, and then should job 2, write or 'append' to the next 50GB of space - once the job reaches a point where it can no longer append to the disk (the disk is full) isn't that the point that it should say that the disk is overwrite protected? I suspect I have something very wrong...
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

Iamthecreator OMAdministrateur Systeme et ReseauxCommented:
You do not need to associate the media manually to any user defined media set.
Create a media set with the desired Overwrite Protection Period and Allow Append settings.
Associate the tape with the scratch media set.
In the job properties specify the media set created earlier.
The first job on a new/Scratch tape can only run as an Overwrite.
Once the first job runs it will automatically assign the tape to the media set specified within the job and the tape will inherit the media set properties hence will become overwrite protected.
Ensure that the subsequent jobs are set to append otherwise the tape will be ejected and you will be prompted to insert an overwritable media.
Iamthecreator OMAdministrateur Systeme et ReseauxCommented:
Backup Exec has a very advanced and robust media management system to provide a fool proof and efficient way of managing and protecting media.
Take some time to read and understand the article I mentioned earlier  (the video does not contain or explain everything)

About media in Backup Exec
CDA_AdministratorAuthor Commented:

I did indeed read the article and it backs up (in my head) that what I've set up is correct...

I've checked my jobs and media settings.

When creating the job, I've got the settings under 'Device and Media' to 'Append to media, overwrite if no appendable media is available'

When first setting up the tape today, I placed it into the scratch media library to start over with it. The job is set to use a media library that has a Overwrite protection period of 1 day, and in infinite append period.

What seems to be happening is job 1 is written to the tape, however job 2, even though there is space left on the tape to be appended to, claims that the tape is overwrite protected and can't write to disk. Even though the job is set to append to the media...
CDA_AdministratorAuthor Commented:
With the above settings, the tape ejected today after only having 272mb written to it.....

Not sure what to do as it's killing my backup schedule!!
Iamthecreator OMAdministrateur Systeme et ReseauxCommented:
There seems to some other problem. If the media settings are not correct or suitable it will not write to the tape at all. Check the BE alerts and notification and Windows event viewer around the time the tape was ejected.
CDA_AdministratorAuthor Commented:
Media 'Daily - Data - 3 - Wednesday' is overwrite protected.

The media in drive 'TD2' is currently allocated and is not available for overwrite operations.

Media Set: Tape Media
Overwrite Protection Until: 1/24/2013 11:47:49 AM.
Appendable until: 1/30/2013 10:45:52 AM

There isn't anything in the event log around the time of the tape being ejected other than 'Please remove the media and respond OK'

There was an error about 2 hours before the tape got ejected, but can't imagine how it'd be related but here it is;

Database Exception Context:AutoClearAlerts: sp ClearAutoAlert Error:-536837662: :: -2147467259:Login timeout expired :: DB Error Set 0: native=0xffffffff source=Microsoft OLE DB Provider for SQL Server hr=0x80004005 Login timeout expired
Iamthecreator OMAdministrateur Systeme et ReseauxCommented:
Also if the media set settings are to allow INFINTE append why is the media properties showing
Appendable until: 1/30/2013 10:45:52 AM  ?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.