[Veritas-bu] Media Open error (83) having upgraded the OS

2003-07-16 10:27:30
Subject: [Veritas-bu] Media Open error (83) having upgraded the OS
From: david.chapa AT adic DOT com (David Chapa)
Date: Wed, 16 Jul 2003 07:27:30 -0700
Did you preserve your st.conf file before applying the jumbo patch?

I would start there, since the jumbo patches are notorious for laying
down a "new" copy of the st.conf file.

After re-reading one of the sections of your email...its seems that this
may not be the case.  You mention that manual submissions seem to work,
but scheduled do not.  

I would created bpsched, bpdbm and bptm directories to start in
/usr/openv/netbackup/logs to see what information you may get from it. 

I would pay particular attention to bptm and bpsched.

David Chapa

-----Original Message-----
From: Redman, Paul [mailto:paul.redman AT hp DOT com] 
Sent: Wednesday, July 16, 2003 4:41 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Media Open error (83) having upgraded the OS


Hope all is well today.

Netbackup Business Server 3.2, Solaris 8 on a Sun Ultra-5 system, no MPs
of FPs, just the Solaris jumbo patch for Netbackup (108261-11).

I have been testing 3.2 and the effect of upgrading Solaris from 2.6 to
8 on a test system with a standalone tape drive.  Sun said all I would
need to do having upgraded was to install the jumbo patch mentioned

One thing I did have to do having upgraded/patched the OS was to
re-install the sg driver as it was missing

Backups are now a fairly unpredictable affair.  I think any manual
backup I kick off via bpadm works successfully, but anything that's
scheduled or run via cli (bpbackup) can fail with an error code of 83
(media open error).

I've searched the Veritas archive and uncovered nothing, the archive for
veritas-bu did have an entry from about 2001, which said to check
classes.  I have .... they're fine.

I'm now running the ltid daemon in verbose mode, but this is as good as
it gets :-

10:28:19 [19382] <2> bptm: INITIATING: -mlist -cmd 
10:28:19 [19382] <2> bptm: EXITING with status 0 <----------
10:29:17 [19358] <2> io_position_for_write: locate block is done
10:29:19 [19358] <2> io_open: retrying open, errno = I/O error
10:29:28 [19358] <2> io_open: retrying open, errno = I/O error
10:29:33 [19358] <16> io_open: cannot open file
req/DD0036, I/O error
10:29:33 [19358] <2> log_media_error: successfully wrote to error file -
3 10:29:33 DD0036 0 OPEN_ERROR
10:29:33 [19358] <2> check_error_history: called from bptm line 13294,
us = 83 

The above is a small section, I didn't want to stuff this e-mail with

Have I got some kind of drive configuration problem post-upgrade or do I
need to look at the batch of media that I am using?  Do I need a
Netbackup patch of some kind?

Thank you in advance & have a splendid day,

> Paul Redman
> Unix Systems Admin - Hilton TFO Helpdesk
> Customer Support & Solutions Centre (CSSC)
> HP Services
> Hewlett Packard
> Tel: External +44 (0)118 916 2075
> Email: Paul.Redman AT hp DOT com

Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu