此内容没有您所选择的语言版本。

Chapter 3. Backup and Restore


This chapter outlines the methods to back up, verify, and restore a Satellite system.
Backups should be conducted either nightly or weekly, depending on the amount of data being stored, and how much data you could tolerate losing in the case of a system outage.
It is recommended that database backups are performed during a scheduled maintenance outage for the RHN Satellite, as all services will become unusable for website and client connections during the backup.

3.1. Backups

Procedure 3.1. Backing up the Embedded Database

  1. Stop the RHN Satellite server using the stop command:
    rhn-satellite stop
    
    Copy to Clipboard Toggle word wrap
  2. Switch to the Oracle user, and create the backup using the db-control utility:
    su - oracle
    db-control backup [directory]
    
    Copy to Clipboard Toggle word wrap
    Replace directory with the absolute path to the location where you want to store your database backup. The process will take several minutes.
  3. Switch back to the root user, and start the Satellite:
    exit
    rhn-satellite start
    
    Copy to Clipboard Toggle word wrap
  4. Switch to the Oracle user, and use the examine option of db-control to check the backup time stamp and to determine if there are any missing files:
    su - oracle
    db-control examine [directory]
    
    Copy to Clipboard Toggle word wrap
    You can also use the verify option of db-control to conduct a thorough review, which includes checking the md5sum of each of the files in the backup:
    db-control verify [directory]
    
    Copy to Clipboard Toggle word wrap
    If the verification is successful, the contents of directory are safe to be used to restore the database.

Note

Users of external databases should also perform periodic backups. Consult your external database administrator for more information on supported backup procedures.

Backing up System Files

In addition to the database, a number of system files and directories should also be backed up. The files and directories that should be backed up are:
  • /etc/sysconfig/rhn/
  • /etc/rhn/
  • /etc/sudoers
  • /etc/tnsnames.ora
  • /var/www/html/pub/
  • /var/satellite/redhat/[0-9]*/ (This is the location for any custom RPMs)
  • /root/.gnupg/
  • /root/ssl-build/
  • /etc/dhcpd.conf
  • /etc/httpd/
  • /tftpboot/
  • /var/lib/cobbler/
  • /var/lib/nocpulse/
  • /var/lib/rhn/kickstarts/
  • /var/www/cobbler/
If possible, back up /var/satellite/ as well. This is a duplicate of the Red Hat RPM repository, and it will save a large download when recovering from a failure. It can be regenerated with the satellite-sync tool. If you are using a disconnected satellite, /var/satellite/ must be backed up in order to be able to recover from failure.
Backing up only the files and directories listed above would require reinstalling the RHN Satellite Server ISO RPMs and re-registering the satellite in order to recover from a failure. In addition, Red Hat packages would need to be resynchronized using the satellite-sync tool, and the /root/ssl-build/rhn-org-httpd-ssl-key-pair-MACHINE_NAME-VER-REL.noarch.rpm package would need to be installed. Alternatively, you could reinstall the RHN Satellite without re-registering it. This can be achieved by canceling or skipping the Red Hat Network registration and SSL certificate generation sections.
The most comprehensive backup method is to back up the entire machine. This method saves time in downloading and re-installing, but also requires additional storage and time to perform the backup.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2026 Red Hat