| Title: | VAX and Alpha VMS |
| Notice: | This is a new VMSnotes, please read note 2.1 |
| Moderator: | VAXAXP::BERNARDO |
| Created: | Wed Jan 22 1997 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 703 |
| Total number of notes: | 3722 |
Customer has a question and I can not seem to find an answer. Customer has an infoserver 150 with an exabyte 8mm tape drive. Infoserver software version information: LADCP Version V13.0 LASTPort Tape (LAP) Version V3.2 ESS$MADDRIVER Ident V2.34 LASTPort Disk (LAD) Version V3.0 ESS$DADDRIVER Ident X-17 Just recently it has required a second tape to be mounted. When doing a backup from a Vax system running V6.2 to the 8mm, the first tape is ejected, but never does he receive an opcom request to mount the second tape. If he inserts the second tape, it successfully completes the backup. If he runs the exact same backup command from a V5.5-2 system, it does generate a request to mount the second tape. Looked in the stars database and previous notes, could not see any reason why this might happen. Any suggestion? /Guy
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 297.1 | QUARK::LIONEL | Free advice is worth every cent | Fri Mar 07 1997 13:27 | 3 | |
You might ask first in TAPE::INFOSERVER. Steve | |||||
| 297.2 | LEFTY::CWILLIAMS | CD or not CD, that's the question | Fri Mar 07 1997 13:52 | 5 | |
He did... The client seems to be where the problem lies, according to
the answers there. O'VMS owns the client.
CHris
| |||||
| 297.3 | Suggestions... | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Fri Mar 07 1997 14:32 | 18 |
First try this with a supported tape drive. (See if this is the Exabyte, or something else...) We'll need to know which Exabyte drive, as there are various known problems with some of the Exabyte drives on certain firmware versions. The customer will need to confirm -- with Exabyte support -- that the customer's drive is up to Exabyte's current revision. We'll also need to know the exact BACKUP command used here. I'm not familiar with the version numbers displayed, and will have to assume that the OpenVMS host InfoServer tape kit -- there's a kit that's needed for various V6.x-vintage OpenVMS releases -- has been applied to this system. (If not, get it and apply it.) If the above does not point to a fix and you have the current MADDRIVER and BACKUP patches applied, then it's time for an IPMT... | |||||