Vault Eject Fails With Status 287

Vault Eject Fails With Status 287

Article: 100046587
Last Published: 2019-11-08
Ratings: 0 0
Product(s): NetBackup

Problem

Deferred Ejection Fails With Status 287

Error Message

Detailed Status of Vault Job shows : Vault eject failed  (287)

With the vault log errors such as the following are observed:

<2> vlteject@VaultScsiRobot::doStartEject(): Adding: C12345, BC=UNKNOWN, RobSlt=17, MailSlt=-1, Cyc=-1, MAILSLOT_STATUS_ABORTED_EJECT (8) to mailSlotList, PIPESerrno=0
<2> vlteject@VaultScsiRobot::doStartEject(): Adding: C67890, BC=UNKNOWN, RobSlt=28, MailSlt=-1, Cyc=-1, MAILSLOT_STATUS_ABORTED_EJECT (8) to mailSlotList, PIPESerrno=0
<2> vlteject@VaultScsiRobot::doStartEject(): Adding: C24680, BC=UNKNOWN, RobSlt=9, MailSlt=-1, Cyc=-1, MAILSLOT_STATUS_ABORTED_EJECT (8) to mailSlotList, PIPESerrno=0

And Reviewing the Media Manager Robots log messages such as the following are observed:

<6> tldcd:read_element_status_all_mailslots: read 3 mailslots' element status at element address 16
<6> tldcd:read_element_status_all_mailslots: count the empty mailslots
<6> tldcd: mailslot 1 is unknown, access=0, assuming full
<6> tldcd: mailslot 2 is unknown, access=0, assuming full
<6> tldcd: mailslot 3 is unknown, access=0, assuming full


Cause

Because the Robot MAP or I/O ports have been left open NetBackup assumes the mailslots are full and is unable to eject further media

Solution

Ensure MAP is closed before proceeding with Vault eject.  The MAP should be closed after media is ejected.

Was this content helpful?