IBM Tivoli Storage Manager: Messages

Appendix B. Allocating Additional Server Memory

If the server is low on memory, the following actions can be taken to allocate additional storage resource for the server:

• For AIX, ensure that there is sufficient paging space. You may also use SMIT to determine if the number of applications is causing a memory shortage.
• For VM, increase the size of the server's virtual machine. This requires that the default storage size be updated in the server's CP directory entry.
• For OS/390 and z/OS, increase the size of the REGION parameter on the JOB or EXEC statement of the JCL used to start the server.

  A minimum size of 128MB is recommended for Tivoli Storage Manager, but larger servers will require a larger region size.

• For Windows, the preferred method of solving a low memory condition is to add physical memory to the system. Otherwise, increase the amount of the system's virtual memory. This can be done from the control panel by running the system applet and increasing the total paging file size.
• For HP-UX, ensure that there is sufficient paging space and that a sufficient amount of shared memory is available. For information on shared memory, refer to the IBM Tivoli Storage Manager Quick Start.
• For Sun Solaris, ensure that there is sufficient paging space. Consult your Sun Solaris system documentation for details.

Reduce the maximum number of client sessions permitted. To do this, update the value of the MAXSESSIONS parameter in the server options file and restart the server.

Decrease the amount of space allocated to the server's database or log buffer pool. To do this, update the value of the BUFPOOLSIZE or LOGPOOLSIZE parameters in the server options file and restart the server. Note that each page causes an additional 4KB page to be allocated for the specified buffer pool. Reducing the pool sizes requires more I/O to service the same amount of data; some performance degradation may result.