cancel
Showing results for 
Search instead for 
Did you mean: 

Update robust logging settings on clients from master ?

Michael_G_Ander
Level 6
Certified

Hello

I have tried to find a to update the robust logging settings on our clients mainly Windows 2008/2012 from the master server Windows 2008

I have been able to enable the robust logging and is now looking for a way to update the settings so the clients starts rotate the logs

Regards

Michael

 

 

 

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue
1 ACCEPTED SOLUTION

Accepted Solutions

mph999
Level 6
Employee Accredited

You can do it from the Logging Assistant if using NBU 7.6  - this will set up specified logs on specified clients.

View solution in original post

9 REPLIES 9

Marianne
Level 6
Partner    VIP    Accredited Certified

Seems you will need to run vxlogcfg on each client...

I had a look at vxlogcfg switches and options - I don't see anything where another host/client can be specified.

mph999
Level 6
Employee Accredited

You can do it from the Logging Assistant if using NBU 7.6  - this will set up specified logs on specified clients.

Michael_G_Ander
Level 6
Certified

That was exactly what I was afraid of, had hoped it could be by bpsetconfig like the enabling of the robust logging

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Michael_G_Ander
Level 6
Certified

Unfortunately we are waiting for 7.6.0.2 to minimize the down times used for upgrading the backup system

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Mark_Solutions
Level 6
Partner Accredited Certified

The words "!!! DO NOT EDIT THIS FILE MANUALLY. USE vxlogcfg INSTEAD !!!" appear in the file:

C:\Program Files\Veritas\NetBackup\nblog.conf

but it doesn't say that you cannot copy it from one client to another (as long as the install path is the same)!

Just a thought!

#EDIT#

Just adding a disclaimer here... at your own risk .. not supported .. test thourougly in a test environment .. etc. etc ... you know what i am saying!

Michael_G_Ander
Level 6
Certified

Think I rather go with some way of running vxcfglog on the clients

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Deb_Wilmot
Level 6
Employee Accredited Certified

You stated Robust logging - not unified logging...

There isn't really anything logged on clients that fall under the unified logs.

 

On the master server - go to Host Properties --> Clients -->select the client you want.

 

Go to the Logging area.

 

Checkmark Robust logs.

 

That will enable robust logging on the client you chose.  You can also manipulate logging levels for global and database.

 

Note that robust logging will limit the number of log files and the size by what is configured in the nblog.conf file in C:\Program Files\Veritas\NetBackup.

 

The default settings are 3 logs, 50mg each.

 

i.e.

Default.MaxLogFileSizeKB=51200
Default.NumberOfLogFiles=3

Attached is a screenshot of the client logging properties.

 

Michael_G_Ander
Level 6
Certified

robust logging is as far as I know from manual/technotes based on the unified logging system, the problem is that logrotate is set to false as default

From a client

C:\Program Files\VERITAS\NetBackup\bin>vxlogcfg -p nb -l -g default
Configuration settings for logset "Default", of product 51.216...
LogDirectory =
DebugLevel = 0
DiagnosticLevel = 0
DynaReloadInSec = 0
LogToStdout = False
LogToStderr = False
LogToOslog = False
RolloverMode = None
LogRecycle = False
MaxLogFileSizeKB = 10240
RolloverPeriodInSeconds = 43200
RolloverAtLocalTime = 0:00
NumberOfLogFiles = 4294967295
FileName = Default
AppMsgLogging = ON
NtEventLogSourceName = Application
NtEventLogCategory = 0
LogFileSDDL = (null)

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Deb_Wilmot
Level 6
Employee Accredited Certified

Log rotation doesn't have anything to do with Robust logging.  This is a very confusing topic and always has been.

 

Also note that your example isn't eactly showing the right information, I'll have to research this.

 

i.e. I ran this on my lab system (fresh install) - here's the output:

 

C:\Program Files\Veritas\NetBackup>cd bin

C:\Program Files\Veritas\NetBackup\bin>vxlogcfg -p nb -l -g default
Configuration settings for logset "Default", of product 51,216...
LogDirectory =
DebugLevel = 0
DiagnosticLevel = 0
DynaReloadInSec = 0
LogToStdout = False
LogToStderr = False
LogToOslog = False
RolloverMode = None
LogRecycle = False
MaxLogFileSizeKB = 10240
RolloverPeriodInSeconds = 43200
RolloverAtLocalTime = 0:00
NumberOfLogFiles = 4294967295
FileName = Default
AppMsgLogging = ON
NtEventLogSourceName = Application
NtEventLogCategory = 0
LogFileSDDL = (null)

 

 

But when I look at the nblog.conf fiel - it shows different values:

 Default.LogDirectory=C:\Program Files\Veritas\NetBackup\logs
Default.LogFilePermissions=664
Default.L10nLib=C:\Program Files\Veritas\NetBackup\bin\vxextwincat
Default.L10nResourceDir=C:\Program Files\Veritas\NetBackup\resources
Default.AppMsgLogging=ON
Default.DiagnosticLevel=6
Default.DebugLevel=1
Default.RolloverMode=FileSize|LocalTime
Default.RolloverAtLocalTime=00.00
Default.MaxLogFileSizeKB=51200
Default.NumberOfLogFiles=3
Default.LogRecycle=false
Default.LogToStdout=false
Default.LogToStderr=false
Default.LogToOslog=false
Default.SyslogOpt=0
Default.SyslogFacility=LOG_LOCAL5
Default.SyslogIdent=VRTS-NB

 

 

Go figure.

 

This IS the same system.