OMNIBACK - one job for oracle, 1 job for other

[Allan Zaebst_1]

I want to make sure that all data is backed up including files and oracle
databases that are created without informing me. I need one job for oracle
databases with a pre_exec to stop oracle and a post_exec to restart it. The
databases may be under any mount point. The second job needs to back up
anything but oracle databases and should be separate to minimize oracle
downtime. I have not figured out how to accomplish this - does anyone have a
technique for doing this?

[Dan Hull]

You can set up a datalist to include or exclude anything you like. Just set up
one scheduled job to back up the filesystems that have Oracle data and a sep.
one to do a filesystem backup of the remaining ones. Just make sure you
schedule enough time between the backups to make sure the first one finishes!

For more information, you may want to post a message on the "Networking &
Openview" forum, since Omniback is an Openview Product.

[Anthony Goonetilleke_1]

To expand on the last response the easiest way to do this using Omniback is to
define a host backup to backup the entire machine but exclude all the Oracle
filesystems from this backup.

The second backup will be a filesystem backup that includes all the Oracle
filesystems but make sure that you include your post and pre exec scripts (i.e.
startup and shutdown of Oracle) in the section under the options menu called
"For backup specification" rather than each individual filesystem as there is
no exact way to tell which one will run first finish first as it depends on a
lot of other factors.

[Roger Sager_1]

We have 6 Oracle instances running, 3 big mothers using Oracle
Financials/Distribution/Manufacturing suite of Apps. I found Omniback difficult
early on to configure, but the solution I use is

1- employ crontab execute steps to stop and start the oracle script usually
located in /sbin/init.d directory
to a time window run this script ie 45 min after midnite using the stop
parameter (/sbin/init.d/oracle stop) which stops all concurrent managers first
which is very, very important otherwise you get run away concurrent manager
processes, Next shutdown of the rdbms, and finally stop the listener. The
startup happens at say 3:30 in reverse order (listener startup, then startup
the instances, then start all concurrent managers)
2- set up the Omniback window to backup in this period when the Oracle
databases are down

This makes it simple and uncomplicated for Oracle cold backups. One note to
note - my mistake the Oracle databases never stopped one night, but Omniback
proceeded at the appointed time, and completed successfully. This implies that
Omni can do a hot backup, but I haven't tried to do a restore from this
session.

Anyways...if anyones interested in the scripts email with your request etc to
rsager@auscott.com.au

Cheers...Roger Sager