Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ Logging Reference Guide
  3. Using logs
  4. About unified logging
  5. About rolling over unified log files
Veritas NetBackup™ Logging Reference Guide

About rolling over unified log files

To prevent log files from becoming too large, or to control when or how often logs are created, you can set a log rollover option. When a file size or time setting is reached, the current log file is closed. New log messages for the logging process are written or "rolled over" to a new log file.

See Log retention and log size.

You can set log file rollover to occur based on file size, time of day, or elapsed time. Set the conditions by using the vxlogcfg command with the options described in Table: vxlogcfg options that control the rollover of the unified log files.

Table: vxlogcfg options that control the rollover of the unified log files

Option

Description

MaxLogFileSizeKB

Specifies the maximum size that is allowed for the log file (in kilobytes) before rollover occurs, if the RolloverMode is set to FileSize.

RolloverAtLocalTime

Specifies the time of day at which the log file is rolled over, if the RolloverMode is set to LocalTime.

RolloverPeriodInSeconds

Specifies a period of time in seconds after which the log file is rolled over, if the RolloverMode is set to Periodic.

MaxLogFileSizeKB or RolloverAtLocalTime

Specifies that the log file rollover occurs whenever the file size limit or the local time limit is reached, whichever is first.

An example of the command:

vxlogcfg -a -p 51216 -g Default 
MaxLogFileSizeKB=256  
RolloverAtLocalTime=22:00

MaxLogFileSizeKB or RolloverPeriodInSeconds

Specifies that the log file rollover occurs whenever the file size limit or the periodic time limit is reached, whichever is first.

A complete description of vxlogcfg is in the NetBackup Commands Reference Guide.

By default, log file rollover is based on a file size of 51200 KB. When a log file reaches 51200 KB in size, the file closes and a new log file opens.

The following example sets the NetBackup (prodid 51216) rollover mode to Periodic.

# vxlogcfg -a --prodid 51216 --orgid 116 -s RolloverMode=Periodic 
    RolloverPeriodInSeconds=86400

The previous example uses the vxlogcfg command with the RolloverMode option. It sets rollover mode for nbpem (originator ID 116) to Periodic. It also sets the interval until the next nbpem log file rollover to 24 hours (86400 seconds).

In the following example, the file names show the log file rollover with the rotation ID incremented:

    /usr/openv/logs/nbpem/51216-116-2201360136-041029-0000000000.log
    /usr/openv/logs/nbpem/51216-116-2201360136-041029-0000000001.log
    /usr/openv/logs/nbpem/51216-116-2201360136-041029-0000000002.log

In addition, you can use log file rotation with the following:

  • Logs for the server processes that use unified logging

    See Originator IDs for the entities that use unified logging.

  • Certain legacy logs

  • The unified logging files that the Bare Metal Restore process bmrsavecfg creates

Feedback

Was this page helpful?
Previous

About changing the location of unified log files

Next

About recycling unified log files

Feedback

Was this page helpful?