HP Data Protector interface for RMAN

Question

Hello,
I would appreciate if someone can share the experience of using HP Data Protector (... earlier it was called OmniBack) with RMAN for backup and recovery
I want to know the benefits of using the data protector interface. The cost implications are really high and I am of the opinion to use RMAN to backup on a disk and using normal filesystem backup of HP Data protector to take the backups on tape
This kind of arrangement would essentially require the dba to go to RMAN to find out which all files are required to be restored, then use data protector to find out the tape that needs recall. Restore required files using DP and use RMAN for recovery
Would the interface really make some difference? And would it be a good decision to spend so much on the Dataprotector interface for RMAN?
Regards
Sudhanshu Bhandari
Oracle 9i OCP DBA
PerotSystems TSI (UK) Ltd.

Answer 1

Hi,
I got here a setup that's like: HP DataProtector, PROD-DB, STANDBY-DB
Roughly, the PROD-DB is 350Gb.
I backup this via a standard HPDP filesystem backup (+-1hour to run) applied to the standby (Data Guard) database (shutdown at backup time).
I'm glad I got HPDP when I have to restore PROD-DB on TEST-DB.. 2 clicks and it's done.
Note that I don't use RMAN for that, it is somewhat not needed in this setup. What if some day i decide to use RMAN? I think that I'll use something kind of like what you propose. It allows you to:
. manage what/when to backup. For example, cron a TS1 backup at day 1, cron a TS2 backup at day 2, ... every day: filesystem backup/purge via HPDP.
. easily restore your DB provided your DBA knows some stuff about HPUX admin... (what if this is a HDD failure? how to fix EVAs? is this in a HP Cluster? ...?)
Anyway, to get back to your main question:
Would the interface really make some difference? Yes, of course. Nowadays lots of people don't like command line *sigh* and would be more attracted if it looks simpler (though it offers less possibilities). With an interface you'll certainly feel safe than via shell scripting.
And would it be a good decision to spend so much on the Dataprotector interface for RMAN?As for me, no. In the setup I explained at the beginning, I got many advantages over a RMAN backup, backed up via HPDP. First, it's simpler to manager: I just have to check my morning mail to see if the backup went OK. Then, I'm sure if I loose the main DB, I can switch to standby quickly (can't afford much downtime). This means that if all of this fails (uh oooh) I'll have to restore the tapes, and this will be the last thing I'd want to do because it'll take ages (+-3h for the whole thing).
In each of these steps I use a single tool.. reducing chair-computer interface error chances. Look how many different layers you'll get in your setup (4+).
This was my 2cents,
HTH
Yoann.
Of course, via RMAN, you don't backup empty space (compress), the recovery granularity is way better (blockrecover), etc. But the main question is: do you really need RMAN? If the answer is yes, then go on with the DP RMAN interface to easy your admin's life. If no, then just drop the idea.