I looked in the dsmsched.log there is nothing in there. (see below)
Is there any other log besides the dsmsched.log or the dsmerror.log? That we
can look at?
Thanks in advance!
7/07/2004 15:40:20 The Scheduler is under the control of the TSM Scheduler
Daemon
07/07/2004 15:40:20 Scheduler has been started by Dsmcad.
07/07/2004 15:40:20 Querying server for next scheduled event.
07/07/2004 15:40:20 Node Name: DOCCOPS
07/07/2004 15:40:21 Session established with server TSMCORE: AIX-RS/6000
07/07/2004 15:40:21 Server Version 5, Release 2, Level 0.0
07/07/2004 15:40:21 Data compression forced off by the server
07/07/2004 15:40:21 Server date/time: 07/07/2004 15:40:34 Last access:
07/07/2004 13:58:20
07/07/2004 15:40:21 --- SCHEDULEREC QUERY BEGIN
07/07/2004 15:40:21 --- SCHEDULEREC QUERY END
07/07/2004 15:40:21 Next operation scheduled:
07/07/2004 15:40:21
------------------------------------------------------------
07/07/2004 15:40:21 Schedule Name: MIDNIGHT
07/07/2004 15:40:21 Action: Incremental
07/07/2004 15:40:21 Objects:
07/07/2004 15:40:21 Options:
07/07/2004 15:40:21 Server Window Start: 00:00:01 on 07/08/2004
07/07/2004 15:40:21
------------------------------------------------------------
07/07/2004 15:40:21 Scheduler has been stopped.
07/08/2004 00:01:32 The Scheduler is under the control of the TSM Scheduler
Daemon
07/08/2004 00:01:32 Scheduler has been started by Dsmcad.
07/08/2004 00:01:32 Querying server for next scheduled event.
07/08/2004 00:01:32 Node Name: DOCCOPS
07/08/2004 00:01:32 Session established with server TSMCORE: AIX-RS/6000
07/08/2004 00:01:32 Server Version 5, Release 2, Level 0.0
07/08/2004 00:01:32 Data compression forced off by the server
07/08/2004 00:01:32 Server date/time: 07/08/2004 00:01:46 Last access:
07/07/2004 15:40:34
07/08/2004 00:01:32 --- SCHEDULEREC QUERY BEGIN
07/08/2004 00:01:32 --- SCHEDULEREC QUERY END
07/08/2004 00:01:32 Next operation scheduled:
07/08/2004 00:01:32
------------------------------------------------------------
07/08/2004 00:01:32 Schedule Name: MIDNIGHT
07/08/2004 00:01:32 Action: Incremental
07/08/2004 00:01:32 Objects:
07/08/2004 00:01:32 Options:
07/08/2004 00:01:32 Server Window Start: 00:00:01 on 07/08/2004
07/08/2004 00:01:32
------------------------------------------------------------
07/08/2004 00:01:32
Executing scheduled command now.
07/08/2004 00:01:32 --- SCHEDULEREC OBJECT BEGIN MIDNIGHT 07/08/2004 00:00:01
07/08/2004 08:03:43 The Scheduler is under the control of the TSM Scheduler
Daemon
07/08/2004 08:03:43 Scheduler has been started by Dsmcad.
07/08/2004 08:03:43 Querying server for next scheduled event.
07/08/2004 08:03:43 Node Name: DOCCOPS
07/08/2004 08:03:45 Session established with server TSMCORE: AIX-RS/6000
07/08/2004 08:03:45 Server Version 5, Release 2, Level 0.0
07/08/2004 08:03:45 Data compression forced off by the server
07/08/2004 08:03:45 Server date/time: 07/08/2004 08:03:59 Last access:
07/08/2004 00:01:47
07/08/2004 08:03:45 --- SCHEDULEREC QUERY BEGIN
07/08/2004 08:03:45 --- SCHEDULEREC QUERY END
07/08/2004 08:03:45 Next operation scheduled:
07/08/2004 08:03:45
------------------------------------------------------------
07/08/2004 08:03:45 Schedule Name: MIDNIGHT
07/08/2004 08:03:45 Action: Incremental
07/08/2004 08:03:45 Objects:
07/08/2004 08:03:45 Options:
07/08/2004 08:03:45 Server Window Start: 00:00:01 on 07/09/2004
07/08/2004 08:03:45
------------------------------------------------------------
07/08/2004 08:03:45 Scheduler has been stopped.
07/08/2004 11:20:36 The Scheduler is under the control of the TSM Scheduler
Daemon
07/08/2004 11:20:36 Scheduler has been started by Dsmcad.
07/08/2004 11:20:36 Querying server for next scheduled event.
07/08/2004 11:20:36 Node Name: DOCCOPS
07/08/2004 11:20:36 Session established with server TSMCORE: AIX-RS/6000
07/08/2004 11:20:36 Server Version 5, Release 2, Level 0.0
07/08/2004 11:20:36 Data compression forced off by the server
07/08/2004 11:20:36 Server date/time: 07/08/2004 11:20:50 Last access:
07/08/2004 10:07:48
07/08/2004 11:20:36 --- SCHEDULEREC QUERY BEGIN
07/08/2004 11:20:36 --- SCHEDULEREC QUERY END
07/08/2004 11:20:36 Next operation scheduled:
07/08/2004 11:20:36
------------------------------------------------------------
07/08/2004 11:20:36 Schedule Name: MIDNIGHT
07/08/2004 11:20:36 Action: Incremental
07/08/2004 11:20:36 Objects:
07/08/2004 11:20:36 Options:
07/08/2004 11:20:36 Server Window Start: 00:00:01 on 07/09/2004
07/08/2004 11:20:36
------------------------------------------------------------
07/08/2004 11:20:36 Scheduler has been stopped.
07/08/2004 12:54:25 The Scheduler is under the control of the TSM Scheduler
Daemon
07/08/2004 12:54:25 Scheduler has been started by Dsmcad.
07/08/2004 12:54:25 Querying server for next scheduled event.
07/08/2004 12:54:25 Node Name: DOCCOPS
07/08/2004 12:54:25 Session established with server TSMCORE: AIX-RS/6000
07/08/2004 12:54:25 Server Version 5, Release 2, Level 0.0
07/08/2004 12:54:25 Data compression forced off by the server
07/08/2004 12:54:25 Server date/time: 07/08/2004 12:54:39 Last access:
07/08/2004 11:41:29
07/08/2004 12:54:25 --- SCHEDULEREC QUERY BEGIN
07/08/2004 12:54:25 --- SCHEDULEREC QUERY END
07/08/2004 12:54:25 Next operation scheduled:
07/08/2004 12:54:25
------------------------------------------------------------
07/08/2004 12:54:25 Schedule Name: MIDNIGHT
07/08/2004 12:54:25 Action: Incremental
07/08/2004 12:54:25 Objects:
07/08/2004 12:54:25 Options:
07/08/2004 12:54:25 Server Window Start: 00:00:01 on 07/09/2004
07/08/2004 12:54:25
------------------------------------------------------------
07/08/2004 12:54:25 Scheduler has been stopped.
Troy Frank wrote:
> I would try looking in the dsmsched.log . That should have a more
> file-by-file accounting of the backup process.
>
> Troy Frank
> Network Services
> University of Wisconsin Medical Foundation
> 608.829.5384
>
> >>> Timothy.Hughes AT OIT.STATE.NJ DOT US 7/8/2004 9:01:23 AM >>>
> Hello All,
>
> First, Thanks for all the responses that I received for the
> Restoring a file from one node to another node question using the
> Gui.
>
> I know this may not be a TSM problem but we are trying to eliminate
> possible causes.
>
> One of our clients Novell servers keeps abending during it's nightly
> incremental backup, Is there a way you can tell where it is in the
> backup (i.e., last file backed up or touched)? Our client is thinking
> that perhaps it is a particular file on the volume that is causing the
> abend.
>
> There is nothing in the tsm server act. log or the dsm.error log
>
> Thanks for in advance for any suggestions/comments!
>
> Novell Tsm client version 5.2.2
> Netware OS 6.5 sp3
> Tsm server 5.2.1.3
> Aix 5.1
>
> Confidentiality Notice follows:
>
> The information in this message (and the documents attached to it, if any)
> is confidential and may be legally privileged. It is intended solely for
> the addressee. Access to this message by anyone else is unauthorized. If
> you are not the intended recipient, any disclosure, copying, distribution
> or any action taken, or omitted to be taken in reliance on it is
> prohibited and may be unlawful. If you have received this message in
> error, please delete all electronic copies of this message (and the
> documents attached to it, if any), destroy any hard copies you may have
> created and notify me immediately by replying to this email. Thank you.
|
