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 rogerd AT uic DOT 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 [ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
>Huebschman, George J. [GJHuebschman AT LMUS.LEGGMASON DOT COM]
>Sent: Thursday, October 15, 2009 4:46 PM
>To: ADSM-L AT VM.MARIST DOT 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: AIXPROD65>server1xyz: 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/Time Message
>--------------------
>----------------------------------------------------------
>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:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
>Tribe
>Sent: Wednesday, October 14, 2009 8:56 PM
>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.
>+----------------------------------------------------------------------
>
>IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason
>therefore recommends that you do not send any confidential or sensitive
>information to us via electronic mail, including social security numbers,
>account numbers, or personal identification numbers. Delivery, and or timely
>delivery of Internet mail is not guaranteed. Legg Mason therefore recommends
>that you do not send time sensitive
>or action-oriented messages to us via electronic mail.
>
>This message is intended for the addressee only and may contain privileged or
>confidential information. Unless you are the intended recipient, you may not
>use, copy or disclose to anyone any information contained in this message. If
>you have received this message in error, please notify the author by replying
>to this message and then kindly delete the message. Thank you.
>
>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."
>
|
