About legacy logging
In NetBackup legacy debug logging, a process creates log files of debug activity in its own logging directory. By default, NetBackup creates only a subset of logging directories, in the following locations:
Windows | install_path\NetBackup\logs install_path\Volmgr\debug |
UNIX | /usr/openv/netbackup/logs /usr/openv/volmgr/debug |
To use legacy logging, a log file directory must exist for a process. If the directory is not created by default, you can use the or the mklogdir batch files to create the directories. Or, you can manually create the directories. When logging is enabled for a process, a log file is created when the process begins. Each log file grows to a certain size before the NetBackup process closes it and creates a new log file.
Note:
It is recommended to always use the mklogdir utility present in Windows and Linux to create the legacy log directories for each platform, in order to have appropriate permissions on them.
You can use the following batch files to create all of the log directories:
Windows: install_path\NetBackup\Logs\mklogdir.bat
UNIX: /usr/openv/netbackup/logs/mklogdir
Follow these recommendations when you create and use legacy log folders:
Do not use symbolic links or hard links inside legacy log folders.
If any process runs for a non-root or non-admin user and there is no logging that occurs in the legacy log folders, use the mklogdir command to create a folder for the required user.
To run a command line for a non-root or non-admin user (troubleshooting when the NetBackup services are not running), create user folders for the specific command line. Create the folders either with the mklogdir command or manually with the non-root or non-admin user privileges.