Avamar - Oracle RMAN backup failed with error "Failed to consolidate backup on Avamar server"

Summary: Avamar - Oracle RMAN backup failed with error "Failed to consolidate backup on Avamar server"

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.

Symptoms



An Avamar backup using Oracle RMAN fails with the error "Failed to consolidate backup on Avamar server"

Below is a log extract showing errors reported by the avoracle plug-in log session.  This appears at the very end of backup after all the avtar sessions have completed successfully
 
...
2020-03-20 15:53:56 avoracle Info <18470>: create_new_workorder: 9158
2020-03-20 15:53:56 avoracle Info <10684>: Setting ctl message version to 3 (from 1)
2020-03-20 15:53:56 avoracle Info <16136>: Setting ctl max message size to 268435456
2020-03-20 15:54:00 avoracle Info <0000>: sbtbackup: avtar started successfully
2020-03-20 16:54:35 avoracle Error <43210>: Failed to consolidate backup on Avamar server
2020-03-20 16:54:46 avoracle Info <6686>: Process 306793 (/usr/local/avamar/ora_rac/bin/avtar) for workorder Oracle_EMR_L0_Backup_Group-1584673881637#0 started
2020-03-20 16:55:59 avoracle Info <6688>: Process 306793 (/usr/local/avamar/ora_rac/bin/avtar) finished (code 0: success)
2020-03-20 16:55:59 avoracle Error <43351>: Failed to create the snapview. However, the database data has been successfully backed up and is marked as a hidden backup. Restore is available through CLI only. See the plug-in documentation for information about restoring hidden backups.

The log shows that after all the avtar sessions completed, the process got stuck for 1 hour before reporting the error  "Failed to consolidate backup on Avamar server".  This error occurred just before the Snapview session was started.

2020-03-20 16:54:35 avoracle Error <43210>: Failed to consolidate backup on Avamar server

- Logging shows that snapview session completed successfully
2020-03-20 16:54:46 avoracle Info <6686>: Process 306793 (/usr/local/avamar/ora_rac/bin/avtar) for workorder Oracle_EMR_L0_Backup_Group-1584673881637#0 started 2020-03-20 16:55:59 avoracle Info <6688>: Process 306793 (/usr/local/avamar/ora_rac/bin/avtar) finished (code 0: success)

- After snapview completed, avoracle prints another error: "Failed to create the snapview. However, the database data has been successfully backed up and is marked as a hidden backup. Restore is available through CLI only".

This backup is not actually hidden, it is visible from within Avamar User Interface (AUI) or the Java GUI, and it is restorable. The backup job in the activity monitor however does show that it failed. 


 

Cause

There were a huge number of avtar sessions which can cause avoracle to take a longer time to complete the wrapup process.  The wrapup process timed out after one hour.  

Resolution

The issue can worked around by reducing the number of avtar sessions which get created or by giving the wrapup process a longer time out via the wrapupprocesstimeoutsecs flag.

By default the Oracle plugin (avoracle) flag "
filesperset" is set to "1", This can be increased to "5" or higher.
Note that by increasing the filesperset value, it would impact the backup deduplication rate.


kA23a000000GJKyCAO_2_0

If the backup is using an RMAN script, add the flag to the rman script.  Below is an example:
allocate channel c0 maxopenfiles = 5 device type sbt;

And also can optionally add the avoracle flag in dataset to increase wrapup timeout, by default, it is 3600 secs:
--[avoracle]wrapupprocesstimeoutsecs=5400

To add special flags to change plugin behaviour refer to 
KB 490673 - How to supply specialised flags to Avamar backups

Affected Products

Avamar

Products

Avamar, Avamar Plug-in for Oracle
Article Properties
Article Number: 000078749
Article Type: Solution
Last Modified: 16 Jun 2025
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.