OmniBack V3.0 dead slow restore

[Roger Sager_1]

G'day folks,

We have a HP 9000 T600 O/S 10.20. We use HP's Omniback software to
backup/restore everything on our box including 6 Oracle databases, and 3 using
Oracle Application 10.7 SmartClient. We recently upgraded from Omniback II
v2.55 to A.03.00 version.

The backup of some 40 gigs onto 2 DTl tape drives takes approximately 2 and a
bit hours, or 1 hour and 20 minutes for an on demand backup of 1 database and
its application files (approx 1.8 gig). However, a restore of the same
database instance using this supposely latest and greatest Omniback II software
takes the better part of a bloody day??? Why???? HP's software upgrades are
very questionable?

Is there are one that knows how to tune Omniback to run faster, or a white
paper on this subject??

Or alternately, using Unix TAR or cpio backups to backup and restore 1.8 gigs
- anyone got a script?

Cheers...Roger Sager, Auscott's Brain-dead DBA

[Anthony Goonetilleke_1]

I know you probably won't like this but you might consider changing versions to
3.1 apparently there is a huge speed increment and a lot f the 3.0 bugs are
fixed. I am currently considering this after a few problems we have encountered
after upgrading to 3.0 from 2.55.

Alternatively have a look at
http://www.cs.umd.edu/projects/amanda/

It works realy well and its free.

[Samir Mohammed]

Did you export/import the Omniback database when upgrading from 2.55 to 3.0 ?

I have a setup using a DLT7000 tape library connected to an HP9000 K460 2-way.
A 40GB Oracle8 hot backup using 1 drive takes 1.5 hrs. The restore of 40GB of
data has taken me 2.5 hrs at a transfer speed of 4.5MB/sec. And I have not
done any changes as for performance enhancement.

If data is going over a lan, check speed and duplex mode. In your restore
window, turn on stats reporting so you can see data transfer rate info. Check
disk contention/thrashing through glance.

I think you are running into contention beyond the control of Omniback. I
would export/import the database to make sure its consistency is intact. If
your Omniback database is beyond 2GB, I highly recommend reducing by
eliminating old info and lowering the level of logging from file level to
directory level for non-database backups.