Veritas-bu

[Veritas-bu] Curious Log Entry

2007-04-24 13:12:13
Subject: [Veritas-bu] Curious Log Entry
From: brooksje at longwood.edu (Brooks, Jason)
Date: Tue, 24 Apr 2007 13:12:13 -0400
That may make sense of the issue.  The parent job that started the backup
ended with a 227 after a retry.  However, the odd part is timing.  I'm not
sure when the initial error occurred.  The Problems report also shows a 50
for the same job, so I'm guessing the bpcd termination on the client end
triggered the 150.  Not sure why they showed in the Activity Monitor.
Here's the Problems report for the client:

4/23/2007       11:20:49 PM     masterA client1 Error   83648   Backup
backup of client client1 exited with status 150 (termination requested by
administrator)
4/23/2007       11:20:49 PM     masterA client1 Error   83647   Backup
backup of client client1 exited with status 150 (termination requested by
administrator)
4/23/2007       11:20:50 PM     masterA client1 Error   83646   Backup
backup of client client1 exited with status 150 (termination requested by
administrator)
4/23/2007       11:21:15 PM     masterA client1 Error   83645   Backup
backup of client client1 exited with status 150 (termination requested by
administrator)
4/23/2007       11:22:06 PM     masterA client1 Error   83542   Backup
backup of client client1 exited with status 50 (client process aborted)
4/23/2007       11:38:54 PM     masterA client1 Error   83646   Backup
backup of client client1 exited with status 227 (no entity was found)
4/24/2007       12:34:41 AM     masterA client1 Error   83647   Backup  from
client client1: ERR - failure reading file: D:\audit\Pix\other\20070424.log
(WIN32 13: The data is invalid. )
4/24/2007       5:13:44 AM      masterA client1 Error   83647   Backup
backup of client client1 exited with status 1 (the requested operation was
partially successful)
4/24/2007       5:13:49 AM      masterA client1 Error   83542   Backup
backup of client client1 exited with status 227 (no entity was found)
4/24/2007       5:13:49 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       5:24:08 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       5:34:33 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       5:44:58 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       5:55:22 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       6:05:47 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       6:16:21 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       6:26:46 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       6:37:11 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       6:47:19 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       6:57:52 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       7:08:21 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       7:18:56 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       7:29:30 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       7:39:55 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       7:50:20 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       8:00:49 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule
4/24/2007       8:11:14 AM      masterA client1 Error   83542   Backup  [3]
backup of client client1, policy Windows_Differential-Inside, is suspended:
exceeded configured number of tries for a schedule

Thanks to all who've replied.  You've all helped sift through the issue.

Jason

> -----Original Message-----
> From: veritas-bu-bounces at mailman.eng.auburn.edu 
> [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf 
> Of Mike Heck
> Sent: Tuesday, April 24, 2007 12:23 PM
> To: veritas-bu at mailman.eng.auburn.edu
> Subject: [Veritas-bu] Curious Log Entry
> 
> I note that the 150 appears to be in All Logs entry report. 
> 
> There are reasons that a 150 can exist that are not caused by 
> end user intervention. If the Parent process sends a kill 
> signal to the child process that child process will exit with 
> a 150, however these 150s normally do not show up in the 
> Activity monitor.
> 
> That brings me to my question: What status did the job for 
> Client1 display in the Activity monitor?
> 
> If you had it enabled I would suggest looking at the trouble 
> shooting logs; Media server bpbrm, bptm (or bpdm)Client 
> bpbkar and bpcd to see if there is any reason for the 150.
> 
> Thank you,
> Mike Heck
> CFT Symantec
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu 
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3332 bytes
Desc: not available
Url : 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20070424/8ac1c9ce/smime.bin

<Prev in Thread] Current Thread [Next in Thread>