Backing up an RHN Satellite Server can be done in several ways. Regardless of the method chosen, the associated database also needs to be backed up. For the Stand-Alone Database, consult your organization's database administrator. For the Embedded Database, refer to Section 8.4 Using RHN DB Control for a complete description of this process and the options available.
Here are the minimum files and directories Red Hat recommends backing up:
/rhnsat/ - Embedded Database only (never to be backed up while the database is running - refer to Section 8.4.2 Backing up the Database)
/etc/sysconfig/rhn/
/etc/rhn/
/etc/tnsnames.ora
/etc/httpd/
/var/www/rhns/
/var/www/html/pub/
/var/satellite/redhat/1/ - custom RPMs
/etc/pxtdb.conf - pertains only to RHN Satellite Server 1.1.x.
If possible, back up /var/satellite/, as well. In case of failure, this will save lengthy download time. Since /var/satellite/ (specifically /var/satellite/redhat/NULL/) is primarily a duplicate of Red Hat's RPM repository, it can be regenerated with satellite-sync. Red Hat recommends the entire /var/satellite/ tree be backed up. In the case of disconnected satellites, /var/satellite/ must be backed up.
Backing up only these files and directories would require reinstalling the RHN Satellite Server ISO RPMs and reregistering the Satellite. In addition, Red Hat packages would need to be resynchronized using the satellite-sync tool. Finally, you would have to reinstall the /etc/sysconfig/rhn/ssl/rhn-org-httpd-ssl-key-pair-MACHINE_NAME-VER-REL.noarch.rpm.
Another method would be to back up all of the files and directories mentioned above but reinstall the RHN Satellite Server without reregistering it. During the installation, cancel or skip the RHN registration and SSL certificate generation sections.
The final and most comprehensive method would be to back up the entire machine. This would save time in downloading and reinstalling but would require additional disk space and back up time.