2.2. Hardware Requirements

The following hardware configuration is required for the two types of RHN Satellite Server:

Stand-Alone DatabaseEmbedded Database
Required - Pentium IV processor, 2.4GHz, 512K cache or equivalentRequired - Pentium IV processor, 2.4GHz, 512K cache or equivalent
Recommended - Pentium IV processor, 2.4GHz dual processor, 512K cache or equivalentRecommended - Pentium IV processor, 2.4GHz dual processor, 512K cache or equivalent
Required - 2 GB of memoryRequired - 2 GB of memory
Recommended - 4 GB of memoryStrongly recommended - 4 GB of memory
3 GB storage for base install of Red Hat Enterprise Linux AS3 GB storage for base install of Red Hat Enterprise Linux AS
6 GB storage per channel, in the /var/satellite/ directory by default but configurable at install6 GB storage per channel, in the /var/satellite/ directory by default but configurable at install
Recommended - an external SAN for more reliable backupsRecommended - an external SAN for more reliable backups
 12 GB storage for the database repository, in the /rhnsat partition (local storage only)
 Strongly recommended - a SCSI drive connected to a level 5 RAID
 Separate partition (or better, a separate set of physical disks) for storing backups. This can be any directory specifiable at backup time.

Table 2-1. Stand-Alone Database and Embedded Database Satellite Hardware Requirements

The following hardware configuration is required for the Stand-Alone Database:

See Section 2.3 Database Requirements for instructions on estimating the tablespace of the database and setting its environment variables.

Keep in mind, the frequency with which client systems connect to the Satellite is directly related to load on the Apache HTTP Server and the database. Reducing the default interval of four hours (or 240 minutes) as set in the /etc/sysconfig/rhn/rhnsd configuration file of the client systems significantly increases the load on those components.

Additional hardware requirements include:

If you are installing RHN Satellite Server with Embedded Database, skip to Section 2.4 Additional Requirements.