Monitoring the upgraded server

When you start to use the upgraded server in production operation, monitor the space that is used by the server to ensure that the amount of space is adequate. Adjust the space if needed.

To monitor the V7.1 server and make any required adjustments, complete the following steps:

1. Monitor the active log to ensure that the size is correct for the workload that is handled by the server instance.

   When the server workload reaches its typical expected level, the space that is used by the active log is 80% - 90% of the space that is available to the active log directory. At that point, you might need to increase the amount of space. Whether you must increase the space depends on the types of transactions in the server workload. Transaction characteristics affect how the active log space is used.

   The following transaction characteristics can affect the space usage in the active log:

   • The number and size of files in backup operations
     • Clients such as file servers that back up large numbers of small files can cause large numbers of transactions that are completed quickly. The transactions might use a large amount of space in the active log, but for a short time.
     • Clients such as a mail server or a database server that back up large chunks of data in a few transactions can cause small numbers of transactions that take a long time. The transactions might use a small amount of space in the active log, but for a long time.
   • Network connection types
     • Backup operations that occur over fast network connections cause transactions that are completed more quickly. The transactions use space in the active log for a shorter time.
     • Backup operations that occur over relatively slower connections cause transactions that take a longer time to be completed. The transactions use space in the active log for a longer time.

   If the server is handling transactions with a wide variety of characteristics, the space that is used for the active log might increase and decrease significantly over time. For such a server, you might need to ensure that the active log typically has a smaller percentage of its space used. The extra space allows the active log to grow for transactions that take a long time.

2. Monitor the archive log to ensure that space is always available.
   Remember: If the archive log becomes full, and the archive failover log becomes full, the active log can become full, and the server stops. The goal is to make enough space available to the archive log so that it never uses all available space.
   You are likely to notice the following pattern:
   1. Initially, the archive log grows rapidly as typical client-backup operations occur.
   2. Database backups occur regularly, either as scheduled or done manually.
   3. After full database backups occur, log pruning occurs automatically. The space that is used by the archive log decreases when the pruning occurs.
   4. Normal client operations continue, and the archive log grows again.
   5. Database backups occur regularly, and log pruning occurs as often as full database backups occur.

   With this pattern, the archive log grows initially, decreases, and then might grow again. Over time, as normal operations continue, the amount of space that is used by the archive log should reach a relatively constant level.

   If the archive log continues to grow, consider taking one or both of these actions:

   • Add space to the archive log. You might need to move the archive log to a different file system.
   • Increase the frequency of full database backups so that log pruning occurs more frequently.
3. If you defined a directory for the archive failover log, determine whether any logs are stored in that directory during normal operations. If the failover log space is being used, consider increasing the size of the archive log. The goal is to use the archive failover log only under unusual conditions, not in normal operation.