Probably the biggest gripes that I have against TSM. Having dealt
with other Backup vendors, Tivoli is very good at batching things, but
it is difficult to follow a single process, or backup for that matter
through to completion. You may be used to other tools that allow you
to see completion
Why not just look at the QUERY EVENT command.
Bill
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Yudi Darmadi
Sent: Wednesday, October 14, 2009 11:35 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Querying status of a finished process
Try this:
q
Try q act se=Process ID begind=date begint=time
Grigori G. Solonovitch
Senior Technical Architect
Information Technology Bank of Kuwait and Middle East http://www.bkme.com
Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com
Please consider the environment before
TSM's query events will report success even though the backup may have
skipped some files that were locked or open. I think many people ignore
skipped files. But when building Servergraph, we added thorough
skipped-file analysis, and were surprised at what our customers found.
It turns out that
Lindsay offers good advice on skipped files, and the part they play in
how a backup went. Too often, sites try to evaluate backups from
standpoint of the TSM server. That's unhealthy, and can result in
many missed files - which come dramatically to light when a crunch
occurs and restore doesn't
Be aware that both the summary table and Event log can show false
success for scheduled backups.
I have had experience with the summary table showing success for backups
where the actlog shows failure. IBM tells me that it is working as
designed.
I have not had experience with false success in
I run a script every morning to look for failed files by issuing a select
statement that looks for msgno's 4005, 4007, 4018, 4037, 4042, and 4987.
Johnny
Huebschman, George J. gjhuebsch...@lmus.leggmason.com 10/15/2009 8:46
AM
Be aware that both the summary table and Event log can show
We are running VSS based backups (SYSTEMSTATE, etc). Quite often there are VSS
problems during backups. We are installing VSS patches, but VSS is still a
source of problems.
TSM Client gives normal completion in this case and event is mensioned as
successfull. I have found only one way to
This is always a puzzle, and the best I've come up with is the backup
completion timestamps for each filespace, as reported by either:
* Linemode Client QUERY FILESPACE command (This valuable information is
not available in the GUI client - why?)
* Server Q FILESPACE F=D. I have written a script
Try this:
q actlog orig=client search=node_name
or using select statement:
SELECT
START_TIME,END_TIME,ACTIVITY,ENTITY,EXAMINED,AFFECTED,FAILED,BYTES,SUCCESSFULL
FROM SUMMARY WHERE ENTITY='node_name'
Rgrds,
Yudi
Hello,
I'm a beginner with TSM and this question might be very basic. However, I
10 matches
Mail list logo
