DisgrntldVeritasUser
Technical User
Im running 3.4_5 on a Solaris 8 master. Im using vault only to eject original tapes and not to make copies. Anyone seen his!
1. Vault sessions are ran and tape 123xyz is set to go into the vault until day a/b/2003.
2. When volumes are filtered from the Media Managment gui to show only tapes that are offsite and not assigned tape 123xyz appears as unassigned before day a/b/2003!
3. When vault is ran before day a/b/2003 tape 123xyz is never requested to come back from offsite, as it should not.
Now this tape is in an unassigned state reflected from the media managment gui, yet vault does not request the tape to be re-entered into the robot.
If bpimmedia -L -mediaid 123xyz is ran backupid return as vailid images on the tape.
??? If this tape was taken from the Vault before it was requested and returned to the robot, would the data be written over since the tape is unassigned?????
Why would a tape be unassigned when there are still valid images on the tape??????
This seems to happen occasionally, and only a couple days before the images actually expire.
1. Vault sessions are ran and tape 123xyz is set to go into the vault until day a/b/2003.
2. When volumes are filtered from the Media Managment gui to show only tapes that are offsite and not assigned tape 123xyz appears as unassigned before day a/b/2003!
3. When vault is ran before day a/b/2003 tape 123xyz is never requested to come back from offsite, as it should not.
Now this tape is in an unassigned state reflected from the media managment gui, yet vault does not request the tape to be re-entered into the robot.
If bpimmedia -L -mediaid 123xyz is ran backupid return as vailid images on the tape.
??? If this tape was taken from the Vault before it was requested and returned to the robot, would the data be written over since the tape is unassigned?????
Why would a tape be unassigned when there are still valid images on the tape??????
This seems to happen occasionally, and only a couple days before the images actually expire.
