how we can change the log size.

Hi,
NBU version is 6.5
Thanks Andy for reply..
but i guess this is not the solution of my query...
these all deals with configuring and moving logs to some different location...
I want to fix their size by allocating some fix space...
I dnt want them to exceed that particular limit which i'll set.....

Mar

2010

0 Votes 0

rjrumfelt

That can be done by log rotation

which is covered in several of the guides that Andy mentioned.

Mar

2010

1 Vote +1

Marianne van den Berg

Trusted Advisor

Accredited

Certified

Have you even tried to read

Have you even tried to read all the links from Andy's post?
Extract from DOCUMENTATION: How to configure log file rotation for Unified logging using "vxlogcfg":

To set the RolloverMode to FileSize

Unified logging can be configured to rotate based on file size. The drawback to this method is that not all log files will contain entries from the same date range. An originator such as 111 (nbemm) will rotate logs faster than other originators such as 153 (nbgenjob). As a result, the oldest log messages for nbemm will expire before the oldest log messages for nbgenjob, which can create discrepancies in the logs.

The following command will rotate the log files once a file reaches 50meg (51200 KB) in size.

# cd /usr/openv/netbackup/bin

# ./vxlogcfg -a -p 51216 -o Default -s RolloverMode=FileSize -s MaxLogFileSizeKB=51200

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

Mar

2010

2 Votes +2

Andy Welburn

Trusted Advisor

@Pinku

As a matter of interest, what issues are you encountering exactly?

As far as our environment is concerned (NB6.5.4), we have logging set to 3 days (clean-up interval setting) which has resulted in a grand total of 672Mb on our Master for legacy logging (all sub-directories/processes) & 1.5Gb for unified logging (35 files of 50Mb each - rollover setting or default?) - so not a lot really!

Do you know at what level your logging is set to? Have you had any issues recently that resulted in Symantec asking you to increase the verbosity of your logging?

As far as your clients are concerned, logs should only really be created if you are having issues with a particular client. e.g. on Windows clients don't run the mklogdir.bat file to create all possible log sub-directories (unless you really have to) as once these are created they will become populated with logs!

These are all covered by the T/N's I quoted earlier, honest!

Regards Andy

"It's not too late to panic ..."

Mar

2010

0 Votes 0

Pinku

Hi.. "vxlogcfg" was

Hi..
"vxlogcfg" was completely a new thing to me..

i got it now....
earlier i missed some things while reading the note.....
and found this note very helpful....
@Andy : thanks for the additional info(above post), i was not even aware of this thing....

@ Marianne next time i'll read the post carefully before u scold me again :)

how we can change the log size.

Comments

You haven't stated your NB version, but there are a lot of

Pinku - Andy has the

Hi, NBU version is 6.5 Thanks

That can be done by log rotation

Have you even tried to read

@Pinku

Hi.. "vxlogcfg" was

Would you like to reply?

Links

Technical Support

Symantec.com

Store

Community Stats