You can enable or disable compression of archive logs on
the Tivoli® Storage
Manager server.
By compressing the archive logs, you reduce the amount of space that
is required for storage. You also reduce the frequency with which
you must run a full database backup to clear the archive log.
Before you begin
Before you configure compression of archive logs, you must
consider the benefits. The results that you achieve might differ,
depending on your hardware and software environment, and the size
of the archive log files.
The following table shows the results
that were obtained in lab tests.
Table 1. Archive log compression
results during lab tests| |
Pre-compression Archive Log Average Size |
Post-compression Archive Log Average Size |
Archive Log Storage Space Reduction |
|---|
| Linux system |
299,799.98 MB
|
129,344.99 MB
|
57.00%
|
| Windows System |
223,542.11 MB
|
85,185.21 MB
|
62.00%
|
Procedure
- Enable dynamic compression of the archive log by issuing
the following command:
SETOPT ARCHLOGCOMPress Yes
- Verify that compression is enabled by issuing the QUERY
OPTION ARCHLOGCOMPRESS command.
Restriction: Use caution when you enable the ARCHLOGCOMPRESS server
option on systems with sustained high volume usage and heavy workloads.
Enabling this option in this system environment can cause delays in
archiving log files from the active log file system to the archive
log file system. This delay can cause the active log file system to
run out of space. Be sure to monitor the available space in the active
log file system after archive log compression is enabled. If the active
log directory file system usage nears out of space conditions, the ARCHLOGCOMPRESS server
option must be disabled. You can use the SETOPT command
to disable archive log compression immediately without halting the
server.