Re: [Veritas-bu] Netbackup VERBOSE in bp.conf
Thanks all - The GUI actually shows 6 levels (0 - 5) and help shows 5 is the highest as you've indicated. Also when I used the GUI it gave a warning that some processes might not see the change unless NBU is restarted so I opted to restart. I'll look into the vxlog stuff. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Rusty Major Sent: Thursday, August 25, 2011 1:03 AM To: nbuser; Lightner, Jeff Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Netbackup VERBOSE in bp.conf This is not always true. For any processes that are always up (bpdbm, etc.), you'll need to restart NBU. For other processes that are started per job (bptm, bpdm), then it is correct that they will re-read the bp.conf file and pick up the changed verbosity. You can have NBU reread the bp.conf file by issuing this command: bprdreq -rereadconfig A side note - bp.conf only applies to legacy processes (bpx) and that log to /usr/openv/netbackup/logs. You also should check the new vxlog command to make sure it is logging at a low level. These are all the new processes (nb) and log into /usr/openv/logs. I don't have the full syntax handy, sorry :D, but it's vxlogcfg that you'll need to look for. -Rusty From: veritas-bu-boun...@mailman.eng.auburn.edumailto:veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edumailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of nbuser Sent: Wednesday, August 24, 2011 9:57 PM To: Lightner, Jeff Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDUmailto:VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Netbackup VERBOSE in bp.conf Verbose =5 is highest and you dont have to restart the services. Whenever a new job schedules it picks up latest change made in bp.conf Sent from my TAB. Please excuse spelling errors. On Aug 24, 2011 10:43 AM, Lightner, Jeff jlight...@water.commailto:jlight...@water.com wrote: There are 5 levels of VERBOSE available. Am I right in assuming VERBOSE = 5 is highest or is VERBOSE = 1 the highest? If change VERBOSE = in bp.conf do I need to actually restart NetBackup or is it sufficient to do the bpadm --global --modify --notify request daemons? If I change debugging level via the NBU Java GUI instead of modifying the files does that mean I don't have to restart NBU? This is NBU 7.1 on RHEL5 master and an HP-UX media server. __ Jeff Lightner | UNIX/Linux Administrator | DS Waters of America, Inc | 5660 New Northside Drive, Ste 250 | Atlanta, GA 30328 *: (Direct Dial) 678-486-3516 |*: (Cell) 678-772-0018 | *:jlight...@water.commailto:jlight...@water.com Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup VERBOSE in bp.conf
Jeff, I dug up where I had this documented. Here’s the command to change the values to the lowest recommended setting. Perhaps 1 is the lowest, I’m not sure. vxlogcfg -a -p NB -o all -s DebugLevel=1 -s DiagnosticLevel=1 I also had a note that an upgrade from 6.5 to 7.0.x will reset the logs. If you upgraded, would be wise to check. The upgrade also moved the location of the logs so you may be able to cleanup some space if the old logs are still hanging around. Finally, the log recycle level is turned off during the upgrade. You will want to check these if you performed an upgrade. Also, for those that don’t know, be sure to run the /usr/openv/netbackup/logs/mklogdir(.bat) command if you haven’t. This creates the logging directories for all possible processes. If NBU doesn’t have the logging directory there, it won’t log anything for that daemon, regardless of the verbosity. This only pertains -Rusty *From:* Lightner, Jeff [mailto:jlight...@water.com] *Sent:* Thursday, August 25, 2011 7:51 AM *To:* Rusty Major; nbuser *Cc:* VERITAS-BU@MAILMAN.ENG.AUBURN.EDU *Subject:* RE: [Veritas-bu] Netbackup VERBOSE in bp.conf Thanks all – The GUI actually shows 6 levels (0 – 5) and help shows 5 is the highest as you’ve indicated. Also when I used the GUI it gave a warning that some processes might not see the change unless NBU is restarted so I opted to restart. I’ll look into the vxlog stuff. -- *From:* veritas-bu-boun...@mailman.eng.auburn.edu [mailto: veritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of *Rusty Major *Sent:* Thursday, August 25, 2011 1:03 AM *To:* nbuser; Lightner, Jeff *Cc:* VERITAS-BU@MAILMAN.ENG.AUBURN.EDU *Subject:* Re: [Veritas-bu] Netbackup VERBOSE in bp.conf This is not always true. For any processes that are always up (bpdbm, etc.), you’ll need to restart NBU. For other processes that are started per job (bptm, bpdm), then it is correct that they will re-read the bp.conf file and pick up the changed verbosity. You can have NBU reread the bp.conf file by issuing this command: bprdreq -rereadconfig A side note – bp.conf only applies to legacy processes (bpx) and that log to /usr/openv/netbackup/logs. You also should check the new vxlog command to make sure it is logging at a low level. These are all the new processes (nb) and log into /usr/openv/logs. I don’t have the full syntax handy, sorry :D, but it’s vxlogcfg that you’ll need to look for. -Rusty *From:* veritas-bu-boun...@mailman.eng.auburn.edu [mailto: veritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of *nbuser *Sent:* Wednesday, August 24, 2011 9:57 PM *To:* Lightner, Jeff *Cc:* VERITAS-BU@MAILMAN.ENG.AUBURN.EDU *Subject:* Re: [Veritas-bu] Netbackup VERBOSE in bp.conf Verbose =5 is highest and you dont have to restart the services. Whenever a new job schedules it picks up latest change made in bp.conf Sent from my TAB. Please excuse spelling errors. On Aug 24, 2011 10:43 AM, Lightner, Jeff jlight...@water.com wrote: There are 5 levels of VERBOSE available. Am I right in assuming VERBOSE = 5 is highest or is VERBOSE = 1 the highest? If change VERBOSE = in bp.conf do I need to actually restart NetBackup or is it sufficient to do the bpadm --global --modify --notify request daemons? If I change debugging level via the NBU Java GUI instead of modifying the files does that mean I don’t have to restart NBU? This is NBU 7.1 on RHEL5 master and an HP-UX media server. __ Jeff Lightner | UNIX/Linux Administrator | DS Waters of America, Inc | 5660 New Northside Drive, Ste 250 | Atlanta, GA 30328 •: (Direct Dial) 678-486-3516 |•: (Cell) 678-772-0018 | •: jlight...@water.com Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup VERBOSE in bp.conf
Verbose =5 is highest and you dont have to restart the services. Whenever a new job schedules it picks up latest change made in bp.conf Sent from my TAB. Please excuse spelling errors. On Aug 24, 2011 10:43 AM, Lightner, Jeff jlight...@water.com wrote: There are 5 levels of VERBOSE available. Am I right in assuming VERBOSE = 5 is highest or is VERBOSE = 1 the highest? If change VERBOSE = in bp.conf do I need to actually restart NetBackup or is it sufficient to do the bpadm --global --modify --notify request daemons? If I change debugging level via the NBU Java GUI instead of modifying the files does that mean I don’t have to restart NBU? This is NBU 7.1 on RHEL5 master and an HP-UX media server. __ Jeff Lightner | UNIX/Linux Administrator | DS Waters of America, Inc | 5660 New Northside Drive, Ste 250 | Atlanta, GA 30328 •: (Direct Dial) 678-486-3516 |•: (Cell) 678-772-0018 | •: jlight...@water.com Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup VERBOSE in bp.conf
This is not always true. For any processes that are always up (bpdbm, etc.), you’ll need to restart NBU. For other processes that are started per job (bptm, bpdm), then it is correct that they will re-read the bp.conf file and pick up the changed verbosity. You can have NBU reread the bp.conf file by issuing this command: bprdreq -rereadconfig A side note – bp.conf only applies to legacy processes (bpx) and that log to /usr/openv/netbackup/logs. You also should check the new vxlog command to make sure it is logging at a low level. These are all the new processes (nb) and log into /usr/openv/logs. I don’t have the full syntax handy, sorry :D, but it’s vxlogcfg that you’ll need to look for. -Rusty *From:* veritas-bu-boun...@mailman.eng.auburn.edu [mailto: veritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of *nbuser *Sent:* Wednesday, August 24, 2011 9:57 PM *To:* Lightner, Jeff *Cc:* VERITAS-BU@MAILMAN.ENG.AUBURN.EDU *Subject:* Re: [Veritas-bu] Netbackup VERBOSE in bp.conf Verbose =5 is highest and you dont have to restart the services. Whenever a new job schedules it picks up latest change made in bp.conf Sent from my TAB. Please excuse spelling errors. On Aug 24, 2011 10:43 AM, Lightner, Jeff jlight...@water.com wrote: There are 5 levels of VERBOSE available. Am I right in assuming VERBOSE = 5 is highest or is VERBOSE = 1 the highest? If change VERBOSE = in bp.conf do I need to actually restart NetBackup or is it sufficient to do the bpadm --global --modify --notify request daemons? If I change debugging level via the NBU Java GUI instead of modifying the files does that mean I don’t have to restart NBU? This is NBU 7.1 on RHEL5 master and an HP-UX media server. __ Jeff Lightner | UNIX/Linux Administrator | DS Waters of America, Inc | 5660 New Northside Drive, Ste 250 | Atlanta, GA 30328 •: (Direct Dial) 678-486-3516 |•: (Cell) 678-772-0018 | •: jlight...@water.com Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
