Roger Deschner wrote:
> 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 FILES
ehalf Of Huebschman,
>George J. [gjhuebsch...@lmus.leggmason.com]
>Sent: Thursday, October 15, 2009 4:46 PM
>To: ADSM-L@VM.MARIST.EDU
>Subject: Re: [ADSM-L] Querying status of a finished process
>
>Be aware that both the summary table and Event log can show false
>success
,
George J. [gjhuebsch...@lmus.leggmason.com]
Sent: Thursday, October 15, 2009 4:46 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Querying status of a finished process
Be aware that both the summary table and Event log can show false
success for scheduled backups.
I have had experience with the
] On Behalf Of
Tribe
Sent: Wednesday, October 14, 2009 8:56 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Querying status of a finished process
Hello,
I'm a beginner with TSM and this question might be very basic. However,
I wasn't able to find the answer in the documentation, so here
tor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Tribe
Sent: Wednesday, October 14, 2009 8:56 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Querying status of a finished process
Hello,
I'm a beginner with TSM and this question might be very basic. However,
I wasn't able to find th
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
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
e environment before printing this Email
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Tribe
Sent: Thursday, October 15, 2009 3:56 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Querying status of a finished process
Hello,
I'm a beginner w
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
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 co
Try this:
q actlog orig=client search=
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
> wasn
Hello,
I'm a beginner with TSM and this question might be very basic. However, I
wasn't able to find the answer in the documentation, so here's my question:
I'm using TSM 5.5 and want to run all commands through the dsmadmc command
line. I'm backing up and restoring NAS nodes.
I found ways to
12 matches
Mail list logo