In this post we will review the best practices when installing, configuring and managing Veeam Plugin for Oracle RMAN, based on the experience of multiple installationsoneyes I reviewedones in different companies of various sizes. Including simple architectures, as well as complex architectures in high availability with Oracle RAC on different platforms x86, SPARC, Power. The objective of this post is to try to maintain a configuration standard and tasks to be carried out in order to maintain an ideal environment for Oracle data protection. In addition, this post includes a guide to update to the new version of backup files generated by the Plugin in its latest release.

Introduction

This post is based on the experience of operating multiple users in Latin America who have the Oracle database solution configured in high availability through Oracle RAC. Where different types of architectures of Veeam Backup & Replication with the use of Veeam Plugin for Oracle RMAN. The post seeks to generate a basic review of the requirements, configurationones and know the operation of Veeam Plugin for Oracle RMAN for Oracle RAC environments in order to achieve a correct operation and according to the configurations.ones necessary for its execution.

This document applies to the version of Veeam Backup & Replication v11 as also for Veeam Plugin for Oracle RMAN v11However, several of the recommendationsones described in this document apply to a previous version (v10).

Good practices Veeam Plugin for Oracle RMAN

One of the solutionsones of databases most used at the business level is Oracle, where we can find different types of installationones to achieve high availability, most of the time we find Oracle Real Application Cluster (RAC), where the most important high availability databases are stored and executed, if not, the core of the business of those who use Oracle.

Being such an important solution for companies, of course, Veeam developed a solution for integration between Oracle and Veeam, to be more specific, with Oracle Recovery Manager (RMAN), which allows database administrators to continue with their data protection protocols through RMAN, let us remember that RMAN is Oracle's native solution for performing backups of Oracle databases, but in this case, we will use Veeam Plugin for Oracle RMAN, to have the possibility of saving the backups in the repositories of Veeam Backup & Replication.

Recall that Veeam Plugin for Oracle technically, it is a library for Oracle RMAN of the SBT type, which allows us to provide the space of the repositories of Veeam Backup & Replication for Oracle RMAN in order to save backups made natively from RMAN.

One of the great advantages of Veeam Plugin for Oracle RMAN is that it allows us to perform the recovery of Oracle databases either via the command line or through Veeam Explorers, which makes disaster recovery much easier. In addition, there is also an integration with Oracle when they are virtual machines performing backup via image including support for Oracle Automatic Storage Management (ASM), which also includes automated backup of Archive Logs for granular recovery and of course including performing instant oracle database recoveryFor more information go to the following link:

https://helpcenter.veeam.com/docs/backup/vsphere/oracle_backup.html?ver=110

As we know Veeam Backup & Replication maintains different Veeam Explorers, such as Veeam explorer for Active Directory, Veeam explorer for Exchange, Veeam explorer for SharePoint, Veeam explorer for SQL Server, Veeam explorer for OneDrive (Veeam Office 365), Veeam explorer for Microsoft Teams (Veeam Office 365) and of course Veeam Explorer for Oracle. For more information go to the following link:

https://helpcenter.veeam.com/docs/backup/explorers/explorers_introduction.html?ver=110

For this reason, it is convenient to perform the integration between Veeam and Oracle via Plugin Veeam for Oracle, in this post, we will talk exclusively about some good practices for the use of Veeam Plugin for Oracle RMAN, according to direct experience in different companies.

Installation

The main good practice for installation is to use the architecture that applies to the operating system and Oracle where we are installing. Veeam Plugin for Oracle RMAN, always the recommendation is to install Veeam Plugin for Oracle RMAN on all Oracle RAC nodesremember that Veeam Backup & Replication has the following versionsonePlugin's:

• Veeam Plugin for Oracle RMAN about AIX ppc64
• Veeam Plugin for Oracle RMAN about Linux x86 and x64
• Veeam Plugin for Oracle RMAN about Solaris x86 and SPARC
• Veeam Plugin for Oracle RMAN about Windows

** https://helpcenter.veeam.com/docs/backup/plugins/rman_plugin.html?ver=110 **

In most cases we find Oracle RAC on Linux, therefore, we will talk about good practices associated with this type of environment, which does not mean that it does not apply to other versions.ones and/or operating systems.

According to the version that is installed, the first good practice is:

1. Installation with “root” user
2. Configuration with the user who owns the Oracle installation, usually the user “oracle”

