Now that we have described the types of files to be backed up, the frequency of backup needed, and the locations of what needs to be backed up, you may use third-party tools or commands to perform your filesystem backups. The backup commands and instructions in this section are meant to serve as workable guidelines to cover all areas requiring backup and are general in nature. They assume a Linux-based operating system with gtar installed, but they may be substituted with alternative file manipulation commands as needed. We recommend that you dedicate a backup mount point with ample storage and timestamp each backup file with the date and time in the file name. Many backup solutions that can be leveraged to automate and simplify the administration of the entire backup process are available on the market.
The Oracle system files are comprised of server specific files under the /etc system directory as well as beahomelist.
- Set up your environment if it is not already set up using the following commands. This may vary depending on your installation:
export BACKUP_DIR=/backup export TIME=`date "+%Y%m%d_%k%M"`
- Execute the following commands to take a backup of the Oracle system files under
/etcand/home/oracle/bea:gtar -czvf $BACKUP_DIR/etcora.${TIME}.tgz /etc/oraInst.loc /etc/oratab gtar -czvf $BACKUP_DIR/beahomelist.${TIME}.tgz /home/oracle/bea
Back up the JDK as per the following instructions and modify the directory locations accordingly:
- Set up your environment if it is not already set up. This may vary depending on your installation:
export BACKUP_DIR=/backup export JAVA_HOME=/u01/oracle/products/jdk1.7.0_55 export TIME=`date "+%Y%m%d_%k%M"`
- Execute the following command to take a backup of the JDK:
gtar -czvf $BACKUP_DIR/jdk.${TIME}.tgz $JAVA_HOME
Oracle SOA Home consists of several installed components such as WebLogic Server, SOA Suite, OSB, coherence, shared libraries and utilities, and more. Back up the JDK as per the following instructions:
- Set up your environment if it is not already set up. This may vary depending on your installation:
export BACKUP_DIR=/backup export ORACLE_HOME=/u01/oracle/products/Oracle_SOA1 export TIME=`date "+%Y%m%d_%k%M"`
- Execute the following command to take a backup of the files:
gtar -czvf $BACKUP_DIR/oraclehome.${TIME}.tgz $ORACLE_HOME
The Domain Home is sometimes created under the $ORACLE_HOME/user_projects/domains directory, but it is not a requirement and often is different in clustered installations. It is only necessary to take a back up of the domain on which AdminServer is running, but you may also opt to take a back up of the domain on all other nodes of the cluster for ease of restoration in future using the following instructions:
- Set up your environment if it is not already set up. This may vary depending on your installation:
export BACKUP_DIR=/backup export DOMAIN_NAME=soa_domain export DOMAIN_HOME=/u01/oracle/products/Oracle_SOA1/user_projects/domains/${DOMAIN_NAME} export TIME=`date "+%Y%m%d_%k%M"`
- Execute the following command to take a backup of the files:
gtar -czvf $BACKUP_DIR/domain.${TIME}.tgz $DOMAIN_HOME
Contact your DBA and use a backup utility such as RMAN to perform nightly hot backups.
Another crude way to take a backup of your database is to use Oracle Data Pump utility commands, such as expdp, that can be used to export the database schemas and the impdp command that is used to import the dump file to the database. Because these are the low-level database methods, this approach is more suitable when performing an initial data migration to a fresh installation or the cloning of an environment that does not contain any business data yet.