Avamar: RMAN plug-in: Oracle issue Triage Guide
Summary: This article is the Oracle RMAN plug-in triage guide for Avamar and Integration Data Protection Appliance.
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
When working with issues relating to the Oracle RMAN, the following steps should be performed.
Gather information from the Oracle Server.
2) Collect the Avamar RMAN Client plug-in version by running ./avoracle --version
3) The name of the Oracle instance being backed up (ORACLE_SID) and Path of ORACLE_HOME used for the backup.
4) Is it a stand-alone, or clustered environment? If clustered, gather the node names that are part of the cluster.
5) Is the version of Oracle compatible with the Avamar RMAN Plugin release used? See the Avamar compatibility guide.
Review the RMAN output.
For backup issues:
1) RMAN output can be located at:
For UI backups: <Avamar_directory_install>/var/clientlogs (<Avamar_directory_install>/ora_rac/var/clientlogs if it is an Oracle RAC backup).
Example of an RMAN file created by the UI: MOD-1662044793811-1002-Oracle_RMANorcl21c-rman1.log
These files can be identified by the end of their name which is: rman1.log
For CLI backups: Ask the DBA for the RMAN output.
2) Review the RMAN output for any error messages, and compare with any known issues in Knowledge Base.
3) Verify that the client for which the Oracle backup fails can conduct regular file system backups.
If regular file system backups fail, resolve those errors before any further RMAN troubleshooting.
4) If the backup is done from CLI check the flagfile can be used to backup files.
5) If the backup is run using the CLI and a taskfile, confirm the backup works without the taskfile. This helps narrow the scope of the behavior.
For additional information about Avamar RMAN Plugin log files, and enabling debug to further help an investigation, see the following article:
Gather information from the Oracle Server.
1) operating system version:
Take the output of the following commands:
Take the output of the following commands:
- On UNIX and Linux: Run uname -a and cat /etc/*release
- On Windows: From a command prompt, run winver
2) Collect the Avamar RMAN Client plug-in version by running ./avoracle --version
version: 7.5.101-3 build date: Sep 2 2017 09:26:50 msg format: 13-10 SSL: TLSv1 OpenSSL 1.0.2a-fips 19 Mar 2015 Zlib: 1.2.7 LZO: 1.08 Jul 12 2002 platform: Linux OS version: SLES-64 Processor: x86_64
3) The name of the Oracle instance being backed up (ORACLE_SID) and Path of ORACLE_HOME used for the backup.
4) Is it a stand-alone, or clustered environment? If clustered, gather the node names that are part of the cluster.
5) Is the version of Oracle compatible with the Avamar RMAN Plugin release used? See the Avamar compatibility guide.
Review the RMAN output.
For backup issues:
1) RMAN output can be located at:
For UI backups: <Avamar_directory_install>/var/clientlogs (<Avamar_directory_install>/ora_rac/var/clientlogs if it is an Oracle RAC backup).
Example of an RMAN file created by the UI: MOD-1662044793811-1002-Oracle_RMANorcl21c-rman1.log
These files can be identified by the end of their name which is: rman1.log
For CLI backups: Ask the DBA for the RMAN output.
2) Review the RMAN output for any error messages, and compare with any known issues in Knowledge Base.
3) Verify that the client for which the Oracle backup fails can conduct regular file system backups.
If regular file system backups fail, resolve those errors before any further RMAN troubleshooting.
4) If the backup is done from CLI check the flagfile can be used to backup files.
avtar -c --label="TEST_BACKUP" --flagfile=<flagfile> /etc/hostsIf avtar fails with a flagfile, this must be resolved before continuing RMAN troubleshooting.
5) If the backup is run using the CLI and a taskfile, confirm the backup works without the taskfile. This helps narrow the scope of the behavior.
For restore issues:
1) Identify the issue by reviewing the RMAN output looking for errors
RMAN output can be located at:
For UI backups: <Avamar_directory_install>/var/clientlogs (<Avamar_directory_install>/ora_rac/var/clientlogs if it is an Oracle RAC backup).
These files can be identified by names which end in: rman1.log and rman2.log
For CLI backups: Asked the DBA for the RMAN output.
2) Review the RMAN output for any error messages, and compare with any known issues in Knowledge Base.
3) For UI restores, verify:
1) Identify the issue by reviewing the RMAN output looking for errors
RMAN output can be located at:
For UI backups: <Avamar_directory_install>/var/clientlogs (<Avamar_directory_install>/ora_rac/var/clientlogs if it is an Oracle RAC backup).
These files can be identified by names which end in: rman1.log and rman2.log
For CLI backups: Asked the DBA for the RMAN output.
2) Review the RMAN output for any error messages, and compare with any known issues in Knowledge Base.
3) For UI restores, verify:
- ALL directories where the database is restored are precreated. Oracle has permission to write to them.
- Oracle Database is in nomount mode before starting the restore.
- Avamar allows you to restore to a different computer. The directory tree where the database resides must be identical to the production database. The same applies if the restore is done to Oracle ASM Groups.
- The UI does not support granular restores. It will always try to restore control file, datafiles, and apply archivelogs. It is not possible to restore a datafile or a set of archivelogs.
Affected Products
Avamar Plug-in for OracleArticle Properties
Article Number: 000202961
Article Type: How To
Last Modified: 20 Jul 2023
Version: 2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.