Vault Problems
just to start off i have a case open with symantec already that is getting closed due to no fix till 6.5.4 MAYBE
So i wanted to know if anyone else is seeing this issue:
The vlteject.mstr file does not update like so
0/vault1/daily|1656|1237228970|1237228970|1237035608|12143107|1237228970
0/vault1/daily|1657|1237228970|1237228970|1237122021|12150734|1237228970
0/vault1/daily|1658|0|0|1237208407|12160616|1237489374
0/vault1/daily|1659|0|0|1237294928|12170631|1237489374
0/vault1/daily|1660|0|0|1237381208|12179603|1237489374
0/vault1/daily|1661|0|0|1237467613|12188533|1237489374
This is causing the reports to be mailed hours later then normal. So we were thinking about trying to suspend tapes when vault begins(Catalog backup step) and get all the media before ejects start. But does anyone know of anyway to get a preview of the media being ejected today?
vlteject -preview -profile <profile> only shows media that was missed on the last vault runs. Nothing that will be ejected.
Any help would be gretly appreciated.
bpimagelist identifies media
Media Written Report
The Media Written report identifies volumes that were used for backups within the specified time period.
# cd /usr/openv/netbackup/bin/admincmd
# ./bpimagelist -A -media [-d <start_date> <start_time> -e <end_date> <end_time>]
Bob Stump
VERITAS - "Ain't it the truth?"
Incorrigible punster -- Do not incorrige
The list this query provides
The list this query provides has almost triple the amount of tapes that are to be ejected... is there any other way?
I would fight with Symantec
I would fight with Symantec to get an emergency binary instead of waiting for 6.5.4. Their QA on their software is horrid and it shows.
Regards,
Benjamin Schmaus
Would you like to reply?
Login or Register to post your comment.