Maintenance Tasks

This section contains tasks you might need to perform after you install and confi your Backup server.

gure

Message Log Management

Backup stores the messages generated by the Backup server daemons in a message log file in the /nsr/logs directory. When the log file becomes too large, you have to delete some messages from the log. To automatically control the size of the log, you can use variables in the Backup startup script in the /etcdirectory or create a script that uses the operating system services.

How to Set the Startup Script to Trim Log Files

To modify the way that Backup services manage the Backup log files, change the following environmental variables in the Backup startup script, networkerin the /etc/init.ddirectory before you start the nsrd daemon:
*To change the maximum size of log files, change the NSR_MAXLOGSIZEvalue. The
default value for NSR_MAXLOGSIZEis 1024 KB.
*To change the maximum number of log files that are saved, change the
NSR_MAXLOGVERSvalue. The default value is 4.
Every time nsrdstarts, it checks the size of the daemon.logfile. By default, when the daemon.logfile reaches the 1024 KB limit, it is renamed daemon.001and a new empty daemon.logis created. If the daemon.logfile fills again, the names of each existing file shift so that the daemon.001file is renamed daemon.002, daemon.logis renamed daemon.001, and a new empty daemon.logfile is created. This process is repeated until the value in NSR_MAXLOGVERSis reached, at which point the highest numbered log is removed.

Caution - The trimming mechanism only functions when you start nsrd. The nsrddaemon does notcheck periodically to see whether the log file has exceeded NSR_MAXLOGSIZE. If nsrdruns for a long time, the log file can still grow very large. To activate the trimming mechanism, enter nsr_shutdownto stop the Backup daemons, then restart the nsrdand nsrexecddaemons.

Solstice Backup 5.1 Administration Guide*April 1998

52