And this is where it is very important that the user who owns the Oracle installation maintains the necessary permissions either at the level of files, folders and group memberships of the Oracle installation, including Oracle Grid, as indicated in:

https://helpcenter.veeam.com/docs/backup/plugins/rman_plugin_permissions.html?ver=110

There is even a post on the blog related to permissions or the error that appears in the configuration when they do not have the appropriate permissions:

https://24xsiempre.com/solucion-veeam-oracle-permission-denied/

Oracle Temp Tablespace

A very good practice always in Oracle databases is to keep space available in temporary tables or as it is well known Temp Tablespace for operations.oneIt is normal for the operation of the databases as well as for storing temporary data of the instances that are currently active.

What is the interaction between temporary tables with the RMAN fallback via Veeam Plugin for Oracle RMAN? in this temporary table Oracle RMAN uses the space to store statistical data of the sessionsonebackup data as well as resource utilization data to make informed decisions.ones of execution of backups in the servers that maintain free resources. For example, Oracle RMAN uses this temporary table to store metadata about the retrieved objects for their order.

As well, Veeam Plugin for Oracle RMAN, queries statistics of Oracle RMAN processes, that is why, that it must be validated that there is always space available in the temporary table so that unexpected errors do not occur or during execution time on the platform.

Configuration

Before any configuration in Oracle RAC, we must first prepare a dedicated repository for Oracle RMAN backups via Veeam Plugin for Oracle RMAN, where after creating the repository using REFS or XFS, either Simple or Scale-Out (SOBR), the user that will have permissions to use the repository in conjunction with the Plugin must be added. Veeam, for this we must add it in “Access Permissions”

Of course, when configuring our repositories to receive Oracle RMAN backups, we will need to maintain a correct configuration of concurrent tasks so that there are no bottlenecks or process queues to write the data to the repository, in fact, later we will review the requirements for Oracle RMAN channels and tasks Veeam Backup & Replication.By doing this we can move on to the Plugin configuration.

As we saw in the previous point of Installation, the configuration must be done with the user who owns the Oracle installation, generally the "oracle" user is used, where the command that is displayed at the end of the Plugin installation must be executed "OracleRMANConfigTool –wizard"

When executing the command, Veeam Plugin for Oracle RMAN examines and/or analyzes all the configuration of the existing instances in the Oracle installation, it will review the Oracle configuration files that maintain information of the instances and in turn the execution of some commands to validate the identification of the instances of databases, as well as query's or queries to the instances for the identification of ASM, validation of CONTROLFILE, SPFILE, etc. Some of the reviewed files and commands are:

• /etc/oratab
• /u01/app/oraInventory/ContentsXML/inventory.xml
• /u01/app/oracle/product/[version]/db_1/oraInst.loc
• srvctl status home
• srvctl config database -d [DB Name]
• srvctl status instance -d [DB Name] -n [Oracle Server]

Due to the above, the permissions and memberships of the Oracle installation groups used by the user who owns the application (generally “oracle”) are very important for detecting and configuring the environment for Veeam Plugin for Oracle RMAN.

Veeam Plugin for Oracle RMAN will ask us for certain information that we must enter, such as the server address of Veeam, the default port and the user credentials that we added in the “Access Permissions” configuration for access to the backup repository. Now we will visualize the repository that we have configured, we will select it with the number that precedes the name of the repository.

In this part it is possible to make the configuration towards multiple backup repositories of Veeam Backup & Replication, only repositories should be added by number containing a space.

And in the next question, “Enter the number of data streams (From 1 to 254) to run in parallel for each repository (RMAN DEVICE PARALLELISM value). Channel count per device [4]:” It is very important to know how many channels or streams we will use when performing the backup. For this we must consider the following:

• 1 CPU Core and 200 MB RAM for each channel used on the Oracle server or RAC node
• 1 CPU Core and 1 GB RAM for every 5 channels used for the repository Veeam Backup

Therefore, when we configure this option we must take into account the hardware requirements for the Oracle servers as well as for the repository. Veeam Backup & Replication, otherwise we could have some kind of bottleneck.

This point usually always brings up questions, such as, How does it work? We know that Oracle RMAN can use multiple channels (with a maximum of 255 channels and each channel can read 64 files in parallel) with the aim of improving performance and parallelism for carrying out the backup natively, but in this case, with Veeam Plugin for Oracle RMAN what you are looking for is that the configuration of the number of channels used by default in each backup is global, of course, always this type of configurationoneglobal s can be overridden in the backup job or script maintained by database administrators and/or Oracle.

