They don't expire; but if somebody does something to delete those tapes
from TSM, yes DRM will lose track of them:
- somebody runs a DELETE VOLHIST for the DBbackup or DBSnapshot tapes
- somebody runs a MOVE DRMEDIA for the stgpool tapes
- somebody runs a DELETE VOLUME with
I don't think the 2 things are related at all, I've seen them happen
independently.
It's inconvenient I know, but I wouldn't spend more time on it until you've
tried a reboot.
Sometimes that clears up the ASR backup failure.
On 6/20/08, Zoltan Forray/AC/VCU [EMAIL PROTECTED] wrote:
TSM
Ditto.
John, there is nothing in the 3584 or in TSM that will give you what you
want, if the tapes are ejected for vaulting and leave the 3584.
The only way we're going to get this info, is if somebody provides an API to
read from the cartridge chip. I'm kinda suprised nobody has done that yet
On Jun 21, 2008, at 10:12 AM, Wanda Prather wrote:
The only way we're going to get this info, is if somebody provides
an API to
read from the cartridge chip. I'm kinda suprised nobody has done
that yet
-- except as Tom says, the cartridges tend to last a long time anyway.
As noted in ADSM
The TS3500 internal web server provides some information about the
cartridges. Not sure what they really means.
It does tell you the number of read and write errors for both LTO and
3592 cartridges from the cartridge memory.
Go to your TS3500 library internal web server
Expand +Cartridges
Select
I know, I just hate manual processes.
What I want is an API so that we can get that sort of info back to the host
in an automated fashion.
I want to be able to run something like:
audit volume * report(medialife)
or
audit volume * report=EXCEPTIONSONLY
(wouldn't that be cool?)
On 6/21/08,
It would probably have to be associated with a libvol instead of a
volume. Volumes get created and deleted as they move out of and back into
the scratch pool. I'd like to see the stats that are currently associated
with volumes instead associated with libvols (mounts, read and write
errors,
