Steve-

What you are encountering ("the eject isn't complete until the
tapes are removed") is true for normal NBU ejects as well as 
Vault ejects.

This is always true for ACSLS robots due to the nature of 
ACSLS ejects, and in the name of consistency the same requirement 
exists for non-ACSLS robots as well.

Because vault doesn't produce the reports until AFTER the
ejects have completed, I bet your your operators are in need 
of a "trigger" to remove ejected tapes from the robot. 
Assuming that you are running NBU 4.5 FP5/6 or NBU 5.x, there 
is a "vlt_starteject_notify" script that can be used for this 
exact purpose.  There is an example script in 
/usr/openv/netbackup/bin/goodies/

HTH
rob


On Fri, Jun 25, 2004 at 12:22:12PM -0400 or thereabouts, Steve Mickeler wrote:
> We have 2  vault profiles. A duplication profile and an eject profile.
> 
> When the eject profile runs, it ejects the tapes into the CAP of the
> L700 but the vault eject profile wont send the emails that this is
> finished until the tapes are removed from the CAP.
> 
> The follow messages appear in the system logs until this is done:
> 
> Jun 24 18:01:07 harbor acsd[14514]: [ID 957372 daemon.notice]
> DecodeExternal() Actual status: STATUS_SUCCESS
> 
> Jun 24 18:01:37 harbor acsd[152]: [ID 491975 daemon.warning] ACS(0)
> Response has not been returned by Eject command sequence 1702, ACS
> status = 72, STATUS_PENDING
> 
> The "DecodeExternal() Actual status: STATUS_SUCCESS" will repeat every
> 30 seconds and then every 5 minutes the " Eject command sequence 1702,
> ACS status = 72, STATUS_PENDING" will appear.
> 
> This is starting to cause other problems such as other tapes being
> ejected into the CAP to fail as it wont allow that to happen until the
> vaulted tapes are removed from the CAP first.
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu