When you estimate space requirements
for active and archive logs, include some extra space for contingencies
such as occasional heavy workloads and failovers.
In Tivoli® Storage
Manager servers
V6.1 and later, the active log can be a maximum size of 128 GB. The
archive log size is limited to the size of the file system that it
is installed on.
Use the following general guidelines when you estimate the size
of the active log:
- The suggested starting size for the active log is 16 GB.
- Ensure that the active log is at least large enough
for the amount of concurrent activity that the server typically handles.
As a precaution, try to anticipate the largest amount of work that
the server manages at one time. Provision the active log with extra
space that can be used if needed. Consider using 20% of extra space.
- Monitor used and available active log space. Adjust the size of
the active log as needed, depending upon factors such as client activity
and the level of server operations.
- Ensure that the directory that holds the active log is as large
as, or larger than, the size of the active log. A directory that is
larger than the active log can accommodate failovers, if they occur.
- Ensure that the file system that contains the active log directory
has at least 8 GB of free space for temporary log movement requirements.
The suggested starting size for the archive log is 48 GB.
The archive log directory must be large enough to contain the log
files that are generated since the previous full backup. For example,
if you perform a full backup of the database every day, the archive
log directory must be large enough to hold the log files for all the
client activity that occurs during 24 hours. To recover space, the
server deletes obsolete archive log files after a full backup of the
database. If the archive log directory becomes full and a directory
for archive failover logs does not exist, log files remain in the
active log directory. This condition can cause the active log directory
to fill up and stop the server. When the server restarts, some of
the existing active-log space is released.
After the server is installed, you can monitor archive
log utilization and the space in the archive log directory. If the
space in the archive log directory fills up, it can cause the following
problems:
- The server is unable to perform full database backups. Investigate
and resolve this problem.
- Other applications write to the archive log directory, exhausting
the space that is required by the archive log. Do not share archive
log space with other applications including other Tivoli Storage
Manager servers.
Ensure that each server has a separate storage location that is owned
and managed by that specific server.