Re: Querying status of a finished process
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 codes and event output sorted by job or process. Unfortunately TSM does not do this. You are stuck querying actlog or running SQL or using any of the fine reporting tools out there. Most of us have created shortcut scripts for this. I don't have mine readily available, but if you ask nice, or search the archives, I'm sure you'll find what you need. Gary Bowers Itrus Technologies On Oct 14, 2009, at 7:55 PM, Tribe wrote: 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 start backups and query running processes (query process ID), but I don't know how to query the status of finished processes. I just want a simple way to figure out if a backup / restore was successful. If I use the query process ID after the job finished, it just tells me Process cannot be found. There must be a simple way to do that, right? I know that I can query the actlog, but is there a better / easier way to do this, given a process id? Thanks, Jan + -- |This was sent by m...@janseidel.net via Backup Central. |Forward SPAM to ab...@backupcentral.com. + --
Re: Querying status of a finished process
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 actlog orig=client search=node_name or using select statement: SELECT START_TIME,END_TIME,ACTIVITY,ENTITY,EXAMINED,AFFECTED,FAILED,BYTES,SUCCESSFU LL 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'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 start backups and query running processes (query process ID), but I don't know how to query the status of finished processes. I just want a simple way to figure out if a backup / restore was successful. If I use the query process ID after the job finished, it just tells me Process cannot be found. There must be a simple way to do that, right? I know that I can query the actlog, but is there a better / easier way to do this, given a process id? Thanks, Jan +-- |This was sent by m...@janseidel.net via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: Querying status of a finished process
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 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 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 start backups and query running processes (query process ID), but I don't know how to query the status of finished processes. I just want a simple way to figure out if a backup / restore was successful. If I use the query process ID after the job finished, it just tells me Process cannot be found. There must be a simple way to do that, right? I know that I can query the actlog, but is there a better / easier way to do this, given a process id? Thanks, Jan +-- |This was sent by m...@janseidel.net via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- Please consider the environment before printing this Email. This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME.
Re: Querying status of a finished process
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 the skipped files alert you to databases that are active during backup (thus can't be backed up consistently). This seems to be a common problem. Your user community doesn't know that databases need special treatment; you DO know that, but you don't know when someone installs a new application and its database. It's (my second-favorite phrase) a built-in organizational disconnect. On Wed, Oct 14, 2009 at 8:55 PM, Tribe tsm-fo...@backupcentral.com wrote: 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 start backups and query running processes (query process ID), but I don't know how to query the status of finished processes. I just want a simple way to figure out if a backup / restore was successful. If I use the query process ID after the job finished, it just tells me Process cannot be found. There must be a simple way to do that, right? I know that I can query the actlog, but is there a better / easier way to do this, given a process id? Thanks, Jan +-- |This was sent by m...@janseidel.net via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- Lindsay Morris Principal TSMworks Tel. 1-859-539-9900 lind...@tsmworks.com
Re: Querying status of a finished process
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 restore all that was expected. It's natural to want the quick, binary answer to the question, Was node X's backup successful? But the volume of data involved in a backup does not lend itself to a yes/no answer. Many things can be problematic in a backup, from performance problems in retries of busy files, to files not participating in Linux backups because of character set differences from the client's locale setting, to unintended excludes, or overlooking the need to add DOMain specs for new file systems. If you don't scan the backup and dsmerror.log (via locally written utilities or commercial packages) and compare that to the realities of your file systems, you're not going to see such issues, and may be lulled into a false sense of security. This is to say that the TSM server is not the place to evaluate backups: that needs to be done on the client, by the client administrator, who is responsible for the data. Richard Sims at Boston University
Re: 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 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 the Event log, but Wanda tells me that it is so and I believe her. Richard Sims is correct, though. The things you find in the server tell you about definite problems. Much of what the server knows about client activity is based on what the Client reports back. The Client does not fail backups just because files fail. Where I am going with this is, that if you want to look at a report on the server of Missed/Failed, look deeper. If something Misses or Fails, you know you have a problem. But, just because you have successful backups, does not me there is no problem. You can query the actlog as follows and get information like this, which comes from the Client. Even that will not identify many of the things Richard mentioned. If you have excluded a directory or domain, the Client will smilingly report success. tsm: AIXPROD65server1xyz: q act node=ClientServerXYZ begind=-2 ANR1699I Resolved server1xyz to 1 server(s) - issuing command Q ACT NODE=ClientServerXYZ BEGIND=-2 against server(s). ANR1687I Output for command 'Q ACT NODE=ClientServerXYZ BEGIND=-2 ' issued against server server1xyz follows: Date/TimeMessage -- 10/13/2009 09:26:17 ANE4005E (Session: 2495820, Node: ClientServerXYZ) Error processing '\\somefiler\somedept\Users\someuser\ABC_9.2.0 - Serusaem NainocarD\ABC\CMA\CYA\stardotext_someuser_20034- .xls': file not found 10/13/2009 11:06:32 ANE4952I (Session: 2491225, Node: ClientServerXYZ) Total number of objects inspected: 8,690,541 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4954I (Session: 2491225, Node: ClientServerXYZ) Total number of objects backed up: 14,904 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4958I (Session: 2491225, Node: ClientServerXYZ) Total number of objects updated: 0 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4960I (Session: 2491225, Node: ClientServerXYZ) Total number of objects rebound: 0 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4957I (Session: 2491225, Node: ClientServerXYZ) Total number of objects deleted: 0 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4970I (Session: 2491225, Node: ClientServerXYZ) Total number of objects expired: 1,936 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4959I (Session: 2491225, Node: ClientServerXYZ) Total number of objects failed: 4 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4965I (Session: 2491225, Node: ClientServerXYZ) Total number of subfile objects: 0 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4961I (Session: 2491225, Node: ClientServerXYZ) Total number of bytes transferred: 40.36 GB (SESSION: 2491225) 10/13/2009 11:06:32 ANE4963I (Session: 2491225, Node: ClientServerXYZ) Data transfer time: 711.79 sec (SESSION: 2491225) 10/13/2009 11:06:32 ANE4966I (Session: 2491225, Node: ClientServerXYZ) Network data transfer rate:59,465.00 KB/sec (SESSION: 2491225) 10/13/2009 11:06:32 ANE4967I (Session: 2491225, Node: ClientServerXYZ) Aggregate data transfer rate:725.91 KB/sec (SESSION: 2491225) 10/13/2009 11:06:32 ANE4968I (Session: 2491225, Node: ClientServerXYZ) Objects compressed by:0% (SESSION: 2491225) 10/13/2009 11:06:32 ANE4969I (Session: 2491225, Node: ClientServerXYZ) Subfile objects reduced by: 0% (SESSION: 2491225) 10/13/2009 11:06:32 ANE4964I (Session: 2491225, Node: ClientServerXYZ) Elapsed processing time:16:11:47 (SESSION: 2491225) -Original Message- From: ADSM: Dist Stor 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 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 start backups and query running processes
Re: Querying status of a finished process
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 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 the Event log, but Wanda tells me that it is so and I believe her. Richard Sims is correct, though. The things you find in the server tell you about definite problems. Much of what the server knows about client activity is based on what the Client reports back. The Client does not fail backups just because files fail. Where I am going with this is, that if you want to look at a report on the server of Missed/Failed, look deeper. If something Misses or Fails, you know you have a problem. But, just because you have successful backups, does not me there is no problem. You can query the actlog as follows and get information like this, which comes from the Client. Even that will not identify many of the things Richard mentioned. If you have excluded a directory or domain, the Client will smilingly report success. tsm: AIXPROD65server1xyz: q act node=ClientServerXYZ begind=-2 ANR1699I Resolved server1xyz to 1 server(s) - issuing command Q ACT NODE=ClientServerXYZ BEGIND=-2 against server(s). ANR1687I Output for command 'Q ACT NODE=ClientServerXYZ BEGIND=-2 ' issued against server server1xyz follows: Date/TimeMessage -- 10/13/2009 09:26:17 ANE4005E (Session: 2495820, Node: ClientServerXYZ) Error processing '\\somefiler\somedept\Users\someuser\ABC_9.2.0 - Serusaem NainocarD\ABC\CMA\CYA\stardotext_someuser_20034- .xls': file not found 10/13/2009 11:06:32 ANE4952I (Session: 2491225, Node: ClientServerXYZ) Total number of objects inspected: 8,690,541 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4954I (Session: 2491225, Node: ClientServerXYZ) Total number of objects backed up: 14,904 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4958I (Session: 2491225, Node: ClientServerXYZ) Total number of objects updated: 0 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4960I (Session: 2491225, Node: ClientServerXYZ) Total number of objects rebound: 0 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4957I (Session: 2491225, Node: ClientServerXYZ) Total number of objects deleted: 0 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4970I (Session: 2491225, Node: ClientServerXYZ) Total number of objects expired: 1,936 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4959I (Session: 2491225, Node: ClientServerXYZ) Total number of objects failed: 4 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4965I (Session: 2491225, Node: ClientServerXYZ) Total number of subfile objects: 0 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4961I (Session: 2491225, Node: ClientServerXYZ) Total number of bytes transferred: 40.36 GB (SESSION: 2491225) 10/13/2009 11:06:32 ANE4963I (Session: 2491225, Node: ClientServerXYZ) Data transfer time: 711.79 sec (SESSION: 2491225) 10/13/2009 11:06:32 ANE4966I (Session: 2491225, Node: ClientServerXYZ) Network data transfer rate:59,465.00 KB/sec (SESSION: 2491225) 10/13/2009 11:06:32 ANE4967I (Session: 2491225, Node: ClientServerXYZ) Aggregate data transfer rate:725.91 KB/sec (SESSION: 2491225) 10/13/2009 11:06:32 ANE4968I (Session: 2491225, Node: ClientServerXYZ) Objects compressed by:0% (SESSION: 2491225) 10/13/2009 11:06:32 ANE4969I (Session: 2491225, Node: ClientServerXYZ) Subfile objects reduced by: 0% (SESSION: 2491225) 10/13/2009 11:06:32 ANE4964I (Session: 2491225, Node: ClientServerXYZ) Elapsed processing time:16:11:47 (SESSION: 2491225) -Original Message- From: ADSM: Dist Stor 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 the
Re: Querying status of a finished process
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 report problems with VSS - check number of backed up bytes. Usually it is 0 after VSS problem. Checking event status and number of backed up files gives better results in my opinion. From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf 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 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 the Event log, but Wanda tells me that it is so and I believe her. Richard Sims is correct, though. The things you find in the server tell you about definite problems. Much of what the server knows about client activity is based on what the Client reports back. The Client does not fail backups just because files fail. Where I am going with this is, that if you want to look at a report on the server of Missed/Failed, look deeper. If something Misses or Fails, you know you have a problem. But, just because you have successful backups, does not me there is no problem. You can query the actlog as follows and get information like this, which comes from the Client. Even that will not identify many of the things Richard mentioned. If you have excluded a directory or domain, the Client will smilingly report success. tsm: AIXPROD65server1xyz: q act node=ClientServerXYZ begind=-2 ANR1699I Resolved server1xyz to 1 server(s) - issuing command Q ACT NODE=ClientServerXYZ BEGIND=-2 against server(s). ANR1687I Output for command 'Q ACT NODE=ClientServerXYZ BEGIND=-2 ' issued against server server1xyz follows: Date/TimeMessage -- 10/13/2009 09:26:17 ANE4005E (Session: 2495820, Node: ClientServerXYZ) Error processing '\\somefiler\somedept\Users\someuser\ABC_9.2.0 - Serusaem NainocarD\ABC\CMA\CYA\stardotext_someuser_20034- .xls': file not found 10/13/2009 11:06:32 ANE4952I (Session: 2491225, Node: ClientServerXYZ) Total number of objects inspected: 8,690,541 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4954I (Session: 2491225, Node: ClientServerXYZ) Total number of objects backed up: 14,904 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4958I (Session: 2491225, Node: ClientServerXYZ) Total number of objects updated: 0 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4960I (Session: 2491225, Node: ClientServerXYZ) Total number of objects rebound: 0 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4957I (Session: 2491225, Node: ClientServerXYZ) Total number of objects deleted: 0 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4970I (Session: 2491225, Node: ClientServerXYZ) Total number of objects expired: 1,936 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4959I (Session: 2491225, Node: ClientServerXYZ) Total number of objects failed: 4 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4965I (Session: 2491225, Node: ClientServerXYZ) Total number of subfile objects: 0 (SESSION: 2491225) 10/13/2009 11:06:32 ANE4961I (Session: 2491225, Node: ClientServerXYZ) Total number of bytes transferred: 40.36 GB (SESSION: 2491225) 10/13/2009 11:06:32 ANE4963I (Session: 2491225, Node: ClientServerXYZ) Data transfer time: 711.79 sec (SESSION: 2491225) 10/13/2009 11:06:32 ANE4966I (Session: 2491225, Node: ClientServerXYZ) Network data transfer rate:59,465.00 KB/sec (SESSION: 2491225) 10/13/2009 11:06:32 ANE4967I (Session: 2491225, Node: ClientServerXYZ) Aggregate data transfer rate:725.91 KB/sec (SESSION: 2491225) 10/13/2009 11:06:32 ANE4968I (Session: 2491225, Node: ClientServerXYZ) Objects compressed by:0% (SESSION: 2491225) 10/13/2009 11:06:32 ANE4969I (Session: 2491225, Node: ClientServerXYZ) Subfile objects reduced by:
Re: Querying status of a finished process
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 to make this easier to
look at. (below)
This is still imperfect, because if you do a partial backup using the
GUI client, and choose only some directories within a filespace, then
the filespace backup completion timestamp does NOT get updated, even
though the SUMMARY table will show success for such a partial backup.
There are other ways this filespace backup completion data can be an
imprefect indicator of the success or failure of a backup. Nevertheless,
these filespace backup completion timestamps are the most reliable thing
available to tell whether or not the backup really worked.
Here's the script I use: (v5.5 server)
/* Script QBACK */
/* Q FILESPACE with dates showing */
/* Argument may be lower or upper case */
/* 2007-11-14 - Roger Deschner, University of Illinois at Chicago */
set sqldisplaymode wide
select -
CAST(filespace_id AS CHAR(2)) AS ID, -
CAST(filespace_name AS CHAR(40)) AS FS Name, -
CAST(filespace_type AS CHAR(8)) AS FS Type, -
CAST(SUBSTRING(CAST(backup_start AS CHAR(26)) FROM 1 FOR 16) AS CHAR(16)) AS
Started, -
CAST(SUBSTRING(CAST(backup_end AS CHAR(26)) FROM 1 FOR 16) AS CHAR(16)) AS
Ended -
from adsm.filespaces where node_name=UPPER('$1') ORDER BY 5 DESC
Roger Deschner University of Illinois at Chicago rog...@uic.edu
==I have not lost my mind -- it is backed up on tape somewhere.=
On Fri, 16 Oct 2009, Grigori Solonovitch wrote:
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 report problems with VSS - check
number of backed up bytes. Usually it is 0 after VSS problem. Checking event
status and number of backed up files gives better results in my opinion.
From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf 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 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 the Event log, but Wanda
tells me that it is so and I believe her.
Richard Sims is correct, though. The things you find in the server tell
you about definite problems. Much of what the server knows about client
activity is based on what the Client reports back. The Client does not
fail backups just because files fail. Where I am going with this is,
that if you want to look at a report on the server of Missed/Failed,
look deeper. If something Misses or Fails, you know you have a problem.
But, just because you have successful backups, does not me there is no
problem.
You can query the actlog as follows and get information like this, which
comes from the Client. Even that will not identify many of the things
Richard mentioned. If you have excluded a directory or domain, the
Client will smilingly report success.
tsm: AIXPROD65server1xyz: q act node=ClientServerXYZ begind=-2
ANR1699I Resolved server1xyz to 1 server(s) - issuing command Q ACT
NODE=ClientServerXYZ BEGIND=-2 against server(s).
ANR1687I Output for command 'Q ACT NODE=ClientServerXYZ BEGIND=-2 '
issued against server server1xyz follows:
Date/TimeMessage
--
10/13/2009 09:26:17 ANE4005E (Session: 2495820, Node:
ClientServerXYZ) Error
processing
'\\somefiler\somedept\Users\someuser\ABC_9.2.0 -
Serusaem
NainocarD\ABC\CMA\CYA\stardotext_someuser_20034-
.xls': file not found
10/13/2009 11:06:32 ANE4952I (Session: 2491225, Node:
ClientServerXYZ) Total
number of objects inspected: 8,690,541
(SESSION: 2491225)
10/13/2009 11:06:32 ANE4954I (Session: 2491225, Node:
ClientServerXYZ) Total
number of objects backed up: 14,904
(SESSION: 2491225)
10/13/2009 11:06:32 ANE4958I (Session: 2491225, Node:
ClientServerXYZ) Total
number of objects updated: 0
(SESSION: 2491225)
10/13/2009 11:06:32 ANE4960I (Session: 2491225, Node:
ClientServerXYZ) Total
number of objects rebound: 0
(SESSION: 2491225)
10/13/2009 11:06:32
Re: Querying status of a finished process
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 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 start backups and query running processes (query process ID), but I don't know how to query the status of finished processes. I just want a simple way to figure out if a backup / restore was successful. If I use the query process ID after the job finished, it just tells me Process cannot be found. There must be a simple way to do that, right? I know that I can query the actlog, but is there a better / easier way to do this, given a process id? Thanks, Jan +-- |This was sent by m...@janseidel.net via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
