Skip to main content

backup Satellite (embedded) database

A simple script to backup the embedded Oracle database included with Satellite 5.4.1


[root@rhnsat01 Satellite]# cat db_backup.sh 
#!/bin/bash

PRETTY_DATE=`date +%Y%m%d`
BACKUP_DIR=/rhnsat-backup/${PRETTY_DATE}
OUTPUT_LOG=/var/log/rhnsat-backup.log

mkdir ${BACKUP_DIR}
if [ ! -d ${BACKUP_DIR} ]
then
  echo "ERROR: unable to create Backup Dir: ${BACKUP_DIR}"
  exit 9
fi

# MESSAGE TO USER ON CONSOLE
echo "NOTE: you can find output at: ${OUTPUT_LOG}"

# BEGIN LOGGING OF THE SCRIPT OUTPUT
echo "Script ran at: `date +%Y%m%d-%H%M`" > ${OUTPUT_LOG}
echo "start: `date +%Y%m%d-%H%M`" >> ${OUTPUT_LOG}

# UPDATE PERMISSIONS OF THE BACKUP DIRECTORY TO ALLOW ORACLE
# TO WRITE
echo "chown -R oracle:dba /rhnsat-backup/*" >> ${OUTPUT_LOG}
chown -R oracle:dba /rhnsat-backup/* >> ${OUTPUT_LOG}

# CREATE A REPORT OF THE CURRENT ORACLE DB USAGE
echo "su - oracle -c \"/usr/bin/db-control report\"" >> ${OUTPUT_LOG}
su - oracle -c "/usr/bin/db-control report" >> ${OUTPUT_LOG}

# STOP SATELLITE SERVER (SHUTDOWN DB)
echo "/usr/sbin/rhn-satellite stop" >> ${OUTPUT_LOG}
/usr/sbin/rhn-satellite stop >> ${OUTPUT_LOG}

# RUN BACKUP VIA db-control UTILITY
echo "su - oracle -c \"/usr/bin/db-control backup $BACKUP_DIR\"" >> ${OUTPUT_LOG}
su - oracle -c "/usr/bin/db-control backup $BACKUP_DIR" >> ${OUTPUT_LOG}

# START SATELLITE SERVER
echo "/usr/sbin/rhn-satellite start" >> ${OUTPUT_LOG}
/usr/sbin/rhn-satellite start >> ${OUTPUT_LOG}

# EXAMINE DB BACKUP INTEGRITY
echo "/usr/bin/db-control examine ${BACKUP_DIR}" >> ${OUTPUT_LOG}
/usr/bin/db-control examine ${BACKUP_DIR} >> ${OUTPUT_LOG}
echo "NOTE: To examine backup fully use" >> ${OUTPUT_LOG}
echo "      su - oracle -c \"/usr/bin/db-control verify ${BACKUP_DIR}\"" >> ${OUTPUT_LOG}
echo "NOTE: To restore from this backup, use:" >> ${OUTPUT_LOG}
echo "      su - oracle -c \"/usr/bin/db-control restore ${BACKUP_DIR}\"" >> ${OUTPUT_LOG}

# INDICATE FINISH TIME IN LOG
echo "finish: `date +%Y%m%d-%H%M`" >> ${OUTPUT_LOG}

exit 0
# ***************************
# NOTES
# ***************************
# /etc/cobbler
# /var/satellite

Comments

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.