Omniback and MC/SG

[Gerald Penyweit]

I am using Omniback as my Enterprise backup solution, and I have MC/SG running with Oracle.
How do I configure Omniback as a package that will fail over to the standby server in the cluster when there is a failure such as can't write to DLT library, etc. Has anyone done this
configuration with MC/SG?

thks,

gcp

[Vincenzo Restuccia]

You can see
http://ovweb.external.hp.com/lpe/cgi-bin/doc_serv/prod_req2.pl?ombak3.5

[Eddie Warren]

Gerald,
I am not sure why you would want to do this? For one thing, your tape library will need a physical connections to both systems. Your robot (picker) will still only be connected to one node and would have to manually switched on a failover (this is if you are even using a tape library). It would be just as easy to have omniback installed on the disk array that is shared by both systems and mount it on a failover.

[Celso Medina Kern]

Omniback can be configured as a High Available Package in MC/SG according to the instructions in B6960-90025 (Administrators Guide - Chapter 13 - Integration with other applications). It is easy and straithforward. This guide is under directory /opt/omni/doc/C named adminux.pdf.

The point is you also want this package to be a device server. To accomplish that you will need both nodes accessing the library devices and robot and use ATS(Advanced Tape Service) to manage access to them. This is usually done through fibre channel connection and Bridge/FC muxes that allow more than one host accessing devices under it. This is a standard solution if your backup server is a mission critical application.