Should we upgrade OmniBackII 3.10 ot 3.50

[Gulam Mohiuddin]

At present we take backups with OBII 3.0 for 4 HP-UX 11.0 and 5 NT boxes on two DLT 7000 4/48.

Recently we wanted to implement online database backups of Oracle 8.1.6 database with RMAN and OmniBackII 3.0, but it failed and according to HP support OBII 3.0 and Oracle 8.1.6 are not supported. HP support informed us to upgrade OBII 3.10 or OBII 3.50.

Now we need to decide what version of OmniBack we should upgrade without much disturbing the current set up.

I think we should upgrade to OBII 3.10, which will require minimum changes as compared to OBII 3.5.

So which is better option OBII 3.10 or OBI 3.5. Are there any known major issues with OBII 3.5 related to Oracle backup.

Also, do we need to upgrade the NT client /Console as well, because NT Administrators use their own NT console to take backups of all NT boxes to a different DLT library 7000 4/48.

What are your suggestions for this situation.

Thanks,

Gulam.

[Shannon Petry]

Funny how someone working in unix seems to be pushing win2K on people :)

Anyhow, I have been running Omniback 3.5 since release in June of 2000, with no problems.

More device support, lots of bug fixes for too many things to mention. I use OBII, 3.5 to backup up 2 UNIX networks of 300GB or so including Oracle, DNS, Squid Proxy, NIS/NIS+ servers, Sendmail/Imap Servers, 2NT boxes (just print/file servers for windblows).

Anyway, 3.0 and 3.1 have many bugs, and problems with certain database problems. The upgrade will require a write-ascii, then read-ascii (which is good to clean things up anyway), and you will be fine.

regards,
Shannon

[Dave Wherry]

From what I've been told there are not many functional differences between 3.1 and 3.5. Just support for new systems like Win 2K, maybe some new hardware and of course bug fixes. I suggest 3.5 as it is more current with fixes.
From what I've heard the next generation of OB is in beta. It promises many changes although I have not heard specifics. I think 3.5 would carry you for quite some time while the dust settles on the new version after it is released.