Table of Contents
Advertisement
Chapter 8. Maintenance
utes. The first backup is a good indicator of how long subsequent backups will take.
Once the backup is complete, return to root user mode and restart the database and related
services with the following command:
service rhn-satellite start
You should then copy that backup to another system using rsync or another file-transfer
utility. Red Hat strongly recommends scheduling the backup process automatically using
cron jobs. For instance, back up the system at 3 a.m. and then copy the backup to the
separate repository (partition, disk, or system) at 6 a.m.
8.4.3. Verifying the Backup
Backing up the Embedded Database is useful only if you can ensure the integrity of the re-
sulting backup. RHN DB Control provides two methods for reviewing backups, one brief,
one more detailed. To conduct a quick check of the backup's timestamp and determine any
missing files, issue this command as oracle:
db-control
examine DIRNAME
To conduct a more thorough review, including checking the md5sum of each of the files in
the backup, issue this command as oracle:
db-control
verify DIRNAME
8.4.4. Restoring the Database
RHN DB Control makes Embedded Database restoration a relatively simple process. As
in the creation of backups, you will need to shut down the database and related services
first by issuing the following commands in this order as root:
service rhn-satellite stop
Then switch to the oracle user and issue this command, including the directory containing
the backup, to begin the restoration:
db-control
restore DIRNAME
This not only restores the Embedded Database but first verifies the contents of the backup
directory using md5sums. Once the restoration is complete, return to root user mode and
restart the database and related services with these commands in this order:
service rhn-satellite start
61
Advertisement
Table of Contents
