Checklist for server hardware and operating system

Use the checklist to verify that the system where the server is installed meets requirements for hardware and software configuration.

Question Tasks, characteristics, options, or settings More information
Does the operating system and hardware meet or exceed requirements?
  • Number and speed of processors
  • System memory
  • Supported operating system level
If you are using the minimum required amount of memory, you can support a minimal workload.

You can experiment by adding more system memory to determine whether there is a boost to performance. Then, decide whether you want to keep the system memory dedicated to the server. Test the memory variations by using the entire daily cycle of the server workload.

If you run multiple servers on the system, add the requirements for each server to get the requirements for the system.

Review operating system requirements at Tivoli® Storage Manager Supported Operating Systems. Additionally, review guidance in Tuning tasks for operating systems and other applications.

For more information about requirements when these features are in use, see the following topics:

To help you determine whether processor or memory characteristics are the cause of performance problems, see Identifying server performance problems.

For more information about server and storage sizing requirements, see the Tivoli Storage Manager Blueprint at https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli Storage Manager/page/NEW - Tivoli Storage Manager Blueprint - Improve the time-to-value of your deployments.

Are disks configured for optimal performance? The amount of tuning that can be done for different disk systems varies. Ensure that queue depths and other disk system options are set appropriately. For more information, see the following checklists for disks:
Does the server have enough memory? Heavier workloads and advanced features such as data deduplication and node replication require more than the minimum system memory that is specified in the system requirements document.
For databases that are not enabled for data deduplication, use the following guidelines to specify memory requirements:
  • For databases less than 500 GB, you need 16 GB memory.
  • For databases with a size of 500 GB - 1 TB, you need 32 GB memory.
  • For databases with a size of 1 TB - 1.5 TB, you need 48 GB memory.
  • For databases greater than 1.5 TB, you need 64 GB memory.

Ensure that you allocate extra space for the active log and the archive log during replication processing.

For more information about requirements when these features are in use, see the following topics:

To help you determine whether processor or memory characteristics are the cause of performance problems, see Identifying server performance problems.

Does the system have enough host bus adapters (HBAs) to handle the data operations that the Tivoli Storage Manager server must run simultaneously? Understand what operations require use of HBAs at the same time.

For example, a server must store 1 GB/sec of backup data while also doing storage pool migration that requires 0.5 GB/sec capacity to complete. The HBAs must be able to handle all of the data at the speed required.

See Tuning HBA capacity.
Is network bandwidth greater than the planned maximum throughput for backups? Network bandwidth must allow the system to complete operations such as backups in the time that is allowed or that meets service level commitments.

For node replication, network bandwidth must be greater than the planned maximum throughput.

For more information, see the following topics:
Are you using a preferred file system for Tivoli Storage Manager server files? The choice of file system is an important factor in the performance of the Tivoli Storage Manager server.

Use a file system that provides advanced features to ensure optimal performance and data availability. The Tivoli Storage Manager server uses direct I/O with file systems that support the feature. Using direct I/O can improve throughput and reduce processor use.

The following is a list of preferred file systems for each operating system:
  • AIX®: Use the JFS2 file system with the rbrw option.
  • HP-UX: Use the VxFS file system.
  • Linux: Use either the ext3 or ext4 file system for the database, recovery log, and storage pool data. As a best practice, use the following file system that is appropriate for your operating system and level:
    • For Red Hat Enterprise Linux x86_64, use the ext3 or ext4 file system. Use the ext4 file system only if Red Hat Enterprise Linux 6.4 or later is installed.
    • For SUSE Linux Enterprise Server and for Red Hat Enterprise Linux ppc64, use the ext3 file system.
  • Solaris: Use the ZFS file system.
  • Windows: Use New Technology File System (NTFS) without compression.
For more information, see Configuring the operating system for disk performance.
Have you configured enough paging space? Paging space, or swap space, extends the memory that is available for processing. When the amount of free RAM in the system is low, programs or data that are not in use are moved from memory to paging space. This action releases memory for other activities, such as database operations.

For AIX, Linux, HP-UX, and Solaris systems, use a minimum of 32 GB of paging space or 50% of your RAM, whichever value is larger.

On Windows systems, paging space is automatically configured.

 
Did you tune kernel parameters after installation of the server? You must tune kernel parameters for servers that are on HP-UX, Linux, or Oracle Solaris systems.
See the information about tuning kernel parameters for your operating system: Not all operating systems require that kernel parameters be tuned.