Ayuda de vídeo de Screencast

Disable logging Netbackup 7.1.04

Created: 11 Oct 2012 • Updated: 06 Enero 2013 | 7 comments
Se ha solucionado este problema. Vea la solución.

Currently I'm generating a fair amount of logs. I've had to use them off and on in the past to troubleshoot things. The biggest one is bpbkar which generates some substantial logs, but also nbjm, nbemm, nbconsole to name a few.

In the Host Properties of the Master Server, I've set the logging level on the Master to "0", and All specific overrides and debug levels for services are set to "Same as Global" or 0 as well.

All Media Servers and Clients are set to "Same as Global".

Is there something that I'm missing as far as disabling them: like a registry setting or something? Or do I simply need to delete the folders to prevent Netbackup from writing the log files?

Comentarios ComentariosIr al último comentario

el cuadro de los Nicolai

For the classic logs (those in netbackup/logs/) just delete the folder. The process writing to the directory needs to be stopped. If it the unified logs use vxlogcfg 

http://www.symantec.com/docs/TECH47372

Unified logs:

http://www.symantec.com/docs/HOWTO34327

http://www.symantec.com/docs/TECH43251

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

SOLUCIÓN
el cuadro de los smckelvey

We aren't using Unified logs.

So, there's no other setting controlling the logging: Netbackup will write those logs by default simply becaue the folder exists?

el cuadro de los Marianne

nbjm, nbemm, nbpem, etc are all unified logs. There is no way you are NOT using them.

Please read through chapter 3 of NBU Troubleshooting Guide..http://www.symantec.com/docs/DOC3683

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

el cuadro de los smckelvey

I have read that. But clearly I haven't found my answer, since apparently I couldn't even discern whether it was Legacy or Unified logging.

Per the guide, I assumed it was Legacy for the following reasons:

  • "Most PC client processes use legacy logging except for a few Bare Metal Restore processes."
  • "All NetBackup processes use either unified logging or legacy logging.", which I took to mean either/or, depending on how it was configured.
  • "Unified logging does not require that you create logging subdirectories.", which made me assume that we were using Legacy since every log lives in it's appropriate subdirectory.

But since I've clearly misunderstood, maybe you can expound enough to answer my questions?

el cuadro de los Nicolai

I think the question are about the classic log (and their size). The unified log are not bugging him in size.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

el cuadro de los Nicolai

Yes - you are correct. Netbackup will write debug info into those log files if the catalog exist.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

el cuadro de los Marianne

Unified logs and their location are listed in the Troubleshooting Guide under this topic: Server processes that use unified logging.

Legacy logs and their location are listed under this topic: About legacy logging and Directory names for legacy debug logs for servers.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links