cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup Vault - no tapes to eject

sensfan
Not applicable

Our tape library had a serious problem that required most of the internals to be replaced.

Since then, the backup jobs run and backup to tape fine.  The vault job runs and the data is duplicated but it says there is no tapes to eject.  When we try to run several of the reports, it fails saying the tapes have not been ejected yet.

Under Reports, Vault Reports, Non-vaulted images, there are a number of tapes that need to be ejected.

We have stopped the services, rebooted the media and master server, rebooted the robot and completely recreated the vault and polices.

I know we can manualy remove tapes from the robot inject new tapes but it is only a temporary solution.

This setup has been working for several years.

Netbackup 6.5.4

Thanks

4 REPLIES 4

Mark_Solutions
Level 6
Partner Accredited Certified

Hi

The vault itself is written to:

\Program Files\veritas\netbackup\db\vault\vault.xml

It is worth looking at that file just in case something has been retained in it from a previous creation.

The Vault runs store their logs under:

\Program Files\Veritas\NetBackup\vault\sessions\

there are file in there to take a look at especially when you dig down into one of your sessions where the logs live - the answer may be in there.

It could of course be something related to your media already being assigned to "another" vault so they may all have to be cleared first to start using them in the "new" vault (even if it has the same name.

Hope this helps 

Mark_Solutions
Level 6
Partner Accredited Certified

did you get anywhere with this - have you resolved it?

watsons
Level 6

When you said replacement of robot, did you make the robot the same # as previously configured?

Say for example, before the replacement, your robot is TLD(0) and your profile is associated with it.

After replacement, if your new robot is now TLD(1), the existing profile won't eject tapes for you - obviously because your profile was associated with TLD(0). In this case, you need to reconfigure your robot to be TLD(0).

If the robot # remains the same, you need to check in session log (detail.log) to find out why. You did not tell us if you use immediate or deferred eject. If it is deferred eject, we need to check a file (vlteject.mstr) to find out whether your tapes are ejected in the past and marked by Vault.

Marianne
Level 6
Partner    VIP    Accredited Certified

New list member, 1 post, never came back to check for advice.......... frown