It should be noted, as stated above, that Veeam Plugin for Oracle RMAN must be installed on each of the servers that componen Oracle RAC, since Oracle RMAN can use any available node with resources to perform its tasks and this is where we will review a very important Oracle table.

How many channels should be used, depending on the resources, with 4 channels is a good startOf course, the number of channels will always be limited by the number of resources that exist in the Oracle cluster. In general, users always use excellent hardware resources for this type of solution.oneyes It is always convenient that existing resources raise the number of channels to use to improve performance.

And since we are talking about resources and channels that RMAN will use, of course, it is necessary recommend a 10gb network, since the greater number of channels used is the greater the amount of bandwidth that Oracle RMAN will use and Veeam Plugin for Oracle RMAN for the transfer of backups to the repository of Veeam Backup & Replication.

And finally, if you want to assign channels manually, you should check the following link:

https://helpcenter.veeam.com/docs/backup/plugins/rman_allocation_backup.html?ver=110

After understanding and entering the channels to be used by Oracle RMAN through Veeam Plugin for Oracle RMAN, the solution asks us the following question, Do you want to use Veeam compression? (y/n). Here again it is a question of resources as well as a decision whether or not it is necessary to enable the compression of Veeam Backup & Replication, in the following link is the detail of the compression that it performs Veeam Backup & Replication and the resources that are necessary

https://helpcenter.veeam.com/docs/backup/vsphere/compression_deduplication.html?ver=110

But since we are talking about good practices according to user experience, the initial recommendation is Do not keep compressions enabledones from both Oracle and Veeam as it will demand resources and affect the entire performance of the backup processes.

And as a general recommendation initially don't use compression de Veeam unless there are resources left over to run compression on the Oracle data.

When selecting that we will not perform the compression, Veeam Plugin for Oracle RMAN will tell us which instances it detected in the operating system and, of course, the configuration that will be applied to Oracle RMAN globally.

Then there are the following 3 optionsones that tell us if we will apply the changes to Oracle RMAN, Export the configuration to apply it manually or, finally, not apply any changes.

Backup Operation and Execution

Generally, for the operation and execution of backups with Oracle RMAN, they always use scripts already developed by Database administrators with the desired configuration of retention as well as additional parameters according to business requirements.

At this point one of the recommendationsones most important for the protection of the instances is that the scripts of backup are as simple as possible and use the global Oracle RMAN configuration which applies to set up Veeam Plugin for Oracle RMAN, without the need to declare the SBT library or channels used in the backup scripts.

As well as it applies to the Archive Logs backup where it is recommended that the execution uses the RMAN global variables.

This does not mean that the configuration cannot be overridden from the script, only that, according to the configurationsones that we have reviewed, It has been the best option for a standardization of scripts and their maintenance.

Another very important issue, you should always finish the execution with the output of the script using the EXIT command, since in the event that Oracle RMAN could not release the session, it will be taken and the process will remain running until the RMAN process is manually canceled. In Veeam Backup & Replication, you will see the statistics window always running waiting for the end of the Oracle RMAN session.

Additional Files to Backup

Apart from the database files and archive logs that will be protected with Oracle RMAN through Veeam Plugin for Oracle RMAN, Oracle configuration files should always be backed up, typically the root folders ($ORACLE_HOME) of Oracle and Grid users.

In addition, it is necessary to back up the configuration files of Veeam Plugin for Oracle RMAN that are generated in the operating system.

To backup these folders it is possible to use Veeam Agent for Linux with file-level backup configuration without snapshots:

https://helpcenter.veeam.com/docs/agentforlinux/userguide/file_backup_snapshotless.html?ver=50

Generally the routes with all their recursive content to be backed up are:

• /etc/oratab
• /u01/
• / Opt /veeam

Of course if the installation paths are different, it is necessary to add them.

And any other paths that are necessary for database administrators and/or for disaster recovery.

Interoperability and Updateones

For users who already have Veeam Plugin for Oracle RMAN from version of Veeam Backup & Replication 9.5 where the updates have been madeones up to the latest version of Veeam Backup & Replication (V11 at the date of this document), it was always considered to validate the interoperability of the versionsoneyes, which are:

