Troubleshooting Support Request Tperrno = Robot Operation Failed Easily
December 23, 2021Recommended: Fortect
Recently, some of our users told us that the robot did not fire when requesting media tperrno =.
Item: 100047734
Last Published: 26.05.
Reviews: 0 0
Product (s): Appliances, NetBackup
How To Check “Error While Requesting Media, TpErrno = Robot Operation Failed”
This article provides a new starting point for understanding and exploring “ media request failed, TpErrno = robot operation failed
”
To edit a videotape, several things have to happen. A great tape is mounted not just because it is physically in the pump, it is mounted only after the NetBackup AVRD daemon has successfully read the h2 tags from the tape and the result is successfully returned to NetBackup.
This really applies to VTL as it is a physical setup.
- NetBackup is requesting a SCSI reservation for the appropriate drive.
- NetBackup requests a tape mount through a media server using a TLDD process.
- TLDD forwards the TL requestDCD on the real control host of the robot. If the TV server is not the host descriptor of the robot, the TLDD on the media hosting server will send a request through the provider to the TLDCD on the host host of the robot.
- tldcd, the robot control host sends the scsi
CDB 0xa5 MOVE MEDIUM
command to the library. - The library moves each of the tapes we requested from the “vault” to the tape drive.
- NetBackup is sending
CDB 0x1d SEND DIAGNOSTIC
to the scsi reader; a valid and appropriate response is required. - NetBackup just runs scsi
CDB 0x00 Test Unit Ready
over and over – once the TUR finally gets the final0x00 READY
results, then only we both know the tape is actually physiologically and correctly loaded into the drive. - AVRD reads the title of the movie from the tape, it contains, among other things, the media ID of the tape – it must match the Media ID we requested, the security check shows that we definitely have the required tape.
On the
fail
Any of these steps will most likely result in flaxit will not mount and will be available for selection — for example, if a failure occurs in step 5 or 6, even though the tape is physically in the drive, NetBackup has determined that this is not possible. received. an acknowledgment is attached and this will cause “ Robot Loading Failed
” even if the robot physically inserts its tape into the drive.
a) Use tpreq -m
(-f
Use
b) robtest for replacing a tape in a drive for the m sx dy
“robust command”, where x is the slot number to move the tape and b is the drive number.
method a) Load the tape just like NetBackup does for a real job and creates a tpreq job opportunity in Activity Monitor. When you’re done, you can either cancel the tpreq job in Activity Monitor or run tpunmount -f
Method b) downloads the tape completely “outside” NetBackup, regardless of what robtest is involved in, sends a scsi CDB 0xa5 MEDIUM
move (to unload ud
In l Otherwise, the tape should be moved to the drive if successful, and after a short time, the media ID should appear next to the drive in the internal output of vmoprcmd.
With tpreq you can switch to monitoring the activity that is used to load the feed. To test a particular drive, you will have to do LOW turns that you don’t want to use. NetBackup uses tape drives in some way, so it cannot specify an exclusive drive.
With robtest, you enter an incredible drive number like m s1 d2, which in turn will move the tape to slot 1 on Robot 2
If you use either of these methods, this drive will end up with a tape:
Recommended: Fortect
Are you tired of your computer running slowly? Is it riddled with viruses and malware? Fear not, my friend, for Fortect is here to save the day! This powerful tool is designed to diagnose and repair all manner of Windows issues, while also boosting performance, optimizing memory, and keeping your PC running like new. So don't wait any longer - download Fortect today!
Here we see a specific Mediaid (AA0010) in the RecMID and ExtMID fields, which is real for the tape in the correct library.
ExtMID (External Media Identifier) denotes a physical barcode on an adhesive strip, an “offline” strip (if only tape drive (s) and small robot or itsPresence, this field is often empty).
RecMID (Recorded Media ID) are Mediaid h2 tags recorded on the tape – a 1 KB document block at the beginning of the entire tape. This should always be done without the possibility of attaching the tape itself.
First of all, we are trying to test the idea that we see the media ID in the main RecMID on the first field of each disk. If it is not present, not everyone will be able to edit a specific tape and will not have the message “ Robot operation error
” even if the videotape may be in the drive.
If you’ve used tpreq do and don’t see the mounted tape, try robtest and make sure the tape is inserted into at least one drive. If the feed is displayed on an input device, manually via the feed header using ‘dd’ (unix), optionally ‘nt_ttu’ (Windows).
If the problem is more detailed, other entries are needed:
- bptm is about VERBOSE = 5
- Operating system device protocols
-
veritas volmgr debug / robots -
veritas volmgr debug / daemon -
veritas volmgr debug / ltid -
veritas volmgr debug tpcommand
-
veritas volmgr DRIVE_DEBUG -
Restart the media manager services or present Veritas Volume Manager in Windows services.
Has this been helpful so far?
Download this software and fix your PC in minutes.Fout Bij Het Aanvragen Van Media Tperrno Robotwerking Mislukt
Fel Vid Begaran Av Media Tperrno Robotdrift Misslyckades
Error Al Solicitar Medios Tperrno Fallo La Operacion Del Robot
미디어 요청 오류 Tperrno 로봇 작업 실패
Fehler Beim Anfordern Von Medien Tperrno Roboterbetrieb Fehlgeschlagen
Blad Zadania Nosnika Tperrno Operacja Robota Nie Powiodla Sie
Erreur De Demande De Media Tperrno Echec De L Operation Du Robot
Errore Durante La Richiesta Del Supporto Tperrno Operazione Del Robot Non Riuscita
Erro Ao Solicitar Midia Tperrno Falha Na Operacao Do Robo
Oshibka Zaprosa Nositelya Tperrno Operaciya Robota Ne Udalas
Path> veritas volmgr ROBOT_DEBUG