Using OEM to backup/restore DB using EMC Avamar (3rd party)

Question

Hi,
I'm trying to find a solution for using OEM to backup and restore DB using EMC Avamar software.
Normally, we can backup/restore DB using Avamar through RMAN CLI using scripts similar to the following:
connect target /
run {
configure controlfile autobackup on;
set controlfile autobackup format for device type sbt to 'CONTROLFILE.orcl.%F';
allocate channel c0 type sbt PARMS="SBT_LIBRARY=c:\PROGRA~1\avs\bin\orasbt64.dll" format '%d_%U';
send '"--prefix=11g/orcl/" "--flagfile=c:\flagfile\avtar-flags.txt" "--bindir=c:\PROGRA~1\avs\bin"';
backup database plus archivelog delete input;
release channel c0;
Where orasbt64.dll is the name of Avamar's 64bit library and flagfile contains some internal flags necessary for backup/restore operations.
Now, I want to use OEM for the same thing so, what I did was try to specify the Media Management Vendor Library Parameters under Backup Settings in OEM. I saved the following as the parameters:
"SBT_LIBRARY=c:\PROGRA~1\avs\bin\orasbt64.dll";
Even after this, the backup script generated by OEM does not contain this parameter. Naturally, backups to EMC Avamar fail.
I would like answers to these 2 questions:
1. How to correctly specify the Media Management Vendor Library Parameters?
2. Is there a way to specify all the parameters (--prefix, flagfile, bindir, PARMS etc.) so that the script generated by OEM is same (or as close as possible) to the one I use for RMAN CLI backups.
Thanks!

Answer 1

Hi Anant,
I'm also having the same issue. It fails because it doesn't understand the "send" command in OEM. Here is the output of the tape backup test:
RMAN> run {
2> allocate channel oem_sbt_backup type 'sbt_tape' format '%U' parms 'SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so,
3> ENV=(PATH=/bin:/usr/bin:/usr/local/avamar/bin);
4> send "--flagfile=/home/oracle/scripts/backup/my-avtar-flags.txt"';
5> backup as COMPRESSED BACKUPSET current controlfile tag '04302012033156';
6> restore controlfile validate from tag '04302012033156';
7> release channel oem_sbt_backup;
8> }
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on oem_sbt_backup channel at 04/30/2012 15:32:00
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27209: syntax error in device PARMS - unknown keyword or missing =
RMAN> allocate channel for maintenance type 'sbt_tape' parms 'SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so,
2> ENV=(PATH=/bin:/usr/bin:/usr/local/avamar/bin);
3> send "--flagfile=/home/oracle/scripts/backup/my-avtar-flags.txt"';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on ORA_MAINT_SBT_TAPE_1 channel at 04/30/2012 15:32:01
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27209: syntax error in device PARMS - unknown keyword or missing =
When I use TSM it doesn't require the "send" command and it backs up successfully. I guess the other option would be to create an EM job to do the backups. However, this wouldn't populate the EM tables for backup reporting.