• Veeam Plug-in for Oracle RMAN 9.5 Update 4 supports integration with Veeam Backup & Replication version 9.5 Update 4, 9.5 Update 4a, and 9.5 Update 4b, 10.
• Veeam Plug-in for Oracle RMAN 10 (10.0.1.4854) supports integration only with Veeam Backup & Replication version 10.
• Veeam Plug-in for Oracle RMAN 10.0.1.4854 (10a Cumulative Patch 20201202) supports integration with Veeam Backup & Replication version 10, 11.
• Veeam Plug-in for Oracle RMAN 11 supports integration only with Veeam Backup & Replication version 11.

It is important to point out this interoperability since many times only the versions are updated.ones of Veeam Backup & Replication and no update Veeam Plugin for Oracle RMAN leading to unexpected errors. Therefore, it is always recommended to update all comps.onethat involve the implementation of Veeam Backup & Replication.

From version 11 of Veeam Plugin for Oracle RMAN uses a new format of backup files, instead of using only one metadata file for all backup files that was used in previous versions.oneAs before, from now on in version 11, there is a separate metadata file for all backup files. What allows to optimize the productivity of the operationsonebackup and recovery

To actualize Veeam Plugin for Oracle RMAN is very easy, depending on the operating system, proceed to download the new version of the installation package as explained in the following documentation

https://helpcenter.veeam.com/docs/backup/plugins/update_rman_plugin.html?ver=110

Since in v11 there are new backup files and metadata, it is necessary to update them, if backups made with versioneprevious s of Veeam Plugin for Oracle RMAN, for example, in the following image we see a backup with version 10 of Veeam Plugin for Oracle RMAN, where it tells us:

“Backup metadata is not up to date. Please upgrade the backup “

The message indicates that the metadata must be updated, to perform this recommended action, first of all, we must have updated Veeam Backup & Replication in the latest V11 and of course Veeam Plugin for Oracle RMAN in the latest V11 and then you must enter the console Veeam Backup & Replication, then in the “Backups” menu, select “Disk” where we will see the Oracle RMAN backup and right click on it:

Here we will see a new “Upgrade” function that will always appear in backups with versionones prior to v11, which will allow us to update our backup files and metadata with Veeam Plugin for Oracle RMAN versionones previous. Clicking on “Upgrade” Veeam Backup & Replication It will indicate that the disabled backup tasks are needed to perform the update action.

We only have to enter the task management of Veeam Backup & Replication clicking “Jobs” and then “Backup” to then identify the backup job of Veeam Plugin for Oracle RMAN and proceed to disable it

By keeping the backup task disabled, we will return to "Backups" then "Disk" and select the Oracle RMAN backup again to perform the "Upgrade" where the message indicated

Checking if we have all the componebefore updated to the latest version, that is Veeam Backup & Replication v11 (in its last update), as well as Veeam Plugin for Oracle RMAN in its latest version, selecting "Yes" will show us the status of the operation

The duration of this operation will always depend on the number of Oracle backup files, the type of repository and, of course, the workload on the file system. If the files are hosted on some Deduplication device, it may take more time depending on the operations.ones of the same device that must rehydrate the data so that Veeam Backup & Replication update the files and metadata.

Configuration Files and Logs

In certain cases it is always advisable to know the location of the different configuration files, in case it is necessary to edit manually, support indicates any change and of course know the location of the log files in case of making a review for a wrong solution behavior or grab the files to update a support case.

The default location of the configuration files Veeam Plugin for Oracle RMAN

• Linux, Solaris, AIX in /opt/veeam/VeeamPluginforOracleRMAN
• Windows C:\Program Files\Veeam\VeeamPluginforOracleRMAN

These configuration files must be edited according to the technical support guidelines of Veeam.

And for the occasionsoneIf it is necessary to review log files or send logs to support the path of these files

• Linux, Solaris, AIX /tmp/veeam_plugin_logs/
• Windows %ProgramData%\Veeam\Backup\RmanPluginLogs

Or use the KB

https://www.veeam.com/kb2871

considerationones General

A general recommendation is that the operating systems involved in the protection of Oracle databases must always be updated, as long as the operation allows it, in the case of the roles of Veeam Backup & Replication, specifically the repositories, in addition to having the updatesones of the drivers of network devices, since in certain when updating either the operating system and also the drivers of the network interfaces, the data backup improved considerably.

On the other hand, it is always recommended to use that all the services, servers and systems involved have an addressones DNS-FQDN so that the configuration is as complete as possible.

That's all, try to make it as complete and detailed as possible, as always, additional ideas or comments are welcome.