need an alternate path

[BRupeshR33]

Hi All,

Is there any alternate way to find out similar "media error" output apart from this mentioned path - /usr/openv/netbackup/db/media/errors?

looking for similar output:

03/26/20 13:39:01 XXXXX 2 TAPE_ALERT Drive_name 0x00020000 0x00000000
03/26/20 14:25:34 XXXXX 2 TAPE_ALERT Drive_name 0x00020000 0x00000000
03/26/20 17:05:48 XXXXX 2 TAPE_ALERT Drive_name 0x00020000 0x00000000
03/27/20 07:40:14 XXXXX 2 TAPE_ALERT Drive_name 0x00020000 0x00000000

Thanks,

Rupesh

[Mouse]

Since these are hardware errors they come from drivers so /var/log/messages and/or syslog will have a matching entry if it's what you are looking for.

[Marianne]

@BRupeshR33 

The entries in the errors file happened almost 4 months ago.
I doubt that there will still be any other log in NetBackup or the OS that has that information.

As per @Mouse , the info is normally logged in syslog, which get recycled by the OS at regular intervals.

In NetBackup, the errors will also be logged in the media server's bptm log (if enabled) as well as on the master server in the 'error' logs. Use 'bperror -media' or Media Logs report to check.
The default logging in NetBackup is to keep logs for 28 days. 

[mph999]

Although these messages are quite old:

0x00020000 0x00000000

translates to a failure of the RFA chip contained within the tape cartridge.  These tapes nee to be retired. 

[Mike_Gavrilov]

+ corresponding bptm log also has these errors