Table of Contents
Advertisement
Chapter 2. Requirements
Stand-Alone Database
Table 2-1. Stand-Alone Database and Embedded Database Satellite Hardware Requirements
The following hardware configuration is required for the Stand-Alone Database:
Dell PowerEdge 2650 or equivalent
•
Two processors
•
2 GB of memory
•
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 in which client systems connect to the Satellite is directly related to load
on the Apache HTTP Server and the database. If you do reduce the default interval of four hours (or
240 minutes), as set in the
you will increase the load on those components significantly.
Additional hardware requirements include:
The Stand-Alone Database must not run on the same server as the RHN Satellite Server.
•
The package repository may be any large storage device easily and securely accessed by the other
•
components. The space requirements depend on the number of packages that will be stored. Default
Red Hat channels contain approximately 3 GB of packages each, and that size grows with each
synchronization; customers must also account for the space requirements of packages in their own
private channels. Whatever storage solution the customer chooses, its mount point may be defined
during the installation process.
If you are installing RHN Satellite Server with Embedded Database, skip to Section 2.4 Additional
Requirements.
2.3. Database Requirements
This section applies only to RHN Satellite Server with Stand-Alone Database as the requirements
for the Embedded Database are included in the Satellite machine's hardware requirements. Red Hat
supports RHN Satellite Server 3.6 installations in conjunction with Oracle 9i R2. The Stand-Alone
Database must not run on the same server as the RHN Satellite Server.
A single 4 GB tablespace is recommended as more than sufficient for most installations. It is possible
for many customers to function with a smaller tablespace. An experienced Oracle database admin-
istrator (DBA) will be necessary to assess sizing issues. The following formula should be used to
determine the required size of your database:
192 KB per client system
•
64 MB per channel
•
For instance, an RHN Satellite Server containing 10 channels serving 10,000 systems would require
1.92 GB for its clients and 640 MB for its channels. If custom channels are to be established for testing
and staging of packages, they must be included in this formula.
/etc/sysconfig/rhn/rhnsd
Embedded Database
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.
configuration file of the client systems,
9
Advertisement
Table of Contents
