What considerations are there for where to put the Tivoli Storage Manager V6.1, V6.2, or V6.3 active log and archive log directories?
The recovery log for the Tivoli Storage Manager V6.1, V6.2, or V6.3 server is a combination of directories that represent the active log and the archive log. The placement and management of these two directories are important to the normal operation of the server.
When planning for Tivoli Storage Manager V6.x, consider the following information about the placement and configuration of these directories:
The active log directory is used to store information for in-progress transactions that are making changes to the server database. This space needs to be sized to hold the peak transaction workload that will be encountered for this server.
After an existing active log file is no longer needed, it is archived to the archive log directory. The movement of files from the active log directory to the archive log directory is done automatically by the server database manager, and is not configurable or tunable by a Tivoli Storage Manager administrator.
The active log directory needs to be placed on high availability, robust disk that has high performance capability. The directory needs to be its own unique directory or mount point. Do not use the same disk or mount point as is used by other server assets, such as the database or archive log. Similarly, do not use the same space for system tasks such as system paging or for other applications.
The archive log directory is used to store information for completed transactions. This information is stored to preserve the transaction history since the last full database backup. The archive log is used for roll-forward recovery so that the server database can be recovered to any point in time, from the time of the last full database backup to the current time. If the archive log is not available, you can restore the database only to those points in time for which database backups are available.
The archive log files are automatically deleted by the server through a pruning process that occurs at the completion of full database backups. Do not delete these files or manipulate them directly or through any other means.
The archive log directory needs to be placed on high availability, robust disk that has high performance capability. Compared to the disk used for the active log, this can be comparable or it could be of lower performance. This needs to be its own unique directory or mount point. Do not use the same disk or mount point as is used by other server assets, such as the database or active log. Similarly, do not use the same space for system tasks such as system paging or for other applications.