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.Solonovitch AT bkme
DOT com
Please consider the environment before printing this Email
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tribe
Sent: Thursday, October 15, 2009 3:56 AM
To: ADSM-L AT VM.MARIST DOT 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 mail AT janseidel DOT net via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT 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."
|
