Backing up Distributed Server Option log files

If you restart the  or reactivate  logging after deactivating it, each  server and pool log file is emptied and restarted. By default, a .bak extension is added to the previous log file name to create a backup log file.

The  Java server does not support appending to the existing log file.

Creating indexed backups of  Java log files

By default, the maximum size of Java-based  server and pool log files is 10 MB. To change the maximum, specify a value for one of the following  configuration options:

• Maximum Log-File Size on the AR System Administrator: Server Information form's Log Files tab.
• Max-Log-File-Size in the  configuration file

When a  Java server or pool log file reaches the maximum size,  backs it up by appending an index number to it and starting a new log file.

For example, the first time the ardist.log file reaches the maximum size,  changes its file name to ardist.log.1 and then creates an empty ardist.log file. When that version of the ardist.log file reaches the maximum size,  renames it ardist.log.2, and so on.

To specify the number of indexed backup files to save, use the following option in the  configuration file:

DSO-Log-Max-Backup-Index

For more information, see Configuration-settings-C-D.

When a backup file is created after this maximum is reached, the oldest indexed backup file is deleted.

For example, if you set this option to 3, the following actions occur when a fourth indexed backup is saved:

• ardist.log.1 (the oldest indexed backup file) is deleted.
• ardist.log.2 is changed to ardist.log.1.
• ardist.log.3 is changed to ardist.log.2.
• The fourth backup is saved as ardist.log.3.

If you do not specify a value for DSO-Log-Max-Backup-Index, 5 indexed backups are saved for each  Java log file.