Re: [Veritas-bu] Curious Log Entry
I have the same - NB60MP4 on Win2KSP2. This has happened a couple of times to me. I found the Job Manager Service failed on me at the time. Windows restarted it automatically, but any running jobs ended with a 150 but certainly weren't cancelled. This has happened when the server wasn't stressed although I didn't check memory usage at the time. Only 2 jobs were running. I haven't bothered investigating further as I've only seen this twice and it didn't have much of an impact. On 4/24/07, Brooks, Jason <[EMAIL PROTECTED]> wrote: Sorry - NBU 6.0MP4, Windows 2K3SP2 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Greenberg, Katherine (ISD, IT) > Sent: Tuesday, April 24, 2007 11:10 AM > To: Brooks, Jason; veritas-bu@mailman.eng.auburn.edu > Subject: Re: [Veritas-bu] Curious Log Entry > > What version of NetBackup? What kind of backup? There were a > few bugs around with 150 errors happening with no intervention: > > http://support.veritas.com/docs/275149 > > http://support.veritas.com/docs/281309 > > Support site is a wonder when you can find things on it! :) > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Brooks, Jason > Sent: Tuesday, April 24, 2007 9:49 AM > To: veritas-bu@mailman.eng.auburn.edu > Subject: [Veritas-bu] Curious Log Entry > > 4/23/2007 11:21:15 PM masterA client1 Error 83645 Backup > backup of client client1 exited with status 150 (termination > requested by > administrator) > > How do you end up with a 150 when no Admins are here? Anyone > seen this one? > I can't recall seeing it before, and at first blush, it makes > me a bit nervous. I'll be poking around to see what I can find. > > Thanks, > Jason > > > Jason Brooks > Computer Systems Engineer > IITS - Longwood University > voice - (434) 395-2034 > fax - (434) 395-2035 > mailto:<[EMAIL PROTECTED]> > > > ** > *** > This communication, including attachments, is for the > exclusive use of addressee and may contain proprietary, > confidential and/or privileged information. If you are not > the intended recipient, any use, copying, disclosure, > dissemination or distribution is strictly prohibited. If you > are not the intended recipient, please notify the sender > immediately by return e-mail, delete this communication and > destroy all copies. > ** > *** > > > ___ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Curious Log Entry
I believe you can get this when resources (memory?) are overloaded on the master/media. Can't be more specific as only seen it very rarely & so haven't investigated thoroughly. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Brooks, Jason > Sent: 24 April 2007 14:49 > To: veritas-bu@mailman.eng.auburn.edu > Subject: [Veritas-bu] Curious Log Entry > > > 4/23/2007 11:21:15 PM masterA client1 Error 83645 Backup > backup of client client1 exited with status 150 (termination > requested by > administrator) > > How do you end up with a 150 when no Admins are here? Anyone > seen this one? > I can't recall seeing it before, and at first blush, it makes me a bit > nervous. I'll be poking around to see what I can find. > > Thanks, > Jason > > > Jason Brooks > Computer Systems Engineer > IITS - Longwood University > voice - (434) 395-2034 > fax - (434) 395-2035 > mailto:<[EMAIL PROTECTED]> > - Egg is a trading name of the Egg group of companies which includes: Egg plc (reg no 2448340), Egg Financial Intermediation Ltd (reg no 3828289), and Egg Banking plc (reg no 2999842). Egg Banking plc and Egg Financial Intermediation Ltd are authorised and regulated by the Financial Services Authority (FSA) and are entered in the FSA register under numbers 205621 and 309551 respectively. These members of the Egg group are registered in England and Wales. Registered office: Laurence Pountney Hill, London EC4R 0HH. This e-mail is confidential and for use by the addressee only. If you are not the intended recipient of this e-mail and have received it in error, please return the message to the sender by replying to it and then delete it from your mailbox. Internet e-mails are not necessarily secure. The Egg group of companies do not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by the Egg group of companies in this regard and the recipient should carry out such virus and other checks as it considers appropriate. This communication does not create or modify any contract. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Curious Log Entry
Nothing wrong with the GUI ! Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Steve Fogarty [mailto:[EMAIL PROTECTED] Sent: 24 April 2007 17:12 To: 'Greenberg, Katherine (ISD, IT)'; 'Hudson, Steve'; 'Jeff Lightner'; WEAVER, Simon (external); 'Brooks, Jason'; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Curious Log Entry Agreed. Stay away from the GUI! Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greenberg, Katherine (ISD, IT) Sent: Tuesday, April 24, 2007 12:31 PM To: Hudson, Steve; Jeff Lightner; WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry Reason # 9 trillion to learn all the various syntax options of bpdbjobs ;) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hudson, Steve Sent: Tuesday, April 24, 2007 11:03 AM To: Jeff Lightner; WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry I couldn't agree more We have inadvertently killed all jobs when trying to kill only one. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Tuesday, April 24, 2007 10:47 AM To: WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry I've never seen a 150 that wasn't caused by someone actually canceling the job (even when they initially don't fess up). That brings up one of my pet peeves about the Java GUI. The options for "kill" selected job and "kill" all jobs are one above the other. Often once you highlight it the highlight goes away when you get the prompt to OK the action. Due to this I've seen a couple of times where people here have killed all when they meant to kill one. The kill all should be all the way at the end of the list and separated by a bar so one has to consciously choose it. Its warning prompt should be significantly different than the one for killing a single job. Hell if it would just leave the original selection highlighted one would be less likely to go ahead and hit OK. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Tuesday, April 24, 2007 10:16 AM To: 'Brooks, Jason'; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry Jason Well its not automated :-) If no one had access to the Master Server console, what about from the end client?? Spooky :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brooks, Jason Sent: 24 April 2007 14:49 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Curious Log Entry ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu - The information contained in this email message and its attachments is intended only for the private and confidential use of the recipient(s) named above, unless the sender expressly agrees otherwise. Transmission of email over the Internet is not a secure communications medium. If you are requesting or have requested the transmittal of personal data, as defined in applicable privacy laws by means of email or in an attachment to email, you must select a more secure alternate mean
Re: [Veritas-bu] Curious Log Entry
Brooks, Jason wrote: > 4/23/2007 11:21:15 PM masterA client1 Error 83645 Backup > backup of client client1 exited with status 150 (termination requested by > administrator) > > How do you end up with a 150 when no Admins are here? Anyone seen this one? > I can't recall seeing it before, and at first blush, it makes me a bit > nervous. I'll be poking around to see what I can find. > We've run into a case where running out of memory on the master can cause a flood of 150s. This was fixed in the 6.0MP4 release for us. .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] I GoodSearch for Bundles Of Love http://www.goodsearch.com/?charityid=821118 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Curious Log Entry
They could have killed the proc too...not that I've ever done that before... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Tuesday, April 24, 2007 10:23 AM To: Steve Fogarty; Greenberg, Katherine (ISD, IT); Hudson, Steve; WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry Don't get me wrong. As an early DOS user who refused to go to Windows for years and a longtime UNIX/Linux admin I don't have much respect for folks who can't do command line. Having said that, however, I do think there are times using a GUI makes sense. For monitoring I like the activity monitor and if one is careful one can actually kill what is intended rather than everything. As noted it is a pet peeve - not a show stopper. For stopping/starting drives and many other tasks the GUI is a royal pain so I use command line or my own scripts based on command line for such tasks. -Original Message- From: Steve Fogarty [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 24, 2007 12:12 PM To: 'Greenberg, Katherine (ISD, IT)'; 'Hudson, Steve'; Jeff Lightner; 'WEAVER, Simon (external)'; 'Brooks, Jason'; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Curious Log Entry Agreed. Stay away from the GUI! Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greenberg, Katherine (ISD, IT) Sent: Tuesday, April 24, 2007 12:31 PM To: Hudson, Steve; Jeff Lightner; WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry Reason # 9 trillion to learn all the various syntax options of bpdbjobs ;) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hudson, Steve Sent: Tuesday, April 24, 2007 11:03 AM To: Jeff Lightner; WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry I couldn't agree more We have inadvertently killed all jobs when trying to kill only one. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Tuesday, April 24, 2007 10:47 AM To: WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry I've never seen a 150 that wasn't caused by someone actually canceling the job (even when they initially don't fess up). That brings up one of my pet peeves about the Java GUI. The options for "kill" selected job and "kill" all jobs are one above the other. Often once you highlight it the highlight goes away when you get the prompt to OK the action. Due to this I've seen a couple of times where people here have killed all when they meant to kill one. The kill all should be all the way at the end of the list and separated by a bar so one has to consciously choose it. Its warning prompt should be significantly different than the one for killing a single job. Hell if it would just leave the original selection highlighted one would be less likely to go ahead and hit OK. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Tuesday, April 24, 2007 10:16 AM To: 'Brooks, Jason'; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry Jason Well its not automated :-) If no one had access to the Master Server console, what about from the end client?? Spooky :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brooks, Jason Sent: 24 April 2007 14:49 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Curious Log Entry ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England _
Re: [Veritas-bu] Curious Log Entry
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: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Mike Heck > Sent: Tuesday, April 24, 2007 12:23 PM > To: veritas-bu@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@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > smime.p7s Description: S/MIME cryptographic signature ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Curious Log Entry
Don't get me wrong. As an early DOS user who refused to go to Windows for years and a longtime UNIX/Linux admin I don't have much respect for folks who can't do command line. Having said that, however, I do think there are times using a GUI makes sense. For monitoring I like the activity monitor and if one is careful one can actually kill what is intended rather than everything. As noted it is a pet peeve - not a show stopper. For stopping/starting drives and many other tasks the GUI is a royal pain so I use command line or my own scripts based on command line for such tasks. -Original Message- From: Steve Fogarty [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 24, 2007 12:12 PM To: 'Greenberg, Katherine (ISD, IT)'; 'Hudson, Steve'; Jeff Lightner; 'WEAVER, Simon (external)'; 'Brooks, Jason'; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Curious Log Entry Agreed. Stay away from the GUI! Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greenberg, Katherine (ISD, IT) Sent: Tuesday, April 24, 2007 12:31 PM To: Hudson, Steve; Jeff Lightner; WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry Reason # 9 trillion to learn all the various syntax options of bpdbjobs ;) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hudson, Steve Sent: Tuesday, April 24, 2007 11:03 AM To: Jeff Lightner; WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry I couldn't agree more We have inadvertently killed all jobs when trying to kill only one. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Tuesday, April 24, 2007 10:47 AM To: WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry I've never seen a 150 that wasn't caused by someone actually canceling the job (even when they initially don't fess up). That brings up one of my pet peeves about the Java GUI. The options for "kill" selected job and "kill" all jobs are one above the other. Often once you highlight it the highlight goes away when you get the prompt to OK the action. Due to this I've seen a couple of times where people here have killed all when they meant to kill one. The kill all should be all the way at the end of the list and separated by a bar so one has to consciously choose it. Its warning prompt should be significantly different than the one for killing a single job. Hell if it would just leave the original selection highlighted one would be less likely to go ahead and hit OK. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Tuesday, April 24, 2007 10:16 AM To: 'Brooks, Jason'; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry Jason Well its not automated :-) If no one had access to the Master Server console, what about from the end client?? Spooky :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brooks, Jason Sent: 24 April 2007 14:49 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Curious Log Entry ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu - The information contained in this email message and its attachments is intended
[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@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Curious Log Entry
Agreed. Stay away from the GUI! Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greenberg, Katherine (ISD, IT) Sent: Tuesday, April 24, 2007 12:31 PM To: Hudson, Steve; Jeff Lightner; WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry Reason # 9 trillion to learn all the various syntax options of bpdbjobs ;) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hudson, Steve Sent: Tuesday, April 24, 2007 11:03 AM To: Jeff Lightner; WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry I couldn't agree more We have inadvertently killed all jobs when trying to kill only one. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Tuesday, April 24, 2007 10:47 AM To: WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry I've never seen a 150 that wasn't caused by someone actually canceling the job (even when they initially don't fess up). That brings up one of my pet peeves about the Java GUI. The options for "kill" selected job and "kill" all jobs are one above the other. Often once you highlight it the highlight goes away when you get the prompt to OK the action. Due to this I've seen a couple of times where people here have killed all when they meant to kill one. The kill all should be all the way at the end of the list and separated by a bar so one has to consciously choose it. Its warning prompt should be significantly different than the one for killing a single job. Hell if it would just leave the original selection highlighted one would be less likely to go ahead and hit OK. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Tuesday, April 24, 2007 10:16 AM To: 'Brooks, Jason'; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry Jason Well its not automated :-) If no one had access to the Master Server console, what about from the end client?? Spooky :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brooks, Jason Sent: 24 April 2007 14:49 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Curious Log Entry ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu - The information contained in this email message and its attachments is intended only for the private and confidential use of the recipient(s) named above, unless the sender expressly agrees otherwise. Transmission of email over the Internet is not a secure communications medium. If you are requesting or have requested the transmittal of personal data, as defined in applicable privacy laws by means of email or in an attachment to email, you must select a more secure alternate means of transmittal that supports your obligations to protect such personal data. If the reader of this message is not the intended recipient and/or you have received this email in error, you must take no action based on the information in this email and you are hereby notified that any dissemination, misuse or copying or disclosure of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by email and delete the original message. ___ Ve
Re: [Veritas-bu] Curious Log Entry
Reason # 9 trillion to learn all the various syntax options of bpdbjobs ;) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hudson, Steve Sent: Tuesday, April 24, 2007 11:03 AM To: Jeff Lightner; WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry I couldn't agree more We have inadvertently killed all jobs when trying to kill only one. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Tuesday, April 24, 2007 10:47 AM To: WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry I've never seen a 150 that wasn't caused by someone actually canceling the job (even when they initially don't fess up). That brings up one of my pet peeves about the Java GUI. The options for "kill" selected job and "kill" all jobs are one above the other. Often once you highlight it the highlight goes away when you get the prompt to OK the action. Due to this I've seen a couple of times where people here have killed all when they meant to kill one. The kill all should be all the way at the end of the list and separated by a bar so one has to consciously choose it. Its warning prompt should be significantly different than the one for killing a single job. Hell if it would just leave the original selection highlighted one would be less likely to go ahead and hit OK. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Tuesday, April 24, 2007 10:16 AM To: 'Brooks, Jason'; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry Jason Well its not automated :-) If no one had access to the Master Server console, what about from the end client?? Spooky :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brooks, Jason Sent: 24 April 2007 14:49 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Curious Log Entry ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu - The information contained in this email message and its attachments is intended only for the private and confidential use of the recipient(s) named above, unless the sender expressly agrees otherwise. Transmission of email over the Internet is not a secure communications medium. If you are requesting or have requested the transmittal of personal data, as defined in applicable privacy laws by means of email or in an attachment to email, you must select a more secure alternate means of transmittal that supports your obligations to protect such personal data. If the reader of this message is not the intended recipient and/or you have received this email in error, you must take no action based on the information in this email and you are hereby notified that any dissemination, misuse or copying or disclosure of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by email and delete the original message. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu * This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information.
Re: [Veritas-bu] Curious Log Entry
I've had issues with 4.5 on Windows 200 where I kill a job and 8 hours later it actually dies. Never longer than a minute I think on 6.0. I don't suppose you've got VPN? I secretly kill jobs from home all the time just to screw w/ the backup admin. Oh wait, that's me! -Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brooks, Jason Sent: Tuesday, April 24, 2007 11:14 AM To: Greenberg, Katherine (ISD, IT); veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry Sorry - NBU 6.0MP4, Windows 2K3SP2 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Greenberg, Katherine (ISD, IT) > Sent: Tuesday, April 24, 2007 11:10 AM > To: Brooks, Jason; veritas-bu@mailman.eng.auburn.edu > Subject: Re: [Veritas-bu] Curious Log Entry > > What version of NetBackup? What kind of backup? There were a few bugs > around with 150 errors happening with no intervention: > > http://support.veritas.com/docs/275149 > > http://support.veritas.com/docs/281309 > > Support site is a wonder when you can find things on it! :) > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Brooks, Jason > Sent: Tuesday, April 24, 2007 9:49 AM > To: veritas-bu@mailman.eng.auburn.edu > Subject: [Veritas-bu] Curious Log Entry > > 4/23/2007 11:21:15 PM masterA client1 Error 83645 Backup > backup of client client1 exited with status 150 (termination requested > by > administrator) > > How do you end up with a 150 when no Admins are here? Anyone seen > this one? > I can't recall seeing it before, and at first blush, it makes me a bit > nervous. I'll be poking around to see what I can find. > > Thanks, > Jason > > > Jason Brooks > Computer Systems Engineer > IITS - Longwood University > voice - (434) 395-2034 > fax - (434) 395-2035 > mailto:<[EMAIL PROTECTED]> > > > ** > *** > This communication, including attachments, is for the exclusive use of > addressee and may contain proprietary, confidential and/or privileged > information. If you are not the intended recipient, any use, copying, > disclosure, dissemination or distribution is strictly prohibited. If > you are not the intended recipient, please notify the sender > immediately by return e-mail, delete this communication and destroy > all copies. > ** > *** > > > ___ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Curious Log Entry
What version of NetBackup? What kind of backup? There were a few bugs around with 150 errors happening with no intervention: http://support.veritas.com/docs/275149 http://support.veritas.com/docs/281309 Support site is a wonder when you can find things on it! :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brooks, Jason Sent: Tuesday, April 24, 2007 9:49 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Curious Log Entry 4/23/2007 11:21:15 PM masterA client1 Error 83645 Backup backup of client client1 exited with status 150 (termination requested by administrator) How do you end up with a 150 when no Admins are here? Anyone seen this one? I can't recall seeing it before, and at first blush, it makes me a bit nervous. I'll be poking around to see what I can find. Thanks, Jason Jason Brooks Computer Systems Engineer IITS - Longwood University voice - (434) 395-2034 fax - (434) 395-2035 mailto:<[EMAIL PROTECTED]> * This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. * ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Curious Log Entry
Sorry - NBU 6.0MP4, Windows 2K3SP2 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Greenberg, Katherine (ISD, IT) > Sent: Tuesday, April 24, 2007 11:10 AM > To: Brooks, Jason; veritas-bu@mailman.eng.auburn.edu > Subject: Re: [Veritas-bu] Curious Log Entry > > What version of NetBackup? What kind of backup? There were a > few bugs around with 150 errors happening with no intervention: > > http://support.veritas.com/docs/275149 > > http://support.veritas.com/docs/281309 > > Support site is a wonder when you can find things on it! :) > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Brooks, Jason > Sent: Tuesday, April 24, 2007 9:49 AM > To: veritas-bu@mailman.eng.auburn.edu > Subject: [Veritas-bu] Curious Log Entry > > 4/23/2007 11:21:15 PM masterA client1 Error 83645 Backup > backup of client client1 exited with status 150 (termination > requested by > administrator) > > How do you end up with a 150 when no Admins are here? Anyone > seen this one? > I can't recall seeing it before, and at first blush, it makes > me a bit nervous. I'll be poking around to see what I can find. > > Thanks, > Jason > > > Jason Brooks > Computer Systems Engineer > IITS - Longwood University > voice - (434) 395-2034 > fax - (434) 395-2035 > mailto:<[EMAIL PROTECTED]> > > > ** > *** > This communication, including attachments, is for the > exclusive use of addressee and may contain proprietary, > confidential and/or privileged information. If you are not > the intended recipient, any use, copying, disclosure, > dissemination or distribution is strictly prohibited. If you > are not the intended recipient, please notify the sender > immediately by return e-mail, delete this communication and > destroy all copies. > ** > *** > > > ___ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > smime.p7s Description: S/MIME cryptographic signature ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Curious Log Entry
I couldn't agree more We have inadvertently killed all jobs when trying to kill only one. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Tuesday, April 24, 2007 10:47 AM To: WEAVER, Simon (external); Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry I've never seen a 150 that wasn't caused by someone actually canceling the job (even when they initially don't fess up). That brings up one of my pet peeves about the Java GUI. The options for "kill" selected job and "kill" all jobs are one above the other. Often once you highlight it the highlight goes away when you get the prompt to OK the action. Due to this I've seen a couple of times where people here have killed all when they meant to kill one. The kill all should be all the way at the end of the list and separated by a bar so one has to consciously choose it. Its warning prompt should be significantly different than the one for killing a single job. Hell if it would just leave the original selection highlighted one would be less likely to go ahead and hit OK. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Tuesday, April 24, 2007 10:16 AM To: 'Brooks, Jason'; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry Jason Well its not automated :-) If no one had access to the Master Server console, what about from the end client?? Spooky :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brooks, Jason Sent: 24 April 2007 14:49 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Curious Log Entry ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu - The information contained in this email message and its attachments is intended only for the private and confidential use of the recipient(s) named above, unless the sender expressly agrees otherwise. Transmission of email over the Internet is not a secure communications medium. If you are requesting or have requested the transmittal of personal data, as defined in applicable privacy laws by means of email or in an attachment to email, you must select a more secure alternate means of transmittal that supports your obligations to protect such personal data. If the reader of this message is not the intended recipient and/or you have received this email in error, you must take no action based on the information in this email and you are hereby notified that any dissemination, misuse or copying or disclosure of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by email and delete the original message. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Curious Log Entry
I've never seen a 150 that wasn't caused by someone actually canceling the job (even when they initially don't fess up). That brings up one of my pet peeves about the Java GUI. The options for "kill" selected job and "kill" all jobs are one above the other. Often once you highlight it the highlight goes away when you get the prompt to OK the action. Due to this I've seen a couple of times where people here have killed all when they meant to kill one. The kill all should be all the way at the end of the list and separated by a bar so one has to consciously choose it. Its warning prompt should be significantly different than the one for killing a single job. Hell if it would just leave the original selection highlighted one would be less likely to go ahead and hit OK. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Tuesday, April 24, 2007 10:16 AM To: 'Brooks, Jason'; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Curious Log Entry Jason Well its not automated :-) If no one had access to the Master Server console, what about from the end client?? Spooky :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brooks, Jason Sent: 24 April 2007 14:49 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Curious Log Entry ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Curious Log Entry
Jason Well its not automated :-) If no one had access to the Master Server console, what about from the end client?? Spooky :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brooks, Jason Sent: 24 April 2007 14:49 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Curious Log Entry ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Curious Log Entry
See if it was a manual or user initiated backup that the iniating user terminated. Bobby. -- Original message -- From: "Brooks, Jason" <[EMAIL PROTECTED]> > ___ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Curious Log Entry
4/23/2007 11:21:15 PM masterA client1 Error 83645 Backup backup of client client1 exited with status 150 (termination requested by administrator) How do you end up with a 150 when no Admins are here? Anyone seen this one? I can't recall seeing it before, and at first blush, it makes me a bit nervous. I'll be poking around to see what I can find. Thanks, Jason Jason Brooks Computer Systems Engineer IITS - Longwood University voice - (434) 395-2034 fax - (434) 395-2035 mailto:<[EMAIL PROTECTED]> smime.p7s Description: S/MIME cryptographic signature ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
