Verifying the Backup67off-site. To conduct a backup, shut down the database and related services first by issuing thefollowing command as root:/usr/sbin/rhn-satellite stopThen switch to the oracle user and issue this command to initiate the backup:db-control backup DIRNAMEBackup files are stored in the directory specified. Note that this is a cold backup; the database must bestopped before running this command. This process takes several minutes. The first backup is a goodindicator of how long subsequent backups will take.Once the backup is complete, return to root user mode and restart the database and related serviceswith the following command:/usr/sbin/rhn-satellite startYou should then copy that backup to another system using rsync or another file-transfer utility. RedHat 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, orsystem) at 6 a.m.8.4.3. Verifying the BackupBacking up the Embedded Database is useful only if you can ensure the integrity of the resultingbackup. 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 thiscommand as oracle:db-control examine DIRNAMETo 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 DIRNAME8.4.4. Restoring the DatabaseRHN DB Control makes Embedded Database restoration a relatively simple process. As in thecreation of backups, you will need to shut down the database and related services first by issuing thefollowing commands in this order as root:/usr/sbin/rhn-satellite stopThen switch to the oracle user and issue this command, including the directory containing the backup,to begin the restoration: