Avamar: Oracle Table Level Recovery with Avamar

Summary: Information about an Oracle 12c recovery using Avamar: set Recovery Manager (RMAN) channel Storage Backup Tool (SBT)_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so and avtar flag file (no --label number). Run RMAN RECOVER TABLE … UNTIL TIME 'SYSDATE‑n' AUXILIARY/DATAPUMP; clear channel. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Instructions

In Oracle 12c, the Table Level Recovery became a new restore option.

To perform an Oracle Table Level Recovery using an Avamar backup of a database the following can be used.
(The database backup should be taken using the Avamar UI.)

Once there is a valid "Full Backup" of the databases in Avamar, proceed with the following steps:

The following channel configuration must be added to the RMAN database configuration for the database needing the restore. This parameter can be cleared after the Table Level Recovery is done, if wanted.

The example channel configuration assumes that Oracle 12c and Linux are being used. Ensure all Avamar Client paths match the host operating system (OS),

configure channel 1 device type sbt PARMS="SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so" format '%d_%U' send '"--prefix=12/SID/" "--flagfile=/var/avamar/avtar_flagfile.txt" "--bindir=/usr/local/avamar/bin" "--logfile=/tmp/tbl_restore.out"';
 

The Avtar flag file should contain normal parameters.

For example:

--pidname=Oracle
--pidnum=1002
--bindir=/usr/local/avamar/bin
--vardir=/usr/local/avamar/var
--server=avamarserver
--id=xxxx
--ap=xxxx
--path=/domain/clientname
--expires=n
--ddr=true
--ddr-index=1
--incpartials
 

Ensure the avtar parameter --labelnumber=n is not used in the flag file.

Below is the RMAN Script required to perform the Table Level Recovery. 

Note: All parameters must be adjusted to the specific customer environment.
 
  • The "Recover Table Name" should have the Table Name being recovered, "NAME._somename."
  • Set the appropriate SYSDATE parameter to match the date of the database backup in Avamar being used for the recovery.
  • Auxiliary and Datapump Destination paths should be set per the customer environment.

    

RECOVER TABLE NAME._somename
UNTIL TIME 'SYSDATE-9'
AUXILIARY DESTINATION '/u01/somepath/dbdump'
DATAPUMP DESTINATION  '/u01/somepath/dbdump'
DUMP FILE 'somename_dump.dat'
NOTABLEIMPORT;
 

The end result should be that everything is restored, including all archivelogs being applied and the resulting data pump file is now created in the specified directory for the DBA to use as needed.     

Reference the following Oracle article for additional information: https://docs.oracle.com/database/121/BRADV/rcmresind.htm#BRADV703 (EXTERNAL LINK).

 

Affected Products

Avamar, Avamar Client, Avamar Plug-in for Oracle
Article Properties
Article Number: 000038655
Article Type: How To
Last Modified: 23 أبريل 2026
Version:  6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.