Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

No appendable media could be mounted.

Status
Not open for further replies.

keefe007

IS-IT--Management
Oct 11, 2004
4
US
I have a server running Windows 2000 Server, which I am having back-up problems on. The backup software is Backup Exec 8.5 using a Archive Python 06408 20/40 GB tape drive.

I have a 5 day tape rotation which runs Monday - Friday. The problem I am having is that lately every Thursday night back-up is not running properly. The backup will run half way, and then eject the tape. Someone has to put the tape back in and the backup finishes a few minutes later.

The error that I see in the logs is:

"No appendable media could be mounted.
Switching to overwrite operation on scratch media."

When I go into the media manager portion of Back-up Exec this certain tape for Thursday shows Append Time Left: None. All of the other tapes Append Time Left: Infinite. I have tried a new tape, but I still get the same result.

Here is a full log: I can post more if needed.

======================================================================
Job server: MAGSERV
Job name: Thursday1
Job started: Thursday, September 02, 2004 at 9:00:01 PM
Job type: Backup
Log file: BEX09.txt
======================================================================

No appendable media could be mounted.
Switching to overwrite operation on scratch media.

Drive and media information from media mount:
Changer Name:
Drive Name: DELL 1
Media Slot: 0
Media Cartridge Label: 4MM000005
Targeted Media Set Name: Media Set 1

======================================================================
Job Operation - Backup
Media operation - overwrite.
Hardware compression enabled.
======================================================================

Media Name: "Thursday1"
Backup of "C: "
Backup set #1 on storage media #1
Backup set description: "MagSet"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 9/2/2004 at 9:00:36 PM.
Unable to open the item \Documents and Settings\Administrator\Cookies\index.dat - skipped.
Unable to open the item \Documents and Settings\Administrator\Local Settings\History\History.IE5\index.dat - skipped.
Unable to open the item \Documents and Settings\Administrator\Local Settings\Temporary Internet Files\Content.IE5\index.dat - skipped.
Unable to open the item \Documents and Settings\All Users\Application Data\Microsoft\Network\Downloader\qmgr0.dat - skipped.
Unable to open the item \Documents and Settings\All Users\Application Data\Microsoft\Network\Downloader\qmgr1.dat - skipped.
Unable to open the item \Documents and Settings\bkupexec\Local Settings\Temp\JET12.tmp - skipped.
Unable to open the item \Documents and Settings\bkupexec\Local Settings\Temp\JET2B4A.tmp - skipped.
Unable to open the item \Documents and Settings\bkupexec\Local Settings\Temp\JET2CB.tmp - skipped.
Unable to open the item \Program Files\VERITAS\Backup Exec\NT\adamm.log - skipped.
Unable to open the item \Program Files\VERITAS\Backup Exec\NT\pvl.ldb - skipped.
Unable to open the item \Program Files\VERITAS\Backup Exec\NT\pvl.mdb - skipped.
Unable to open the item \WINNT\System32\dhcp\dhcp.mdb - skipped.
Unable to open the item \WINNT\System32\dhcp\DhcpSrvLog.Thu - skipped.
Unable to open the item \WINNT\System32\dhcp\j50.log - skipped.
Unable to open the item \WINNT\System32\dhcp\tmp.edb - skipped.
Unable to open the item \WINNT\System32\dns\dns.log - skipped.

Backup completed on 9/2/2004 at 9:32:41 PM.
Backed up 19498 files in 823 directories.
16 items were skipped.
Processed 2,380,594,928 bytes in 32 minutes and 5 seconds.
Throughput rate: 70.8 MB/min
----------------------------------------------------------------------

Media Name: "Thursday1"
Backup of "D: "
Backup set #2 on storage media #1
Backup set description: "MagSet"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 9/2/2004 at 9:32:42 PM.

Drive and media information from media mount:
Changer Name:
Drive Name: DELL 1
Media Slot: 0
Media Cartridge Label: Monday1
Targeted Media Set Name: Media Set 1
Backup set #2 on storage media #2

Backup completed on 9/7/2004 at 11:13:44 AM.
Backed up 1341 files in 37 directories.
Processed 376,181,526 bytes in 4 minutes and 27 seconds.
Throughput rate: 80.6 MB/min
----------------------------------------------------------------------

Media Name: "Thursday1"
Backup of "E: "
Backup set #3 on storage media #2
Backup set description: "MagSet"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 9/7/2004 at 11:13:45 AM.

Backup completed on 9/7/2004 at 11:15:16 AM.
Backed up 1155 files in 105 directories.
Processed 225,729,315 bytes in 1 minute and 31 seconds.
Throughput rate: 141.9 MB/min
----------------------------------------------------------------------

Media Name: "Thursday1"
Backup of "\\MAGSERV\System?State "
Backup set #4 on storage media #2
Backup set description: "MagSet"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 9/7/2004 at 11:15:16 AM.

