Strange Behaviour

[rallingham]

If I have a backup session currently running and from the admin command line I run a q eve * * begind=-1 f=d I get output that suggests the session or backup job has failed.

tsm: TSM_SERVER1>q eve * * begind=-1 f=d

Policy Domain Name: DOM1
Schedule Name: NIGHTLY_DSK_BKUP
Node Name: TSMSERV
Scheduled Start: 12/12/2010 18:06:00
Actual Start: 12/12/2010 18:09:42
Completed: 12/13/2010 08:17:53
Status: Failed
Result: 0
Reason:

Once the job/session/backup has finished I get the correct outuput.

tsm: TSM_SERVER1>q eve * * begind=-1 f=d

Policy Domain Name: DOM1
Schedule Name: NIGHTLY_DSK_BKUP
Node Name: TSMSERV
Scheduled Start: 12/12/2010 18:06:00
Actual Start: 12/12/2010 18:09:42
Completed: 12/13/2010 11:17:53
Status: Completed
Result: 0
Reason: All operations completed successfully.

Has anyone else seen this behaviour? It is not critical just strange. I know enough to go to the client and check things out before rerunning any backup job manually.

 

[rallingham]

Has no one seen this? It is hard to believe that I am the only one to cross this path.

 

[gimlet]

Have you checked the activity logs to see if the job is failing and then being retried?

 

[mahmurth]

We have observed this problem before in TSM, even if the schedlog shows the backup completed with out any failures, but when checked in TSM server event status shows failed with -99, think it should be a bug.