ADSM-L

Re: Help with messages please !!!

2000-02-02 08:16:31
Subject: Re: Help with messages please !!!
From: Steven P Roder <tkssteve AT REXX.ACSU.BUFFALO DOT EDU>
Date: Wed, 2 Feb 2000 08:16:31 -0500
On Tue, 1 Feb 2000, Dann Fred wrote:
> Joyce,
>   If this was a scheduled backup you can look at the DSMSCHED.LOG for the file
> name.  In Unix the schedule log is located in /usr/lpp/adsm/bin.

Joyce,

     I think that if you do a more complete scan of the actlog for this
client's session, that you will find what object failed.  If you are not
excluding the client schedlog, then it is probably that file ;-)

Also, note that your schedule ended with RC=4.  This is not caused by the
failed object, but rather a filesystem also failed to backup, perhaps due
to a stale NFS mountpoint.  You can find out the problem via the schedlog
on the client (and probably the actlog too).  A quick test would be to
login to the machine, and issue the command "df" to see if it hangs, or
returns info. about a stale NFS filesystem...

Failed objects do not cause the schedule to be marked as failed...

Hope this helps,

>
> I have a couple of questions.....  In the activity log where it says that 1
> object failed.  I'm guessing I am supposed to look on the client
>  to find out exactly what object was not backed up.  But where ...Help???
>
> Thanks,
> Joyce
>
> Actitvity Log
> -------------
> Date and Time       Message
>
>
> --------------------------------------------------------------------------------
> -------------------------------
>
> 02/01/2000 02:23:37 ANR0406I Session 244 started for node KUJIRA (SUN SOLARIS)
> (Tcp/Ip 198.80.170.3(-27672)).
> 02/01/2000 02:56:38 ANE4952I (Session: 244, Node: KUJIRA)  Total number of
> objects inspected:   59,441
> 02/01/2000 02:56:38 ANE4954I (Session: 244, Node: KUJIRA)  Total number of
> objects backed up:    1,124
> 02/01/2000 02:56:38 ANE4958I (Session: 244, Node: KUJIRA)  Total number of
> objects updated:          1
> 02/01/2000 02:56:38 ANE4960I (Session: 244, Node: KUJIRA)  Total number of
> objects rebound:          0
> 02/01/2000 02:56:38 ANE4957I (Session: 244, Node: KUJIRA)  Total number of
> objects deleted:        867
> 02/01/2000 02:56:38 ANE4959I (Session: 244, Node: KUJIRA)  Total number of
> objects failed:           1
> 02/01/2000 02:56:38 ANE4961I (Session: 244, Node: KUJIRA)  Total number of 
> bytes
>  transferred:     4.90 GB
> 02/01/2000 02:56:38 ANE4963I (Session: 244, Node: KUJIRA)  Data transfer time:
>                 1,679.12 sec
> 02/01/2000 02:56:38 ANE4966I (Session: 244, Node: KUJIRA)  Network data 
> transfer
>  rate:        3,063.61 KB/sec
> 02/01/2000 02:56:38 ANE4967I (Session: 244, Node: KUJIRA)  Aggregate data
> transfer rate:      2,597.78 KB/sec
> 02/01/2000 02:56:38 ANE4968I (Session: 244, Node: KUJIRA)  Objects compressed
> by:                    0%
> 02/01/2000 02:56:38 ANE4964I (Session: 244, Node: KUJIRA)  Elapsed processing
> time:            00:33:00
> 02/01/2000 02:56:38 ANR2579E Schedule FILESYS_UNIX in domain FILESYS for node
> KUJIRA failed (return code 4).


Steve Roder, University at Buffalo
VM Systems Programmer
UNIX Systems Administrator (Solaris and AIX)
ADSM Administrator
(tkssteve AT buffalo DOT edu | (716)645-3564 | 
http://ubvm.cc.buffalo.edu/~tkssteve)
<Prev in Thread] Current Thread [Next in Thread>