Backup completed on 9/7/2004 at 11:16:21 AM.
Backed up 1995 files in 79 directories.
Processed 270,538,009 bytes in 1 minute and 5 seconds.
Throughput rate: 238.2 MB/min
----------------------------------------------------------------------

======================================================================
Job ended: Tuesday, September 07, 2004 at 11:16:21 AM
Job completion status: Successful
======================================================================

Thanks!

Keefe John
Techware PC
262-808-9000
 
Your backup is spanning more than one tape now. Your data has increased. Look at the job log above.

Your job is probably set to append/overwrite in the job properties.

The backup starts:

No appendable media could be mounted.
Switching to overwrite operation on scratch media

Means the tape is not appendable. So if the tape reports not appendable - then its full or in scratch media. Scratch media is tapes that are for overwrite operation..so it would not be appendable.

Backup Exec switches to overwrite mode and starts overwriting the tape 4MM000005

Drive and media information from media mount:
Changer Name:
Drive Name: DELL 1
Media Slot: 0
Media Cartridge Label: 4MM000005
Targeted Media Set Name: Media Set 1

Job is running
C: Drive Backup set #1 on storage media #1
D: Drive Backup set #2 on storage media #1

Mounts another tape during the middle of the D: drive backup. Notice The tape named Monday is inserted in the same slot and now we switch to Backup set #2 on storage media #2. Meaning we are still backing up part of D: but on the next tape in the set.


Backup of "D: "
Backup set #2 on storage media #1
Backup set description: "MagSet"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 9/2/2004 at 9:32:42 PM.

Drive and media information from media mount:
Changer Name:
Drive Name: DELL 1
Media Slot: 0
Media Cartridge Label: Monday1
Targeted Media Set Name: Media Set 1
Backup set #2 on storage media #2


So it looks like your getting 2.3 gigs on the first tape and around 832 megs on the second tape.

The job is completing sucessfully - so there is no error.
The message your seeing is informational

Are you sure the tape drive is 20/40? I think your correct and its is a DDS4 Do your other jobs compare to the byte count?
What tapes do you use?
It almost seems if you have a DDS4 20/40 tape drive and using DDS1 Tapes. DDS1 tapes hold 2/4gb which makes more since to me if your getting 2.3 gigs on that first tape and that would seem normal depending on how compressed the data is already.

Hardware compression is turned on according to the job log.

I would have to see some of your other backups on other days
 
Thanks for the help so far.

I am pretty sure that these are 20/40 GB tapes. There are 5 of the same tapes, 4 of which work fine. I have tried swapping in a new blank tape on Thursday and get the same issue.

Here are the logs for an entire 5 day rotation, Monday - Friday.
As you can see the same backup happens every day. It is just slightly larger each day. The backup works fine Mon, Tues, Weds, then it goes work thurs, but then friday works fine again.
 
Is that Thurday tape Identical in brand to your other tapes. What do the tapes say physically on the outside?
 
And if it is identical, are you doing any other backups to that tape?

-SQLBill
 
Goto the Media tab and right click on Media Set 1, what is the Overwrite and Append period
 
Overwrite protection period: None
Append period: Infinite - Allow Append

The weird thing is, when I look at the media tab the two different tapes I tried for thursday now show "Append Time Left: None" while all of the other tapes in the set show "Append Time Left: Infinite.
 
That would mean the tape is fuill, then moved on to the second tape which your job log reports. Hmmm
 
Recheck your backup jobs. It's possible that:

1. One or more of your backup jobs are going to the wrong tape.

2. You have additional backups going to the Thursday tape

3. Someone else is doing backups to that tape.

4. The tape is bad and only part is usable.

I think 3 is unlikely, you would see the jobs in Backup Exec. Likewise, 2 would show up in the job monitor.

-SQLBill
 
Still doesnt explain why he is getting 3 gigs on a tape that when the jobs start is a overwrite then kicks out the tape. All the jobs are consistant for byte count, media set targeted, etc. His thursday job definitly overwrites the tape then prompts for another...so there would be nothing esle on the tape...thats why he is getting no appendable media...nothing is on the tape at that point so no other jobs have written to the tape.


No appendable media could be mounted.
Switching to overwrite operation on scratch media.

This means the tape is in scratch and anything in scratch will be overwritable - not appendable


Thats why I question if this Thursday tape is physically different from the other. But he reports he has tried other tapes or new tape.. Almost seems as if the job is corrupt or something.
 
You run these jobs at night, so try this:

swap Wednesday's tape with Thursday's tape. If the job fails tonight (Wednesday job - using Thursday's tape) then you know it's the tape. If the job works fine but fails again on Thursday (using Wednesday's tape), you know it's a problem with your Thursday job.

-SQLBill
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top