Oracle Solaris: System requirements for Oracle Solaris systems
The Tivoli® Storage Manager server can require a large amount of memory, network bandwidth, and processor resources. In many cases, the server performs best when other applications are not installed on the same system.
Hardware requirements
These tables list the minimum hardware and software requirements for the installation of a Tivoli Storage Manager server. Use these requirements as a starting point. You can find the most current information about system requirements at Tivoli Storage Manager Supported Operating Systems.
See IBM Tivoli Storage Manager Optimizing Performance (V7.1.1) for server configuration guidelines and best practices.
Table 1 describes the minimum hardware requirements that are needed for your Tivoli Storage Manager Solaris system. The installation fails if you do not have the minimum requirements. For more details about planning disk space, see Oracle Solaris: Capacity planning.
Type of hardware | Hardware requirements |
---|---|
Hardware | One of the following processors is required:
|
Disk space | The following list is the minimum values for
disk space for Ultra SPARC-based processors (sun4u and sun4v architecture)
for the respective directories and logs:
Significant additional disk space is required for database and log files. The size of the database depends on the number of client files to be stored and the method by which the server manages them. The default active log space is 16 GB, the minimum that is needed for most workloads and configurations. When you create the active log, you need at least 64 GB in size to run replication. If replication and data deduplication are both being used, create an active log of 128 GB in size. Allocate at least three times the default active log space for the archive log (48 GB). Ensure that you have sufficient resources if you are using data deduplication or expect a heavy client workload. For optimal performance and to facilitate I/O, specify at least two equally sized containers or Logical Unit Numbers (LUNs) for the database. See IBM Tivoli Storage Manager Optimizing Performance (V7.1.1) for more information about the configuration of directories for the database. In addition, each active log and archive log should have its own container or LUN. Ensure that you see the capacity planning section for more details about disk space. |
Memory | The following minimum values for memory:
Tip: Ensure that there is at least twice as much
swap space allocated as there is physical memory on the system.
|
Software requirements
Table 2 describes the minimum software requirements that are needed for your Tivoli Storage Manager Solaris system.
Type of software | Minimum software requirements |
---|---|
Operating system | Oracle Solaris 10 Update 10 on SPARC, running
in 64-bit kernel system with sun4u or sun4v architecture
|
Communication protocol | TCP/IP |
Device drivers | The Tivoli Storage Manager device driver required for non-IBM® drives and tape libraries. The Tivoli Storage Manager device driver package contains device driver tools and ACSLS daemons. For the IBM 3590, 3592, or the Ultrium tape library or drives, the IBM device drivers are required. Install the most current device drivers. You can locate IBM driver packages at the Fix Central website: http://www.ibm.com/support/fixcentral/. Configure the device drivers before you use the Tivoli Storage Manager server with tape devices. |
Gunzip utility | The gunzip utility must be available on your system before you install or upgrade the Tivoli Storage Manager Version 7 server. Ensure that the gunzip utility is installed and the path to it is set in the PATH environment variable. |
Other software | Korn Shell (ksh) |