Veeam Plug-ins for

Enterprise Applications

Version 11
User Guide
April, 2021
© 2021 Veeam Software.

All rights reserved. All trademarks are the property of their respective owners.

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language in any form by any means, without written permission from Veeam Software
(Veeam). The information contained in this document represents the current view of Veeam on the issue
discussed as of the date of publication and is subject to change without notice. Veeam shall not be liable for
technical or editorial errors or omissions contained herein. Veeam makes no warranties, express or implied, in
this document. Veeam may have patents, patent applications, trademark, copyright, or other intellectual
property rights covering the subject matter of this document. All other trademarks mentioned herein are the
property of their respective owners. Except as expressly provided in any written license agreement from Veeam,
the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other
intellectual property.

NOTE:
Read the End User Software License Agreement before using the accompanying software programs. Using
any part of the software indicates that you accept the terms of the End User Software License Agreement.

2 | Veeam Plug-ins for Enterprise Applications | User Guide

Contents
CONTACTING VEEAM SOFTWARE ................................................................................................................... 6
ABOUT THIS DOCUMENT ............................................................................................................................... 7
VEEAM PLUG-INS OVERVIEW ......................................................................................................................... 8
VEEAM PLUG-IN FOR SAP HANA .................................................................................................................... 9
How Veeam Plug-in for SAP HANA Works ................................................................................................ 10
Planning and Preparation ..........................................................................................................................11
System Requirements..................................................................................................................... 12
Required Permissions ..................................................................................................................... 14
Used Ports ..................................................................................................................................... 15
Licensing ........................................................................................................................................ 18
Environment Planning ................................................................................................................... 20
Veeam Backup Repositories........................................................................................................... 26
Access and Encryption Settings on Repositories ............................................................................ 29
Deployment and Configuration ................................................................................................................ 31
Installing Plug-in for SAP HANA ..................................................................................................... 32
Configuring Plug-in for SAP HANA ................................................................................................. 33
Updating Plug-in for SAP HANA ..................................................................................................... 37
Uninstalling Plug-in for SAP HANA ................................................................................................ 38
Automating Configuration of Plug-in for SAP HANA ...................................................................... 39
Importing Backups ........................................................................................................................ 40
Uprgading Backup Files ................................................................................................................. 42
Database Protection ................................................................................................................................ 44
Database Backup (HDBSQL Scripts) ............................................................................................... 45
Database Backup (SAP HANA Studio) .............................................................................................47
Database Backup (SAP HANA Cockpit) ........................................................................................... 50
Backup Job in Veeam Backup & Replication Console ....................................................................... 52
Database Recovery .................................................................................................................................. 54
Restoring Databases (HDBSQL Commands) .................................................................................... 55
Restoring Databases (SAP HANA Studio) ....................................................................................... 56
Restoring SYSTEMDB (SAP HANA Cockpit) .................................................................................... 63
Recovering Tenant Databases with SAP HANA Cockpit .................................................................. 68
Recovering Databases to Other Servers (System Copy) ................................................................... 72
Restore from Backup Copy .............................................................................................................74
Retention of SAP HANA Backups .............................................................................................................. 75
Deleting Backups Using SAP HANA Tools .......................................................................................76
Deleting Backups Manually ............................................................................................................ 77

3 | Veeam Plug-ins for Enterprise Applications | User Guide

 Configuring Force Deletion of Backups .......................................................................................... 78
Removing Backups from Configuration ...........................................................................................79
Backup Copy for SAP HANA Backups ....................................................................................................... 80
Creating Backup Copy Job .............................................................................................................. 81
Converting Backup Copy to Backup ............................................................................................... 92
VEEAM PLUG-IN FOR ORACLE RMAN............................................................................................................ 93
How Veeam Plug-in for Oracle RMAN Works ........................................................................................... 94
Planning and Preparation ........................................................................................................................ 96
System Requirements.....................................................................................................................97
Required Permissions .................................................................................................................... 99
Used Ports ................................................................................................................................... 101
Licensing ......................................................................................................................................104
Oracle Environment Planning ...................................................................................................... 106
Veeam Environment Planning ..................................................................................................... 109
Veeam Backup Repositories........................................................................................................... 111
Access and Encryption Settings on Repositories ........................................................................... 114
Deployment and Configuration .............................................................................................................. 116
Installing Veeam Plug-in for Oracle RMAN .................................................................................... 117
Configuring Veeam Plug-in for Oracle RMAN................................................................................ 123
Updating Veeam Plug-in for Oracle RMAN ................................................................................... 132
Uninstalling Veeam Plug-in for Oracle RMAN ............................................................................... 134
Importing/Exporting Plug-in Settings .......................................................................................... 135
Importing Backups ....................................................................................................................... 136
Upgrading Backup Files ................................................................................................................ 138
Database Protection ...............................................................................................................................140
Oracle RMAN Full Backup ............................................................................................................. 141
Oracle RMAN Channel Allocation.................................................................................................. 142
Backup Job in Veeam Backup & Replication .................................................................................. 143
Database Recovery ................................................................................................................................. 146
Restore to Original Server ............................................................................................................ 147
Restore to Another Server ............................................................................................................ 148
Restore from Backup Copy ........................................................................................................... 150
Restore with Veeam Explorer for Oracle ....................................................................................... 152
Restore of Control File from Autobackup ..................................................................................... 153
Retention of RMAN Backups................................................................................................................... 155
Configuring Retention Policy ........................................................................................................ 156
Configuring Redo Log Retention .................................................................................................. 157
Configuring Force Deletion of Backups ......................................................................................... 158
Deleting Backups Manually .......................................................................................................... 159

4 | Veeam Plug-ins for Enterprise Applications | User Guide

 Removing Backups from Configuration ........................................................................................ 160
Backup Copy for Oracle RMAN Backups .................................................................................................. 161
Creating Backup Copy Job ............................................................................................................ 162
Converting Backup Copy to Backup .............................................................................................. 173
VEEAM PLUG-IN FOR SAP ON ORACLE ........................................................................................................ 175
How Veeam Plug-in for SAP on Oracle Works ......................................................................................... 176
Planning and Preparation ....................................................................................................................... 178
System Requirements................................................................................................................... 179
Required Permissions .................................................................................................................. 180
Used Ports ................................................................................................................................... 181
Licensing ...................................................................................................................................... 184
Environment Planning .................................................................................................................. 186
Backup Repositories Planning....................................................................................................... 188
Deployment and Configuration .............................................................................................................. 192
Installing Veeam Plug-in for SAP on Oracle .................................................................................. 193
Configuring Plug-in for SAP on Oracle .......................................................................................... 194
Configuring Parallelism for Redo Logs .......................................................................................... 198
Importing Backups ....................................................................................................................... 199
Uninstalling Plug-in for SAP on Oracle ......................................................................................... 201
Database Protection .............................................................................................................................. 202
SAP on Oracle Full Backup ........................................................................................................... 203
SAP on Oracle Incremental Backup .............................................................................................. 205
SAP on Oracle Backup (RMAN_UTIL) ............................................................................................ 206
SAP on Oracle Redo Logs Backup ................................................................................................ 209
Backup Job in Veeam Backup & Replication Console ..................................................................... 210
Database Recovery ................................................................................................................................. 212
Oracle Databases Restore ............................................................................................................. 213
Redo Logs Restore ....................................................................................................................... 214
Database Restore to Another Server (System Copy) ..................................................................... 215
Restore from Backup Copy ........................................................................................................... 217
Retention of SAP on Oracle Backups....................................................................................................... 218
Configuring Retention Policy for Backups ..................................................................................... 219
Deleting Backups Manually ......................................................................................................... 220
Removing Backups from Configuration ......................................................................................... 221
Backup Copy for SAP on Oracle Backups ................................................................................................. 222
Creating Backup Copy Job ............................................................................................................ 223
Converting Backup Copy to Backup ..............................................................................................234
Logs and Support ................................................................................................................................... 235

5 | Veeam Plug-ins for Enterprise Applications | User Guide

Contacting Veeam Software
At Veeam Software we value feedback from our customers. It is important not only to help you quickly with your
technical issues, but it is our mission to listen to your input and build products that incorporate your
suggestions.

Customer Support
Should you have a technical concern, suggestion or question, visit the Veeam Customer Support Portal to open a
case, search our knowledge base, reference documentation, manage your license or obtain the latest product
release.

Company Contacts
For the most up-to-date information about company contacts and office locations, visit the Veeam Contacts
Webpage.

Online Support
If you have any questions about Veeam products, you can use the following resources:

• Full documentation set: www.veeam.com/documentation-guides-datasheets.html

• Veeam R&D Forums at forums.veeam.com

6 | Veeam Plug-ins for Enterprise Applications | User Guide

About This Document
The document describes how to deploy, configure and use Veeam Plug-in for SAP HANA, Veeam Plug-in for
Oracle RMAN and Veeam Plug-in for SAP on Oracle.

Intended Audience
This document is intended for DBA's, backup administrators and other IT professionals who use Veeam to back
up and restore SAP HANA and Oracle databases.

7 | Veeam Plug-ins for Enterprise Applications | User Guide

Veeam Plug-ins Overview
Veeam Plug-ins for Enterprise Applications extend Veeam Backup & Replication functionality and allow you to
create transactionally-consistent backups of SAP HANA and Oracle databases.

• Veeam Plug-in for SAP HANA — an SAP-certified backup and recovery solution that allows you to back up
and restore SAP HANA databases.

• Veeam Plug-in for Oracle RMAN — an Oracle-certified backup and recovery solution that allows you to
back up and restore Oracle databases.

• Veeam Plug-in for SAP on Oracle — an SAP-certified backup and recovery solution that allows you to back
up and restore Oracle databases to which an SAP application is connected.

IMPORTANT

Veeam Plug-ins store database and log backups in repositories added to the Veeam Backup & Replication
infrastructure. Thus, to use Veeam Plug-ins, you must have a Veeam Backup & Replication server deployed
in your infrastructure. To learn how to deploy Veeam Backup & Replication, see the Deployment section of
the Veeam Backup & Replication User Guide.

8 | Veeam Plug-ins for Enterprise Applications | User Guide

Veeam Plug-in for SAP HANA
Veeam Plug-in for SAP HANA is an SAP-certified backup tool that integrates with backint and allows you to
store transactionally-consistent SAP HANA database backups and logs in repositories connected to Veeam
Backup & Replication.

NOTE

If you want to protect the SAP HANA server itself, you can use the image-level and file-level backup
functionality of Veeam Backup & Replication or Veeam Agent for Linux.

Image- and file-level backups of SAP HANA servers do not guarantee transaction-consistency of the
databases.

9 | Veeam Plug-ins for Enterprise Applications | User Guide

How Veeam Plug-in for SAP HANA Works
Veeam Plug-in acts as an agent between SAP HANA server and Veeam backup repositories. Veeam Plug-in
compresses, deduplicates database backups and transfers them to a backup repository connected to the Veeam
Backup & Replication infrastructure. After you install and configure Veeam Plug-in on the SAP HANA server, you
can perform all backup and restore operations with HDBSQL scripts and with native SAP HANA tools, such as
SAP HANA Studio and SAP HANA Cockpit.

Additionally, if you enable log backups (Backint), SAP HANA automatically backs up logs according to log
backup interval configured in SAP HANA settings or depending on whether the log file is full or closed.

When Veeam Plug-in is configured, SAP Backint performs a database backup in the following way:

1. When you start a database backup, the SAP HANA Backint starts Veeam Plug-in services on the SAP HANA
server.

2. Veeam Plug-in connects to the Veeam Backup & Replication server and creates a backup job object (if it
has not been created before). In the Veeam Backup & Replication console, Veeam backup administrators
can use this backup job object to monitor SAP HANA backups.

3. Veeam Plug-in starts Veeam Data Mover services on the SAP HANA server and on a backup repository.
According to specified number of parallel backint channels, Veeam Data Movers create channels to
transfer backup data.

4. Veeam Data Movers transport backup data to the backup repository.

10 | Veeam Plug-ins for Enterprise Applications | User Guide

Planning and Preparation
Before you start to use Veeam Plug-in for SAP HANA, read the environment planning recommendations and
make sure that your environment meets system requirements.

• System Requirements

• Required Permissions

• Used Ports

• Licensing

• Environment Planning

• Veeam Backup Repositories

• Granting Permissions on Veeam Backup Repositories

11 | Veeam Plug-ins for Enterprise Applications | User Guide

System Requirements
Before you start using Veeam Plug-in for SAP HANA, consider the following requirements.

Supported OSes
Veeam Plug-in for SAP HANA is supported for the following OSes.

• SLES for SAP Applications 15 (x86_64):

o 15 SP2 (HANA 1.0 SPS12 revision 122.31 and newer)

o 15 SP1 (HANA 1.0 SPS12 revision 122.27 and newer)

o 15 (GA) (HANA 1.0 SPS12 revision 122.21 and newer)

• SLES for SAP Applications 12 (x86_64):

o 12 SP5 (HANA 1.0 SPS12 revision 122.29 and newer)

o 12 SP4 (HANA 1.0 SPS12 revision 122.22 and newer)

o 12 SP3 (HANA 1.0 SPS12 revision 122.15 and newer)

o 12 SP2 (HANA 1.0 SPS12)

o 12 SP1 (HANA 1.0 SPS12)

o 12 (GA) (HANA 1.0 SPS10 and newer)

• RHEL for SAP Solutions 8 (x86_64):

o 8.2 (HANA 2.0 SPS04 revision 48.02 and HANA 2.0 SPS05 revision 52 and newer)

o 8.1 (HANA 2.0 SPS04 revision 45 and newer)

o 8.0 (HANA 2.0 SPS04 only, starting with revision 40)

• RHEL for SAP Solutions 7 (x86_64):

o 7.9 (HANA 2.0 SPS05 revision revision 54 and newer)

o 7.7 (HANA 2.0 SPS04 revision 48 and newer)

o 7.6 (HANA 2.0 SPS04 revision 36 and newer)

o 7.5 (HANA 2.0 SPS03 only, starting with revision 32)

o 7.4 (HANA 2.0 SPS02 revision 23 and newer, up to HANA 2.0 SPS04)

o 7.3 (HANA 2.0 SPS02 revision 21 and newer, up to HANA 2.0 SPS03)

o 7.2 (up to HANA 2.0 SPS03)

SAP HANA
Veeam Plug-in for SAP HANA supports the following versions of SAP HANA:

• SAP HANA 2.0 SPS 02/SPS 03/SPS 04/SPS 05 (only with Backint version 1.0). Express Edition is not
supported.

• SAP HANA 1.0 SPS12 and newer.

12 | Veeam Plug-ins for Enterprise Applications | User Guide

Veeam Backup & Replication
Mind the following compatibility of Veeam Backup & Replication and Veeam Plug-in versions:

• Veeam Plug-in for SAP HANA 11 supports integration only with Veeam Backup & Replication version 11.

• Veeam Plug-in for SAP HANA 10.0.1.4854 (10a Cumulative Patch 20201202) supports integration with
Veeam Backup & Replication version 10, 11.

• Veeam Plug-in for SAP HANA 10 (earlier than 10.0.1.4854) supports integration only with Veeam Backup
& Replication version 10.

• Veeam Plug-in for SAP HANA 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.

Note that if you want to use the latest functionality, you must update both Veeam Backup & Replication and
Veeam Plug-in to the latest version.

13 | Veeam Plug-ins for Enterprise Applications | User Guide

Required Permissions
User Rights on the SAP HANA Server
The account used for installing and updating Veeam Plug-in must have root privileges.

Veeam Backup Server User

• The account specified in the Veeam Plug-in configuration settings must be able to authenticate against
the Veeam Backup & Replication server. For details, see Configuring Veeam Plug-in for SAP HANA.

• The account specified in the Veeam Plug-in configuration settings must be granted access rights on the
Veeam backup repository where you want to store backups.
To learn how to grant permissions on Veeam repositories, see Granting Permissions on Repositories.

• You can work with backups created by Veeam Plug-in only with the account used for creating the backups.
If you want to use another account, see required permissions in Configuring Veeam Plug-in for SAP HANA.

14 | Veeam Plug-ins for Enterprise Applications | User Guide

Used Ports
To enable proper work of Veeam Plug-ins, make sure that the following ports are open.

SAP HANA Server

The following table describes network ports that must be opened to ensure proper communication of the SAP
HANA server and backup infrastructure components.

From To Protocol Port Notes

Default port used for communication with

Veeam the Veeam Backup & Replication server.
Backup & Note that data between Veeam Plug-ins
TCP 10006
SAP HANA Replication and backup repositories is transferred
server server directly, bypassing the Veeam Backup &
where Replication server.
Veeam
Plug-in is
installed Backup
Default range of ports used as data
repository
2500 to transmission channels. For every TCP
server or TCP
3300** connection that a backup process uses,
gateway
one port from this range is assigned.
server*

* For NFS share, SMB share repositories, and Dell EMC Data Domain, HPE StoreOnce deduplication storage appliances,
Veeam Backup & Replication uses an auxiliary backup infrastructure component — gateway server. For details, see the
Gateway Server section of the Veeam Backup & Replication User Guide.
** This range of ports applies to newly added backup infrastructure components. If you upgrade to Veeam Backup &
Replication 10.0 from earlier versions of the product, the range of ports from 2500 to 5000 applies to the already added
components.

Backup Repositories and Gateway Servers

Depending on the type of backup repositories that you use for Veeam Plug-in backups, the following ports must
be open to allow communication between backup infrastructure components.

From To Protocol Port Notes

Direct Attached Storage

Linux server
Veeam used as a
Port used as a control channel from the
Backup & backup
TCP 22 Veeam Plug-in server to the target Linux
Replication repository or
host.
server gateway
server

15 | Veeam Plug-ins for Enterprise Applications | User Guide

 From To Protocol Port Notes

Microsoft Ports used as a management channel from

TCP 135, 137 to the Veeam Plug-in server to the
Windows
server used UDP 139, 445 Repository/Gateway server. Also, the ports
as a backup are used to deploy Veeam components.
repository or
gateway Default ports used by the Veeam Installer
server TCP 6160, 6162
Service and Veeam Data Mover Service

Network Attached Storage

Gateway Default port used by the SMB transport

TCP 445
server protocol.

(specified in
the SMB SMB server SMB/Netbios name resolution for the SMB
share TCP 135, 137 to protocol (needed in some cases). For
repository UDP 139 details, see the Used Ports section of the
settings) Veeam Backup & Replication User Guide.

Gateway
server

(specified in TCP Standard NFS ports used as a transmission

the NFS NFS server 111, 2049 channel from the gateway server to the
UDP target NFS share.
share
repository
settings)

Dell EMC Data Domain

Port used to assign a random port for the

mountd service used by NFS and
TCP 111
DDBOOST. Mountd service port can be
statically assigned.
Veeam Dell EMC
Backup & Data Domain Main port used by NFS. To change the
Replication
port, you can use the ‘nfs set server-
server For more TCP 2049
port’ command. Note that the command
or information,
see Dell EMC requires SE mode.
Gateway
server Documents.
Main port used by NFS MOUNTD. To
change the port, you can use the 'nfs
TCP 2052
set mountd-port' command. Note
that the command requires SE mode.

HPE StoreOnce

16 | Veeam Plug-ins for Enterprise Applications | User Guide

 From To Protocol Port Notes

Veeam Default command port used for

9387
Backup & communication with HPE StoreOnce.
Replication
HPE
server TCP
StoreOnce
or Default data port used for communication
Gateway 9388
with HPE StoreOnce.
server

ExaGrid

Veeam
Backup & Default command port used for
ExaGrid TCP 22
Replication communication with ExaGrid.
server

Quantum DXi

Veeam
Backup & Default command port used for
Quantum DXi TCP 22
Replication communication with Quantum DXi.
server

For detailed list of ports used by Veeam Backup & Replication server and backup repositories, see the Used Ports
section of the Veeam Backup & Replication User Guide.

17 | Veeam Plug-ins for Enterprise Applications | User Guide

Licensing
To use the Veeam Plug-in functionality, you must have a valid Veeam Backup & Replication license. Licenses are
installed and managed on the Veeam Backup & Replication server that is connected to the Veeam Plug-in server.
If the license is not valid or out of resources, Veeam Plug-in backup jobs fail.

This guide provides information only on specifics of Veeam licenses for Veeam Plug-ins. For terminology and
general information about Veeam Licensing, see Veeam Licensing Policy.

In this section:

• Licensed Objects

• Supported License Types and Packages

• Obtaining and Managing Licenses

Licensed Objects
A machine where SAP HANA is deployed is assumed protected if it has been processed by a Veeam Plug-in
backup job in the last 31 days.

If you are using any instance-based (Veeam Universal Licensing) license on your Veeam Backup & Replication,
you don't need to install any additional licenses.

A machine protected by both Veeam Plug-in and Veeam Backup & Replication will consume a license only once.
For example, you have an SAP HANA server that you back up using Veeam Plug-in. You can also back up this
server using image-level backup functionality of Veeam Backup & Replication. In this case, only one license will
be consumed.

NOTE

[For Perpetual per-socket licenses] If you are using a legacy perpetual per-socket license, a license is
required for each hypervisor CPU socket occupied by protected SAP HANA servers.

A socket is consumed from the license only if the hypervisor where protected servers reside is added to the
Veeam Backup & Replication infrastructure. If the hypervisor is not added to the Veeam Backup &
Replication infrastructure, an instance unit will be consumed from the license. To learn how to add a
hypervisor to the Veeam Backup & Replication infrastructure, see the Virtualization Servers and Hosts
section of the Veeam Backup & Replication User Guide.

IMPORTANT

If you have an SAP HANA Scale-Out Cluster, each node will consume a separate license unit. The license
units will be consumed for all cluster nodes, even if Veeam Plug-in is installed on one of the nodes.

18 | Veeam Plug-ins for Enterprise Applications | User Guide

Supported License Types and Packages
You can use Veeam Plug-ins with the following license types and packages. Note that this guide contains
information on peculiarities of Veeam license packages only for Veeam Plug-ins. For the full list of license
packages, see Pricing and Packaging.

• For Veeam Universal Licensing:

You can use Veeam Plug-ins with all license packages (Veeam Backup Essentials, Veeam Backup &
Replication, Veeam Availability Suite).
Note that if you use the Rental license type, functionality of Veeam Plug-ins is supported only for the
Enterprise Plus edition of Veeam Backup & Replication.

• For Perpetual Socket license:

Functionality of Veeam Plug-ins is supported only for the Enterprise Plus edition of Veeam Backup &
Replication.

Obtaining and Managing Licenses

To learn how to install a license and monitor licensed objects, see the Licensing section in the Veeam Backup &
Replication User Guide.

19 | Veeam Plug-ins for Enterprise Applications | User Guide

Environment Planning
Integration of SAP HANA and Veeam Plug-in requires additional environment planning. When you deploy the
plug-in, keep in mind the following requirements and limitations.

Compression
Veeam Plug-in uses built-in compression functionality of Veeam Backup & Replication. If you want to disable
the compression, do the following:

1. Open the /opt/veeam/VeeamPluginforSAPHANA/veeam_config.xml file with a text editor.

2. In the veeam_config.xml file, find the <AgentParams /> line and add the following parameter:

<AgentParams compression="NoCompression" />

Scheduling
• Veeam Plug-in forwards the backups created by SAP HANA integrated backup application to a Veeam
backup repository. You can schedule backup operations with all SAP HANA relevant scheduling options
like SAP HANA Cockpit (HANA Cockpit 2.0 SPS 06 or later version), SAP DB13 (NW 7.02 SP17 or later
version) or external schedulers like cron, UC4, TWS and others.
For instructions on how to configure external schedulers, see the Veeam Plug-in for SAP HANA Best
Practices.

• You can schedule and run existing SAP HANA backup scripts within an image-level or file-level backup job
of Veeam Backup & Replication or Veeam Agent for Linux. For details, see the Pre-Freeze and Post-Thaw
Scripts section in the Veeam Backup & Replication User Guide.

NOTE

For SAP Management Software, make sure SAP HANA 2.0 systems are configured in the Multi-Container
mode. Otherwise, backups will fail with the following error: [110091] Invalid path selection for
data backup using backint.

Backup File Naming

Veeam Plug-in backup files are stored in the .VAB format. Also, each backup file has a metadata file (.VASM).
This extension helps to identify backup files on the backup repository and enable the import and other related
features of Veeam Backup & Replication.

Veeam Plug-in backup file names match the external backup ID's (EBID) created by SAP HANA.

Veeam Backup Job Name

Veeam backup jobs visible in the Veeam Backup & Replication console are created automatically at first backup
run.

Standalone SAP HANA Server (Scale-Up): The backup job object name in Veeam Backup & Replication is created
automatically based on the names of the HANA server and selected repository.

20 | Veeam Plug-ins for Enterprise Applications | User Guide

Scale-Out SAP HANA Cluster: When you run the Veeam Plug-in configuration wizard for the first time in one of
the SAP HANA cluster members, the wizard asks for the cluster name. The cluster name will be used in the
backup job object name together with the repository name.

Veeam User Management

Veeam Plug-in for SAP HANA uses the Windows authentication methods of the Veeam Backup & Replication
server to establish a connection to this server and to the backup target. It is recommended to create one specific
user for each Veeam Plug-in server or for each scale-out cluster.

If this user will be later changed manually, the new user must have at least the Veeam Backup Operator and
Veeam Restore Operator rights within the Veeam Backup & Replication user management. To learn how to
assign Veeam Backup & Replication roles, see the Roles and Users section of the Veeam Backup & Replication
Guide.

SAP HANA Backup Channels and Veeam Repository Task Slots

By default, SAP HANA uses one channel per data backup operation. You can configure SAP HANA to use
additional channels. When multiple channels are used, SAP HANA distributes the data equally across available
channels.

To control the number of parallel channels used for each SAP HANA Backint instance, you can edit the
parallel_data_backup_backint_channels parameter in the SAP HANA global.ini file. For
instructions, see the Multistreaming Data Backups with Third-Party Backup Tools section of the SAP HANA
Administration Guide

NOTE

The number of multistreaming channels applies to all data backup services larger than 128GB. Data backup
services smaller than 128GB use only one channel.

Basically, the more channels used in parallel, the faster is the data flow between SAP HANA and the source
Veeam Transport Agent. However, the more channels used in parallel, the more resources are used on the SAP
HANA server, network, Veeam backup repository, backup source and target disk systems. You should find the
right mix between performance and resource allocation for your specific business need.

The following hardware resources are recommended based on tests on Skylake processors:

• SAP HANA server: 1 CPU core and 200 MB of RAM per currently used channel.

• Backup repository server: 1 CPU core and 1 GB of RAM per 5 currently used channels.
These resources are recommended only if you use a dedicated backup repository for Veeam Plug-in
backups. If you use the same backup repository for Veeam Plug-in backups and VM backups created by
Veeam Backup & Replication or Veeam Agents, consider adding the mentioned above hardware resources
based on usual load on your backup repository. For details on hardware requirements for a backup
repository, see the System Requirements section of the Veeam Backup & Replication User Guide.
We recommend to contact your Veeam system engineer to optimize the channel settings and resource
allocation. Also, mind the following recommendations:

o It is not recommended to use more than 64 channels in parallel as the overhead will reduce individual
channel performance. Set the max_recovery_backint_channels setting in global.ini to 64 or
below depending on available hardware resources.

o It is recommended to use a separate backup repository for Veeam Plug-in backups.

21 | Veeam Plug-ins for Enterprise Applications | User Guide

 o If you want to improve backup performance, the SAP HANA buffer must be increased for additional
used channels. For details, consult with your SAP HANA database administrator.

o SAP HANA can back up individual databases and tenants in parallel. To optimize resources, you can
back up databases sequentially.

o If there are not enough available repository task slots, SAP HANA waits till repository task slots
become available.

o During restore, the order of repository task slots is ignored, and channels are used as requested by
SAP HANA.

• Veeam Backup & Replication server: during manual metadata operations such as import of backup files,
the Veeam Backup & Replication server needs additional 15 GB of RAM per 1 million files located in the
same backup job folder.

You can use the following examples as reference:

• Example 1: Backing up all databases in parallel

In this example, there is a system with 2 tenant databases, each database has 4 services. The databases
are backed up in parallel. The SAP HANA channel setting is 6. The following maximum repository task
slots and SAP channels are used:

o Up to 4 task slots/channels are used by SYSTEMDB and its 4 services (all below 128 GB)

o Up to 6 task slots/channels are used for the index service of the tenant database 1 (the database is
bigger than 128 GB)

o Up to 3 task slots/channels are used for the rest of the 3 remaining services of the tenant database 1
(all below 128 GB)

o Up to 6 task slots/channels are used for the index service of the tenant database 2 (the database is
bigger than 128 GB)

o Up to 3 task slots/channels are used for the rest of the 3 remaining services of the tenant database 2
(all below 128 GB)

o If the log backups are below 128GB, you must reserve at least 3 channels for the log backup of
SYSTEMDB, tenant database 1, and tenant database 2. These log backups are started automatically on
their own schedule or when the maximum file size of the log file is reached.
In total, for backup processes of all databases started in parallel you need up to 27 available task slots.

• Example 2: Backup of all databases sequentially

In this example, there is system with 2 tenant databases, each database has 4 services. The databases are
backed up sequentially. The SAP HANA channel setting is 6. The following maximum repository task slots
and SAP channels are used:

o Up to 6 task slots/channels are used for the index service of a tenant database (the database is bigger
than 128 GB).

o Up to 3 task slots/channels are used for the rest of the 3 remaining services of the same tenant
database (all below 128 GB).

o If the log backups are below 128GB, you must reserve at least 3 channels for the log backup of
SYSTEMDB, tenant database 1, and tenant database 2. These log backups are started automatically on
their own schedule or when the maximum file size of the log file is reached. Assuming that the log file
backups are below 128 GB and do not use additional channels.
In total, for backup processes of sequential started database backups, 12 task slots must be available.

22 | Veeam Plug-ins for Enterprise Applications | User Guide

SAP HANA Encryption
Veeam Plug-in supports SAP HANA integrated encryption. The encryption processes are performed on the SAP
HANA side. Veeam Plug-in is not involved in encryption processing.

Plan the protection of the encryption environment carefully. In case the encryption keys are lost, Veeam Plug-in
can only provide an access to the encrypted backup file. You will have to decrypt data in SAP HANA. For details,
see the Managing Data Encryption section of the SAP HANA Administration Guide.

SAP HANA Catalog Backup with Backint

To back up the SAP HANA catalog using Backint, change the settings of the catalog_backup_using_backint
parameter in the backup section of the global.ini.

SAP HANA Backint Parameter File

Veeam Plug-in does not use the Backint parameter file. Leave these fields empty when asked for.

SAP HANA Scale-Out Cluster

Veeam Plug-in supports SAP HANA scale-out clusters with the following limitations:

• Due to design of SAP HANA databases, the same Veeam Plug-in configuration must be set on all scale-out
cluster members, including stand-by nodes.

o On all cluster nodes, Veeam Plug-in must be configured to transfer backups to the same repository.

o Each cluster node must use the same credentials to connect to Veeam servers.

• All backup tasks across the SAP HANA scale-out cluster are performed in parallel.

SAP HANA System Replication Failover

SAP HANA does not allow you to back up from replicas. You can back up these databases only after a failover.
To prepare the replication target system for backups after the failover, you can configure Veeam Plug-in as
usual for a new scale-up or scale-out system. The Veeam backup job object will be created at first backup run
and reflect the hostname of each system.

IMPORTANT

You must perform full database backup at least once after each failover or failback, so that SAP HANA
starts to create automatic log backups.

23 | Veeam Plug-ins for Enterprise Applications | User Guide

After the failover, if you want to restore backups created before the failover, you must configure the plug-in to
be able to access the backup files from the original source system:

1. Go to /opt/veeam/VeeamPluginforSAPHANA and run the Veeam Plug-in configuration tool with the
following parameter.

VM2ADM:/opt/veeam/VeeamPluginforSAPHANA> SapBackintConfigTool --set-restor

e-server

2. Select the original source server.

Select source SAP HANA plug-in server to be used for system copy restore:
1. SAP-VM1
2. SAP-VM02
Enter server number: 1

3. Specify the backup repository where the required source server backup is stored.

Available backup repositories:

1. serv10_repo
Enter repository number: 1

4. Perform system copy restore. For instructions, see Recovering Databases to Other Servers.

5. Later, if you want to restore from the new backup chain created from the system replication server, you
must run the command again and select the system replication server as a source for restore.

Hosting Environments
By default, Veeam Plug-in uses a hostname to create the Veeam Backup & Replication job object and a folder
where the backups will be stored. If server names match, you can set the following entry in the Veeam
configuration XML file (/opt/veeam/VeeamPluginforSAPHANA/veeam_config.xml) to be able to
distinguish servers:

<PluginParameters customServerName="hostname.domain.tld" />

Example:

If your servers in multiple environments have the name sap1 and the domains for the 2 environments are
customer1.local and customer2.local you have to set the following entries:

<PluginParameters customServerName="sap1.customer1.local" />

<PluginParameters customServerName="sap1.customer2.local" />

24 | Veeam Plug-ins for Enterprise Applications | User Guide

Additional Files to Back Up
SAP HANA INI Files

SAP HANA does not back up the SAP configuration stored in INI files. Contact your SAP HANA database
administrator to discuss the backup of the following files:

• /usr/sap/<SID>/SYS/global/hdb/custom/config

• /usr/sap/<SID>/<INSTANCE>/<FQDN>

• /usr/sap/<SID>/SYS/global/hdb/custom/config

Also, to backup SAP HANA configuration files, you can use file or image-level backup options of Veeam Backup
& Replication or Veeam Agent for Linux.

SAP HANA Server for Disaster Recovery

You can use Veeam Backup & Replication or Veeam Agent to create an image-level backup of the SAP HANA
server. Note that to create transaction-consistent backups, you must use pre-freeze and post-thaw scripts.

Veeam Plug-in Configuration File

To back up the configuration file of Veeam Plug-in, back up the following file:
/opt/veeam/VeeamPluginforSAPHANA/veeam_config.xml

Backup Files
Veeam Plug-in stores backup files in the following formats:

• A .VAB file stores compressed and deduplicated copy of a SAP HANA database. Veeam Plug-in creates
.VAB files for all types of backups.

• A .VASM file stores metadata that contain information about the backup. A .VASM file is created for each
.VAB file. .VASM files are used by Veeam Backup & Replication to get data about Veeam Plug-in backups.

• A .VACM file stores metadata of a backup job object.

25 | Veeam Plug-ins for Enterprise Applications | User Guide

Veeam Backup Repositories
Veeam Plug-ins store backup files in repositories added to the Veeam Backup & Replication infrastructure. In
this section, you can find the list of supported backup repositories and limitations for Veeam Plug-in backups.

Supported Backup Repositories

Veeam Plug-in for SAP HANA supports integration with the following types of repositories added to the Veeam
Backup & Replication infrastructure:

• Windows Server

• Linux Server

• CIFS (SMB) Share

• Dell EMC Data Domain

• HPE StoreOnce. If you plan to use HPE StoreOnce as a backup repository for Veeam Plug-in for SAP HANA,
the total number of stored files (data and metadata) must not exceed 1,000,000 per storage system.

• Quantum DXi

• NFS File Share

• ExaGrid. Mind the following:

o Follow the requirements in the ExaGrid section of the Veeam Backup & Replication User Guide.

o In the global.ini of SAP HANA, set the max_recovery_backint_channels parameter value to

a number lower than the repository task slots. ExaGrid recommends setting it to 1, and adjust
gradually if needed.

You can also use scale-out backup repositories that contain repositories supported by Veeam Backup &
Replication.

Backup Repositories Limitations

• For Veeam Plug-in backups, the warning which indicates that free space on a storage device has reached a
specified threshold is configured in the veeam_config.xml file of Veeam Plug-in. The warning settings in
the Veeam Backup & Replication console does not affect this setting.
To configure the warning settings, add the following parameter in the
/opt/veeam/VeeamPluginforSAPHANA/veeam_config.xml file.

<PluginParameters repositoryFreeSpacePercentWarning="10" />

• Due to specific design of SAP HANA backups, Veeam Plug-in does not use fast cloning. Backups
transferred to repositories that use ReFS or XFS as a file system are processed the same way as with NTFS
repositories.

• The plug-in configuration wizard will not show repositories where the Encrypt backups stored in this
repository option is enabled. To learn how to disable the encryption option, see Access and Encryption
Settings on Repositories.

26 | Veeam Plug-ins for Enterprise Applications | User Guide

 • Make sure Veeam backup repositories have enough free space to store database backups and transaction
log backups. If required, you can use a scale-out backup repository.

• If you use Veeam Plug-in for SAP HANA version 9.5 Update 4, Veeam Backup & Replication backup copy
jobs does not process and copy the backups created by the plug-in.

• Veeam extract utility cannot extract backup files created by Veeam Plug-in.

• For security reasons, it is recommended to use separate repositories for different users and grant access to
backup repositories only for required users.

Scale-Out Backup Repositories

If you want to store Veeam Plug-in backups in the scale-out backup repositories, mind the following:

• For Veeam Plug-in backups and backup copies, the Performance policy of a scale-out repository functions
a little differently:

a. Veeam Backup & Replication checks if there are extents without warning on free space insufficiency. If
all extents have the warning, Veeam Backup & Replication uses an extent with the largest amount of
free space that has a free task slot.

b. If there are extents without the warning, Veeam Backup & Replication checks if there are incremental
extents with free task slots. If there are no incremental extents with free task slots, Veeam Backup &
Replication uses a full extent with least amount of used task slots.

c. If there are incremental extents with free task slots, Veeam Backup & Replication sends backup files
to an incremental extent with least amount of used task slots. If the amount of used tasks is the same,
an extent with the most amount of free space.

• If a scale-out repository is configured in the Data locality policy, repository extents will be selected
according to the amount of free space for each SAP HANA Backint connection. If there are two extents
with one slot on each extent, the backup will be launched on two streams (one on each extent).

• If you want to add repositories as extents to a scale-out backup repository, and Veeam Plug-in backups
are present on the source repository, you must do the following:

a. Copy the Veeam Plug-in job folder (the whole folder) to an existing scale-out backup repository
extent.

b. Delete the backups from the source repository.

c. Rescan the source repository.

d. Add the repository as an extent to the scale-out repository.

e. Rescan the scale-out repository.

f. Set the scale-out repository as target in the Veeam Plug-in settings.

g. Map the imported backups using the following command:

sudo SapBackintConfigTool --map-backup

27 | Veeam Plug-ins for Enterprise Applications | User Guide

Capacity Tier
You can configure Veeam Backup & Replication to transfer Veeam Plug-in backup files to a capacity tier. Both
policies (Move policy, Copy policy) are supported for Veeam Plug-in backups with the following limitations:

• For Veeam Plug-in backup files, capacity tier does not verify whether data that is being moved is unique
and has not been offloaded earlier. Thus, it is highly recommended to check the pricing plans of your
cloud storage provider to avoid additional costs for offloading and downloading backup data.

• Capacity tier does not track dependencies of full and incremental Veeam Plug-in backup files. Thus, mind
the following:

o [For the Move policy] When backup files are transferred to the capacity tier, Veeam Backup &
Replication takes into account only the creation time of backup files. Make sure that the
operational restore window is not longer than the whole backup chain cycle period. Otherwise, you
may encounter the scenario when full backup files are transferred to the capacity tier and their
increment backup files still remain in the performance tier.

o The capacity tier immutability expiration date does not have the additional block generation period.
The immutability expiration date is based only on the number of days specified in settings of the
object storage backup repository.

• If a scale-out repository is down, you cannot restore from the Veeam Plug-in backup files stored on the
capacity tier. In this case, you can only import the backup files manually and then perform the data
recovery operations.

• If you use a capacity tier that has been created in Veeam Backup & Replication version 10, you cannot
transfer Veeam Plug-in backup files to a capacity tier. However, if you want to transfer them manually,
do the following:

o If the backup files are created by Veeam Plug-in version 10, upgrade the metadata of backup files
as described in Upgrading Metadata Files to New Format.

o Run the Start-VBROffloadBackupFile PowerShell command to send backup files to the capacity tier.

• If you want to restore from backups stored on the capacity extent, at least one performance extent
must be available or you must switch the catalog_backup_using_backint parameter to the False
state in the global.ini file. Otherwise, at the end of the restore process, SAP Backint will not be able
to back up the catalog and restore will fail.

28 | Veeam Plug-ins for Enterprise Applications | User Guide

Access and Encryption Settings on Repositories
When you configure Veeam Plug-in, you specify an account that must be used to connect to the Veeam Backup
& Replication server. To be able to store backups on a backup repository, the specified account must have access
permissions on the target backup repository.

To grant access permissions, do the following:

1. In Veeam Backup & Replication, open the Backup Infrastructure view.

2. In the inventory pane, click the Backup Repositories node or the Scale-out Repositories node.

3. In the working area, select the necessary backup repository, click Set Access Permissions on the ribbon or
right-click the backup repository and select Access permissions.

4. In the Access Permissions window, specify to whom you want to grant access permissions on this backup
repository:

o Allow to everyone — select this option if you want to grant repository access to any user. This option
is equal to granting access rights to the Everyone group in Microsoft Windows (anonymous users are
excluded). For security reasons, the option is not recommended for production environments.

o Allow to the following accounts or groups only — select this option if you want only specific users to
be able to store backups on this repository. Click Add to add the necessary users and groups to the
list.

29 | Veeam Plug-ins for Enterprise Applications | User Guide

 5. Veeam Plug-ins cannot send backups or backup copies to a repository where encryption is enabled. Thus,
unselect the Encrypt backups stored in this repository check box.

30 | Veeam Plug-ins for Enterprise Applications | User Guide

Deployment and Configuration
To deploy Veeam Plug-in, you must install the plug-in on a SAP HANA server and configure plug-in integration
settings. In this section:

• Installing Veeam Plug-in for SAP HANA

• Configuring Veeam Plug-in for SAP HANA

• Automatic Configuration of Veeam Plug-in for SAP HANA

• Importing Backups

This guide gives instructions on how to deploy Veeam Plug-in assuming that you have already deployed a
Veeam Backup & Replication server and configured a backup repository. If you need instructions on how to
deploy Veeam Backup & Replication, see the Veeam Backup & Replication User Guide for your platform.

31 | Veeam Plug-ins for Enterprise Applications | User Guide

Installing Plug-in for SAP HANA
Veeam Plug-in for SAP HANA is an additional component of Veeam Backup & Replication, and the installation
package of the plug-in is included in the Veeam Backup & Replication installation ISO file.

To install Veeam Plug-in, do the following:

1. Mount the Veeam Backup & Replication installation ISO file.

If you deploy Veeam backup infrastructure for the first time, you can download Veeam Backup &
Replication at: https://www.veeam.com/backup-replication-vcp-download.html.

2. In the mounted ISO, go to /Plugins/SAP HANA/x64. You can install the plug-in using the RPM package
or TAR.GZ bundle. Do one of the following, depending on the type of package suitable for your OS. Note
that the install operations in the terminal of the Linux machine require root privileges.

o To install from the RPM package:

i. Upload the VeeamPluginforSAPHANA-X.X.X.XXXX.x86_64.rpm file to the SAP HANA

server.

ii. To install Veeam Plug-in, run the following command:

rpm -i VeeamPluginforSAPHANA-X.X.X.XXXX.x86_64.rpm

o To install from the TAR.GZ bundle:

i. Upload the VeeamPluginforSAPHANA.tar.gz file to the SAP HANA server.

ii. Create the /opt/veeam directory.

mkdir /opt/veeam

iii. Unpack the bundle to the /opt/veeam directory:

tar -xzvf -i VeeamPluginforSAPHANA.tar.gz -C /opt/veeam

NOTE

If you want to install Veeam Plug-in on an SAP HANA scale-out cluster, repeat the described installation
process on all cluster nodes.

32 | Veeam Plug-ins for Enterprise Applications | User Guide

Configuring Plug-in for SAP HANA
When you configure Veeam Plug-in settings, you set up integration settings between a SAP HANA server,
Veeam Backup & Replication server and backup repositories where backup files will be stored. Veeam Plug-in
uses the SapBackintConfigTool wizard to configure the integration settings. The wizard configures the SAP
HANA Backint settings and creates the/opt/veeam/VeeamPluginforSAPHANA/veeam_config.xml file.

NOTE
• The configuration of Veeam Plug-in must be performed by a user with database administrator rights
on all SAP HANA instances of the server.
• The SAP HANA High Level Isolation mode is not supported.

See the following instructions:

• Veeam Plug-in Configuration

• Configuration of Veeam Plug-in on Multiple SAP HANA Instances

• Verifying Configuration of Veeam Plug-in for SAP HANA

• Configuration Tool Commands

Veeam Plug-in Configuration

To configure Veeam Plug-in, do the following:

1. Log in as a user with database administrator rights and run the following command to launch the Veeam
Plug-in configuration tool. You do not need root privileges if you have configured group access as
described in the Required Permissions section.

sudo SapBackintConfigTool --wizard

2. Specify the DNS name or IP address of your Veeam Backup & Replication server.

Enter backup server name or IP address: serv02.tech.local

3. Specify the port which will be used to communicate with the backup server. Default port: 10006.

Enter backup server port number: 10006

4. Specify credentials to authenticate against the Veeam Backup & Replication server.

Enter username: serv02\administrator

Enter password for serv02\administrator:

33 | Veeam Plug-ins for Enterprise Applications | User Guide

 IMPORTANT

You can work with backups created by Veeam Plug-in only with the account used for creating the
backups. If you want to use another account, assign the Veeam Backup Administrator role or the
Veeam Backup Operator and Veeam Restore Operator roles to the account.
To learn how to assign Veeam Backup & Replication roles, see the Roles and Users section of the
Veeam Backup & Replication Guide.

5. Select the backup repository where you want to store backups. In the terminal dialog, enter the number of
the repository from the list of available repositories.

Available backup repositories:

1. serv10_repo
2. serv07_repo
Enter repository number: 1
Configuration result:
SID SH2 has been configured

IMPORTANT
• The used account must have access to Veeam backup repositories that you plan to use.
• Encryption must be disabled on the repository.

Otherwise, the repositories will not be listed as available. To learn how to configure access and
encryption settings on repositories, see Access and Encryption Settings on Repositories.

If you start the wizard for the first time on an SAP HANA scale-out cluster, the wizard asks you for a
cluster name. The cluster name will be used by Veeam Backup & Replication to identify the backup job for
the cluster. Further runs of the wizard within the SAP HANA scale-out cluster will not ask for this entry
again.

Configuration of Veeam Plug-in on Multiple SAP HANA

Instances
Configuration of Veeam Plug-in includes configuration or creation of the SAP HANA Backint symlinks on all SAP
HANA instances. To be able to do this for multiple SAP HANA instances at the same time, the configuration must
be performed by a user with root privileges. Alternatively, you can use an account from the sapsys user group to
configure the plug-in and set the symlink for SAP HANA instances where the account has access rights. You can
repeat the wizard under another account to configure additional SAP HANA instances.

Alternatively, you can configure a Linux security group. To do that, you must add all Veeam Plug-in admins to
this security group and set the following rights:

chown root:<youradmingroup> /opt/veeam/VeeamPluginforSAPHANA/veeam_config.xml

chmod 664 /opt/veeam/VeeamPluginforSAPHANA/veeam_config.xml

To learn about required permissions for backup and restore operations within SAP HANA, see the Authorization
for Backup and Recovery section of the SAP HANA Administration Guide.

34 | Veeam Plug-ins for Enterprise Applications | User Guide

Verifying Configuration of Veeam Plug-in for SAP HANA
When you finish the plug-in configuration wizard, the plug-in creates a soft link in the
/hana/shared/<SID>/global/hdb/opt directory.

To verify that the Backint Agent is configured correctly, do the following:

1. Connect to the database using SAP HANA Studio or Cockpit.

2. Go to Backup/Configuration.

3. In the Backint Agent field, make sure that the specified path leads to
/opt/veeam/VeeamPluginforSAPHANA/hdbbackint.

Configuration Tool Commands

Apart from running a configuration wizard, you can use the SapBackintConfigTool tool to change a specific
parameter in the veeam_config.xml file or enable/disable Veeam Plug-in features.

See the list of available commands for SapBackintConfigTool:

Command Description

--help Shows the list of tool parameters.

--show-config Shows configuration parameters.

Starts the wizard to configure the plug-in settings. This wizard edits the
--wizard veeam_config.xml file or creates a new one if the configuration file was
removed from the /opt/veeam/VeeamPluginforSAPHANA directory.

35 | Veeam Plug-ins for Enterprise Applications | User Guide

 Command Description

--set-credentials Specifies credentials to log in to the Veeam Backup & Replication server.
<"serv\username">
<password>

--set-host <hostname> Specifies the IP address or hostname of the Veeam Backup & Replication server.

--set-port Specifies a port number that will be used to communicate with the Veeam
<port_number> Backup & Replication server.

Launches a wizard to select a backup repository. A backup repository is selected

--set-repository from repositories which are available in the connected Veeam Backup &
Replication instance.

--set-restore-server [for System Copy] Specifies the backup that will be copied.

--map-backup Maps the imported backup.

--set-force-delete Deletes backup files after specified days.

Enables restore from backup copy. Note that if you enable restore from backup
copy, you cannot back up databases with Veeam Plug-in. To revert changes, you
--configure-restore- must disable restore from backup copy.
from-copy
Note that when you launch the command, the wizard will ask you to reconfigure
the catalog backup from backint to disk.

--promote-backup-copy- Maps the imported backup copy to a regular Veeam Plug-in backup chain.
to-primary

Example:

To specify credentials that will be used to log in to the Veeam Backup & Replication server, use the plug-in
configuration tool with the following command.

SapBackintConfigTool --set-credentials "serv02\Administrator" "password"

36 | Veeam Plug-ins for Enterprise Applications | User Guide

Updating Plug-in for SAP HANA
Periodically, Veeam releases a new version of Veeam Backup & Replication that contains new features and bug
fixes. The release package also contains a new version of Veeam Plug-ins.

To update Veeam Plug-in for SAP HANA:

1. Upload the new VeeamPluginforSAPHANA-X.X.X.XXXX.x86_64.rpm package to the SAP HANA

server.

2. Run the following command. Note that the operation requires root privileges.

rpm -U VeeamPluginforSAPHANA-X.X.X.XXXX.x86_64.rpm

IMPORTANT

Version of Veeam Backup & Replication must be the same or newer that the version of Veeam Plug-in. Note
that if you want to use the latest functionality, you must update both Veeam Backup & Replication and
Veeam Plug-in to the latest version.

37 | Veeam Plug-ins for Enterprise Applications | User Guide

Uninstalling Plug-in for SAP HANA
To uninstall Veeam Plug-in for SAP HANA on a Linux machine, go to the directory with the Veeam Plug-in
package and run the following command. Note that the operation requires root privileges.

rpm -e VeeamPluginforSAPHANA

38 | Veeam Plug-ins for Enterprise Applications | User Guide

Automating Configuration of Plug-in for SAP
HANA
To automate the configuration of Veeam Plug-in for SAP HANA, do the following:

1. Copy the veeam_config.xml file to other servers where you want to configure the plug-in.

2. The password stored in the configuration file is encrypted with a machine key. Thus, on each machine,
after the veeam_config.xml file was copied, you must reset the password of the account used to log in
to the Veeam Backup & Replication server. To reset the password, use the following command. Note that
the operation requires root privileges.

SapBackintConfigTool --set-credentials <"serv\username"> <password>

39 | Veeam Plug-ins for Enterprise Applications | User Guide

Importing Backups
If you have lost the Veeam Backup & Replication database or want to import backup files on another Veeam
Backup & Replication server, do the following:

1. Copy the backup file folder to a backup repository or create add a new backup repository with this folder
as a subfolder.

TIP

Starting from version 11, each Veeam Plug-in backup file (.vab) has its own metadata file (.vasm).
Make sure you import backup files and all related metadata files. Also, you must import the backup
job metadata file (.vacm) which is stored in the same folder.

2. Log in to the Veeam Backup & Replication console.

3. Open the Backup Infrastructure view.

4. In the inventory pane of the Backup Infrastructure view, select the Backup Repositories node.

5. In the working area, select the required backup repository and click Rescan on the ribbon. Alternatively,
you can right-click the backup repository and select Rescan.

6. On the SAP HANA server, set the new repository as target in the Veeam Plug-in settings:

sudo SapBackintConfigTool --set-repository

Available backup repositories:
1. serv10_repo
2. serv07_repo
Enter repository number: 1
Configuration result:
SID SH2 has been configured

40 | Veeam Plug-ins for Enterprise Applications | User Guide

 7. Start the Veeam Plug-in configuration wizard with the following parameter:

sudo SapBackintConfigTool --map-backup

IMPORTANT
• If backup files are not imported according to instructions given above, the backup and restore jobs
can fail.
• [For backups of scale-out clusters and servers with the customServerName option] To avoid
mapping failure, the cluster name must be the same as the name used before importing backups.

41 | Veeam Plug-ins for Enterprise Applications | User Guide

Upgrading Backup Files
Since version 11, Veeam Plug-in uses a new format of backup files: instead of one metadata file for all backup
files there are separate metadata files (.vasm) for each database backup file (.vab). The new metadata format
allows to optimize the productivity of backup and restore operations.

For Veeam Plug-in 11, the backup files upgrade is not obligatory. However, in the next version, backup files
created by Veeam Plug-in version 10 will not be supported.

Prerequisites
Before upgrading backup files, make sure the following requirements are met.

• Make sure that you have upgraded Veeam Plug-in on the source server. If the plug-in is not upgraded to
version 11 and you upgrade the backup files, then all next backup job runs will fail.

• Make sure that you have disabled the backup job whose backup files you want upgrade. You must also
disable the backup copy jobs that use these backup files as a source.

• If the backup files reside on the scale-out backup repository, all repository extents must be available.
Also, the extents must not be in the Seal or Maintenance mode.

• If you want to upgrade backup files created by a backup copy job, you must meet the same requirements
as for the backup job files.

• During the process of the metadata upgrade, you cannot run the target backup job and you cannot restore
from the backup files.
The upgrade process duration depends on the number of backup files in the backup set, type of the
backup repository and workload level on the file system.
For example, there are backup files of an SAP HANA server that contains 10 instances and is backed up
every 15 minutes with the retention policy set for 2 weeks. The upgrade of backup files can have the
following duration on not overloaded file systems:

o Microsoft Windows: 30 minutes

o Linux: from 30 minutes to 3 hours

o SMB/NFS: 1.5 hours

o Data Domain Boost/Quantum DXi/ExaGrid/CIFS (SMB)/NFS file share: 3-4 hours

o HPE StoreOnce: up to 10 hours (due to specifics of this repository type for processing large number of
files)

Upgrading Backup Files in Veeam Backup & Replication

Console
To upgrade backup files in the Veeam Backup & Replication console, do the following:

1. Open the Home view.

2. In the inventory pane, expand the Backups view and select Disk.

3. In the working area, right-click the job or the restore point and select Upgrade.

42 | Veeam Plug-ins for Enterprise Applications | User Guide

Alternatively, you can select the job or the restore point and click Upgrade on the ribbon.

43 | Veeam Plug-ins for Enterprise Applications | User Guide

Database Protection
After you configure Veeam Plug-in, you can back up databases with SAP HANA backup tools. Veeam Plug-in will
automatically transfer data to the Veeam backup repository and store this data in Veeam proprietary format.
The backup process itself is performed by SAP HANA Backint.

Keep in mind that examples in this section are provided only for demonstrating purposes. For details on full
backup functionality of SAP HANA tools, see the SAP HANA Backup section of the SAP HANA Administration
Guide.

IMPORTANT

Veeam Plug-in transfers backup data to the Veeam backup repository only when you perform the backup
using SAP Backint.

To back up SAP HANA databases, you can use SQL commands or SAP HANA administration tools. For examples,
see the following guides:

• Backing Up Databases Using SQL Commands

• Backing Up Databases with SAP HANA Studio

• Backing Up Databases with SAP HANA Cockpit

44 | Veeam Plug-ins for Enterprise Applications | User Guide

Database Backup (HDBSQL Scripts)
You can use HDBSQL to backup and restore SAP HANA databases using Backint. For details on the HDBSQL
backup, see the BACKUP DATA Statement section of the SAP HANA SQL and System Views Reference.

The following example shows how to configure secure storage of SAP HANA connection data and provides a list
of options for the SAP HANA database backup process.

Prerequisites
Before the backup process, you can use the HDBUSERSTORE tool to set secure storage of SAP HANA connection
details.

Log in to SAP HANA HDBSQL as the operating system administrator ( <sid>adm) run the following commands.
For details, see the Secure User Store section of the SAP HANA Security Guide.

sh4adm@linux-q0pn:/usr/sap/SH4/HDB01> hdbuserstore SET <key> hostname:30013@SID

<username> <password>
sh4adm@linux-q0pn:/usr/sap/SH4/HDB01> hdbsql -U <key>

Backing Up SAP HANA Databases Using Backint

To back up the database with Backint, use one of the following commands depending on which type of backup
you want to perform:

• Full backup of SYSTEMDB.

backup data using backint ('backup_name_prefix');

• Differential backup of SYSTEMDB.

backup data differential using backint ('backup_name_prefix');

• Incremental backup of SYSTEMDB.

backup data incremental using backint ('backup_name_prefix');

• Full backup of a tenant database.

backup data for <TENANT_DATABASE_NAME> using backint ('backup_name_prefix'

);

• Differential backup of a tenant database.

backup data differential for <TENANT_DATABASE_NAME> using backint ('backup

_name_prefix');

45 | Veeam Plug-ins for Enterprise Applications | User Guide

 • Incremental backup of a tenant database.

backup data incremental for <TENANT_DATABASE_NAME> using backint ('backup_

name_prefix');

• Full backup of a tenant database with the ASYNCHRONOUS option. The ASYNCHRONOUS option can be
helpful if you monitor SAP HANA backups on another host and just want to run the backup command from
a script. The option runs the backup job in the background and closes the current script session.

backup data for <TENANT_DATABASE_NAME> using backint ('backup_name_prefix'

) ASYNCHRONOUS;

46 | Veeam Plug-ins for Enterprise Applications | User Guide

Database Backup (SAP HANA Studio)
After you configure Veeam Plug-in, you can back up your databases with SAP HANA Studio. Veeam Plug-in will
automatically transform the backup files to Veeam backup repository.

The example provided below is for demonstration purposes only. For details on the full backup functionality of
SAP HANA Studio, see the Creating Data Backups and Delta Backups section of the SAP HANA Administration
Guide.

To perform Backint backup with SAP HANA Studio, do the following:

1. In SAP HANA Studio, connect to the database as a user with DATABASE ADMIN privileges.

2. In the Systems view, right-click the database.

3. Select Backup and Recovery and then select Back Up System Database or Back Up Tenant Database.

4. In the backup wizard, specify backup settings:

a. Select the required backup type:

▪ Complete Data Backup: backup of all data structures required to recover the database.

▪ Incremental Data Backup: backup of data changed since the last full data backup or the last
delta backup.

▪ Differential Data Backup: backup of data changed since the last full data backup.

b. In the Destination Type list, select Backint. With this option selected, Veeam Plug-in will transfer the
backup file to Veeam backup repository.

c. Change the default backup prefix, if needed.

47 | Veeam Plug-ins for Enterprise Applications | User Guide

 d. Click Next.

48 | Veeam Plug-ins for Enterprise Applications | User Guide

 5. In the Review Backup Settings step of the wizard, click Finish to start the backup process.

After you launch the backup process, SAP HANA Studio will back up the database, and Veeam Plug-in will
forward backup files to the backup repository that is specified in the Veeam Plug-in settings.

49 | Veeam Plug-ins for Enterprise Applications | User Guide

Database Backup (SAP HANA Cockpit)
After you configure Veeam Plug-in, you can back up your databases with SAP HANA Cockpit 2.0. You can
perform complete, incremental, and differential backups of SYSTEMDB and tenant databases. Veeam Plug-in
will automatically transform backup files to Veeam backup repository. Keep in mind that you must select the
Backint option as a destination target.

The example provided below is for demonstrating purposes only. For details on the full backup functionality of
SAP HANA Cockpit, see the Create Data Backups and Delta Backups of the SAP HANA Administration Guide.

To perform Backint backup with SAP HANA Cockpit, do the following:

1. In the System Overview page, go to Database Administration and select Manage Database Backups.

2. At the Backup Catalog section, click Create Backup.

3. Specify backup settings:

a. Select the required backup type:

▪ Complete Data Backup: backup of all data structures required to recover the database.

▪ Incremental Data Backup: backup of data changed since the last full data backup or the last
delta backup (incremental or differential).

▪ Differential Data Backup: backup of data changed since the last full data backup.

50 | Veeam Plug-ins for Enterprise Applications | User Guide

 b. In the Destination Type setting, select Backint. With this option selected, Veeam Plug-in will transfer
the backup to Veeam backup repository.

c. Change the default prefix for the backup file, if needed.

d. To start the backup, click Back Up.

51 | Veeam Plug-ins for Enterprise Applications | User Guide

Backup Job in Veeam Backup & Replication
Console
After you start a backup process with SAP HANA Backint, Veeam Backup & Replication creates a backup job. You
can use this job to view the statistics on the backup process, generate backup job reports or you can also disable
the backup job.

You cannot launch or edit SAP HANA backup jobs in the Veeam Backup & Replication console. You can manage
backup operations only on the SAP HANA side using SAP HANA Studio, SAP HANA Cockpit or HDBSQL.

NOTE

Due to specifics of the SAP HANA backup process, the progress bar of a running SAP HANA backup job is
not available.

To view details of a backup job process, do the following.

1. Open the Veeam Backup & Replication console.

2. In the Home view, expand the Jobs node and click Backup.

3. In the list of jobs, select the SAP HANA backup job to see details of the current backup process or the last
backup job session.

Generating Backup Job Reports

You can generate reports with details about an SAP HANA backup job session performance. The session report
contains the following session statistics: session duration details, details of the session performance, amount of
read, processed and transferred data, backup size, compression ratio, list of warnings and errors (if any).

1. Open the Home view.

52 | Veeam Plug-ins for Enterprise Applications | User Guide

 2. In the inventory pane, select Jobs.

3. In the working area, select the necessary job and click Report on the ribbon. You can also right-click the
job and select Report.

Disabling Backup Job

You can disable SAP HANA backup jobs in the Veeam Backup & Replication console. If you disable the job, you
will not be able to run SAP Backint backup commands on the SAP HANA server.

To disable a backup job:

1. Open the Home view.

2. In the inventory pane, select Jobs.

3. In the working area, select the necessary job and click Disable on the ribbon. You can also right-click the
job and select Disable.

53 | Veeam Plug-ins for Enterprise Applications | User Guide

Database Recovery
With the configured Veeam Plug-in you can restore SAP HANA databases from the backups that reside on the
Veeam backup repository. All restore operations are performed on the SAP HANA side. To restore databases,
you can use SAP HANA Cockpit, SAP HANA Studio, or HDBSQL.

Keep in mind that examples provided in this section are for demonstrating purposes only. To see the full restore
functionality of SAP HANA tools, see the SAP HANA Recovery section of SAP HANA Administration Guide.

To learn how to recover SAP HANA databases from backups stored on Veeam repositories, see:

• Recovering Databases Using SQL Commands

• Recovering Databases with SAP HANA Studio

• Recovering SYSTEMDB with SAP HANA Cockpit

• Recovering Tenant Databases with SAP HANA Cockpit

• Recovering Databases to Other Servers

54 | Veeam Plug-ins for Enterprise Applications | User Guide

Restoring Databases (HDBSQL Commands)
You can use HDBSQL to restore SAP HANA databases from backups stored on Veeam backup repositories. For
details on the HDBSQL restore, see the RECOVER DATABASE Statement section of the SAP HANA SQL and
System Views Reference.

To recover SAP HANA databases from backups stored on Veeam backup repositories, do the following:

1. Log in to SAP HANA HDBSQL as the HDB administrator. Use HDBUSERSTORE to securely store connection
details on a client machine.

sh4adm@linux-q0pn:/usr/sap/SH4/HDB01> hdbuserstore SET <key> hostname:3001

3@SID <username> <password>
sh4adm@linux-q0pn:/usr/sap/SH4/HDB01> hdbsql -U <key>

2. Recover a tenant database to the latest state using Backint. As the timestamp, specify the current data
and time or future date and time.

alter stop database <DATABASE_NAME>;

recover database for <DATABASE_NAME> until timestamp '2020-01-01 12:00:00'
using catalog backint;

55 | Veeam Plug-ins for Enterprise Applications | User Guide

Restoring Databases (SAP HANA Studio)
You can restore SAP HANA databases from the Veeam Plug-in backups using SAP HANA Studio.

The example below is provided for demonstration purposes only. For details on the full restore functionality of
SAP HANA tools, see the Recovering an SAP Database section of the SAP HANA Administration Guide.

To perform a Backint recovery from Veeam Plug-in backups, do the following:

1. Log in to SYSTEMDB using as a user with DATABASE ADMIN privileges.

2. Right-click the SYSTEMDB database.

3. Click Backup and Recovery and select Recover System Database or Recover Tenant Database.

4. Enter the operating system user credentials.

56 | Veeam Plug-ins for Enterprise Applications | User Guide

 5. Recovery process requires the database to be shut down. In the pop-up window, click OK to confirm the
database shutdown.

6. At the Specify Recovery Type step of the recovery wizard, select the required restore point or the option
to restore the database to the most recent state.

7. At the Locate Backup Catalog step of the wizard, select one of the following, depending on where your
backup catalogs reside:

o Search for the backup catalog in the file system only.

57 | Veeam Plug-ins for Enterprise Applications | User Guide

 o Search for the backup catalog in Backint only.

58 | Veeam Plug-ins for Enterprise Applications | User Guide

 8. Select the required backup to restore.

59 | Veeam Plug-ins for Enterprise Applications | User Guide

 9. At the Locate Log Backups step, click Next.

10. At the Other Settings step:

a. Switch on the availability check for the Backint backups.

b. If you are recovering the database to a database with a new SID or landscape ID, select the Install
New License Key check box and specify the path to the license file.

60 | Veeam Plug-ins for Enterprise Applications | User Guide

 c. Click Next.

61 | Veeam Plug-ins for Enterprise Applications | User Guide

 11. At the Review Recovery Settings step, click Finish.

62 | Veeam Plug-ins for Enterprise Applications | User Guide

Restoring SYSTEMDB (SAP HANA Cockpit)
You can restore SAP HANA SYSTEMDB databases from the Veeam Plug-in backups using SAP HANA Cockpit.

The example below is provided for demonstration purposes only. For details on the full restore functionality of
SAP HANA Cockpit, see the Recovering an SAP HANA Database section of the SAP HANA Administration Guide.

Before You Begin

Before you start the recovery, shut down the database that you want to recover:

1. In the SAP HANA Cockpit console, locate the database that you want to recover.

2. In the Overall Database Status block, click Stop System.

63 | Veeam Plug-ins for Enterprise Applications | User Guide

 3. At the Manage Services section, click Stop System and select the Softly option to shut down the database
after SAP HANA finishes running statements.

Performing Recovery
To perform a Backint recovery of SYSTEMDB from a Veeam Plug-in backup, do the following:

1. In the System Overview block, go to the Database Administration section and click Recover database.

64 | Veeam Plug-ins for Enterprise Applications | User Guide

 2. At the Recovery Target step, select the required restore point or the option to restore the database to the
most recent state. Then, click Step 2.

3. Specify the location of the latest backup catalog and click Step 3.

4. At the Backup to be Used step, select the backup and click Step 4.

65 | Veeam Plug-ins for Enterprise Applications | User Guide

 5. At the Delta Backups step, select Yes to use delta backups.

6. At the Specify Alternative Backup Locations step, if you want to use backups that are not in the backup
catalog, specify their locations. You can also change the location for log backups.
If you you leave the fields empty, SAP HANA will use the locations specified in the backup catalog.

7. At the Check Availability of Backups step, select Yes or No options, to check if the backups are available.
Note that at this step SAP HANA does not check the integrity of the backup content on the block level.

66 | Veeam Plug-ins for Enterprise Applications | User Guide

 8. At the Initialize Log Area step, select No to initialize the log area and click Review. You must initialize the
log are only if the log area is unavailable or if you are recovering the database to a different system.

9. Review the recovery options and click Start Recovery.

67 | Veeam Plug-ins for Enterprise Applications | User Guide

Recovering Tenant Databases with SAP HANA
Cockpit
You can restore SAP HANA tenant databases from the Veeam Plug-in backups using SAP HANA Cockpit.

The example below is provided for demonstration purposes only. For details on the full restore functionality of
SAP HANA tools, see the Recovering an SAP HANA Database of the SAP HANA Administration Guide.

To perform a Backint recovery of an SAP HANA tenant database from a Veeam Plug-in backup, do the following:

1. In the System Overview page of the required system, click Manage Databases.

2. In the Manage Databases page, expand the toolbar options and select Recover Tenant.

3. After you launch the recovery wizard, SAP HANA will issue the warning that the database must be stopped
for recovery. Click Stop Tenant in the warning window.

4. At the Recovery Target step of the wizard, select the required restore point and click Step 2.

68 | Veeam Plug-ins for Enterprise Applications | User Guide

 5. Specify the location of the latest backup catalog and click Step 3.

6. At the Backup to be Used step, select the backup and click Step 4.

7. At the Delta Backups step, select Yes to use delta backups.

69 | Veeam Plug-ins for Enterprise Applications | User Guide

 8. At the Specify Alternative Backup Locations step, if you want to use backups that are not included in the
backup catalog, specify their locations. You can also change the location for log backups.
If you leave the fields empty, SAP HANA will use the locations specified in the backup catalog.

9. Select Yes or No, to check if the backups are available. Note that at this stage SAP HANA does not check
the integrity of the backup content on the block level.

10. Select No to initialize the log area and click Review. You must initialize the log area only if the log area is
unavailable or if you are recovering the database to a different system.

70 | Veeam Plug-ins for Enterprise Applications | User Guide

 11. Review the recovery options and click Start Recovery.

71 | Veeam Plug-ins for Enterprise Applications | User Guide

Recovering Databases to Other Servers (System
Copy)
You can restore SAP HANA databases from Veeam Plug-in backups to another server. To restore databases to
another server, you must reconfigure settings of Veeam Plug-in as shown below.

For security reasons, you can restore databases to another server only in the following condition. The account
you use to connect to Veeam Backup & Replication server must be the same account that performed the backup
of the source system. If you want to use another account, you can assign the Veeam Backup Administrator or
Veeam Restore Operator roles to the required account. For details on assigning Veeam Backup & Replication
roles, see the Roles and Users section of the Veeam Backup & Replication User Guide.

Procedure
To restore databases to another server, you must reconfigure settings of Veeam Plug-in as shown below:

1. Go to /opt/veeam/VeeamPluginforSAPHANA and run the following command to select the source

server whose backups you want to use during restore.

VM2ADM:/opt/veeam/VeeamPluginforSAPHANA> SapBackintConfigTool --set-restor

e-server
Select source SAP HANA plug-in server to be used for system copy restore:
1. SAP-VM1
2. SAP-VM02
Enter server number: 1

2. Specify a backup repository where the required backup files are stored.

Available backup repositories:

1. serv10_repo
Enter repository number: 1

NOTE
• The account used to connect to Veeam Backup & Replication server must have access
permissions on the required repository. Otherwise the repository will not be displayed in the
list of available repositories. To learn how to configure access permissions on repositories, see
Setting Up User Permissions on Backup Repositories.
• The wizard does not import existing backups from the repository. To perform a System Copy
restore from the imported backup, you must map the backup. For details, see Importing
Backups.

3. Perform the SAP HANA System Copy based restore following this SAP KB article.

4. After the restore, you must revert back the restore-server option of the Veeam Plug-in configuration
wizard. Otherwise, you will not be able to restore data from the actual server backup file. If you perform
only restore to other server, leave this setting enabled. It will not affect the backups of the actual system.

72 | Veeam Plug-ins for Enterprise Applications | User Guide

 VM2ADM:/opt/veeam/VeeamPluginforSAPHANA> SapBackintConfigTool --set-restor
e-server
Select source SAP HANA plug-in server to be used for system copy restore:
1. SAP-VM1
2. SAP-VM02
Enter server number: 2
Available backup repositories:
1. serv10_repo
Enter repository number: 1

NOTE

If you are performing a system copy from another database to a database that was previously backed
up by Veeam Plug-in, mind the following.
If the catalog_backup_using_backint parameter is enabled, after performing a system copy, SAP
HANA automatically starts a new log chain and sends it to the backint along with a new catalog
backup. This new catalog backup overwrites the previous catalog, making it impossible to access pre-
restore backups for this database.

If you are planning to restore the older state of this database, you can disable the
catalog_backup_using_backint parameter before performing the system copy.

Also, to have access to pre-restore backups, you can store a copy of the old backup catalog outside
the default directory and specify this catalog during the restore.

73 | Veeam Plug-ins for Enterprise Applications | User Guide

Restore from Backup Copy
You can restore from backups and backup copies. To restore from backup copies, you must enable the restore
from backup copy option in the Veeam Plug-in wizard.

IMPORTANT

If the restore from backup copy option is enabled, you cannot back up databases using Veeam Plug-in, and
you cannot restore from backups created by primary Veeam Plug-in backup jobs. You can restore only from
backup copy files until you disable the restore from backup copy option.

• Enabling Restore from Backup Copy

• Disabling Restore from Backup Copy

Enabling Restore from Backup Copy

To be able to restore from backup copies, do the following:

1. In the machine where Veeam Plug-in is installed, open the terminal and run the following command:

SapBackintConfigTool --configure-restore-from-copy

2. Select the number of the backup copy job you want to use:

Select secondary job for failover:

0. Disable
1. Plug-ins backup copy job\linuxq01 SAP HANA backup <serv10_repo>
Select secondary job for failover:1

IMPORTANT

The account used to connect to the Veeam Backup & Replication server must have access
permissions on the required repository.

Disabling Restore from Backup Copy

To be able to back up with Veeam Plug-in and restore from backups, disable the restore from backup copies (set
the parameter back to 0):

SapBackintConfigTool --configure-restore-from-copy
Select secondary job for failover:
0. Disable
1. Plug-ins backup copy job\linuxq01 SAP HANA backup <serv10_repo>
Select secondary job for failover:0

74 | Veeam Plug-ins for Enterprise Applications | User Guide

Retention of SAP HANA Backups
In the main scenario, when using Veeam Plug-in for SAP HANA, you must configure the retention policy using
native SAP HANA tools. For details the SAP HANA housekeeping options:

• Deleting Backups Using SAP HANA Tools

Also, you can manually delete backups from a backup repository using the Veeam Backup & Replication console
and enable the force deletion functionality of Veeam Plug-in. For details, see:

• Deleting Backups Manually Using Veeam Backup & Replication Console

• Configuring Force Deletion of Backups

75 | Veeam Plug-ins for Enterprise Applications | User Guide

Deleting Backups Using SAP HANA Tools
To configure retention policies for SAP HANA backups, you can use the SAP HANA housekeeping options:

• Manual Deletion of Backups in SAP HANA Studio

• Configuring Retention Policy in SAP HANA Cockpit

• Deletion of Catalog and Backups Using Scripts

IMPORTANT

If you delete backups from a backup catalog using scripts or SAP HANA Studio and don't select the option
to delete backup physically from the backup location, backups will remain in the backup repository. In this
case, we recommend to enable the options for physical deletion of backups in used SAP HANA retention
tools or you must enable the force deletion feature of Veeam Plug-in for SAP HANA. Otherwise, you will
run out of space on the backup repository.

Manual Deletion of Backups in SAP HANA Studio

For details, see the Housekeeping for Backup Catalog and Backup Storage section of the SAP HANA
Administration Guide.

To physically delete the backups, you must select the Catalog and Backup Location option. Note that if you have
physical backups in both the file system and a Veeam backup repository, you can choose to delete data backups
in only one location.

Configuring Retention Policy in SAP HANA Cockpit

For details, see the Retention Policy section of the SAP HANA Administration with SAP HANA Cockpit Guide.
Note that the retention policy functionality is supported only in SAP HANA 2.0 SPS03 and later versions.

When you configure a retention policy in SAP HANA Cockpit, make sure that you have selected the Also delete
physically from Backint check box in the Options for Backup Deletion section. Otherwise the backups will not be
deleted from the repository.

Deletion of Catalog and Backups Using Scripts

Deletion of catalog and backups using scripts. For details see the BACKUP CATALOG DELETE Statement section
of the SAP HANA SQL and Views Reference.

To physically delete backups from the backup repository, you must include the WITH BACKINT and WITH FILE
options in the script.

76 | Veeam Plug-ins for Enterprise Applications | User Guide

Deleting Backups Manually
In the main scenario, when using Veeam Plug-in for SAP HANA, you must configure the retention policy using
native SAP HANA tools. For details on the SAP HANA housekeeping options, see Deleting Backups Using SAP
HANA Tools.

If you have lost the backup catalog, you can delete the backups manually from Veeam backup repositories using
the Veeam Backup & Replication console.

NOTE

If you remove backups from a backup repository manually, the backup catalog will not be updated.

To remove a backup from a backup repository, do the following:

1. In the Veeam Backup & Replication console, open the Home view.

2. In the Inventory pane, select Backups.

3. In the working area, right-click the backup job object name and select Delete from disk.

77 | Veeam Plug-ins for Enterprise Applications | User Guide

Configuring Force Deletion of Backups
In the main scenario, when using Veeam Plug-in for SAP HANA, you must configure the retention policy using
native SAP HANA tools. For details, see Retention of SAP HANA Backups.

Veeam Plug-in for SAP HANA has a functionality that automatically force deletes backup files which are older
than specified number of days. For example, you can use it if a backup repository contains backup files that are
no longer in the backup catalog.

To enable force deletion of backup files, do the following:

1. On the SAP HANA server, run the following command.

SapBackintConfigTool --set-force-delete

2. Enter the number of days after which Veeam Plug-in will force delete backup files on all configured
Veeam backup repositories.

Garbage collector automatically deletes backup files older than the specif
ied number of days.
Make sure the number of days value exceeds your retention policy.
To disable this functionality, set the number of days to 0.
Enter the number of days to delete backups after, between 7 and 999 [0]:

By default, the force delete functionality is disabled (set to 0).

IMPORTANT
• A value for the number of days setting must be at least 1 backup generation period longer than the
retention period for your SAP HANA backups. Otherwise, Veeam Plug-in will delete earliest backups
created within the retention period.
• If a backup repository contains backups older than the specified retention period, Veeam Plug-in
removes old backup files only after the next run of the Backint backup.

78 | Veeam Plug-ins for Enterprise Applications | User Guide

Removing Backups from Configuration
If you want to remove records about backups from the Veeam Backup & Replication console and configuration
database, you can use the Remove from configuration operation.

When you remove a backup from the configuration, backup files (VAB, VBM) remain on the backup repository.
You can import backup files later and restore data from them.

To remove a backup from the configuration:

1. Open the Home view.

2. In the inventory pane, select Backups.

3. In the working area, select the backup and click Remove from > Configuration on the ribbon. You can also
right-click the backup and select Remove from configuration.

79 | Veeam Plug-ins for Enterprise Applications | User Guide

Backup Copy for SAP HANA Backups
Having just one backup does not provide the necessary level of safety. The primary backup may get destroyed
together with production data, and you will have no backups from which you can restore data.

To build a successful data protection and disaster recovery plan, it is recommended that you follow the 3-2-1
rule:

• 3: You must have at least three copies of your data: the original production data and two backups.

• 2: You must use at least two different types of media to store the copies of your data, for example, local
disk and cloud.

• 1: You must keep at least one backup offsite, for example, in the cloud or in a remote site.

Thus, you must have at least two backups and they must be in different locations. If a disaster takes out your
production data and local backup, you can still recover from your offsite backup.

To help you adopt the 3-2-1 rule, Veeam Backup & Replication offers the backup copy functionality that allows
you to create several instances of the same backup in different locations, whether onsite or offsite. Backup
copies have the same format as those created by backup jobs and you can recover your data from them when
you need it.

Veeam Backup & Replication fully automates the backup copy process and lets you specify retention settings to
maintain the desired number of restore points, as well as full backups for archival purposes. Backup copy is a
job-driven process. When enabled, the backup copy job for Veeam Plug-in backups runs continuously.

For details on how it works, see the Backup Copy section of the Veeam Backup & Replication User Guide.

80 | Veeam Plug-ins for Enterprise Applications | User Guide

Creating Backup Copy Job
To copy backups to a secondary location, you must configure a backup copy job. The backup copy job defines
how, where and when to copy backups. One job can be used to process backups of one or more machines.

You can configure a job and start it immediately or save the job to start it later.

Before creating a job, check prerequisites. Then use the New Backup Copy Job wizard to configure a backup
copy job.

1. Launch Backup Copy Job wizard.

2. Specify a job name and description.

3. Selects backups to process.

4. Define backup copy target.

5. Specify advanced settings.

6. Define backup copy schedule.

7. Finish working with the wizard.

Before You Begin

Before you create a backup copy job, check the prerequisites and limitations:

• If you create a backup copy job for a backup of Veeam Plug-in version 9.5 Update 4, the backups will not
be copied. Veeam Plug-in will issue a warning that you must upgrade Veeam Plug-in to version 10. After
you upgrade the plug-in and create a new restore point, backup copy job will start to function and copy
backup files created by both plug-in versions.

• Backup infrastructure components that will take part in the backup copy process must be added to the
backup infrastructure and properly configured. These include source and target backup repositories
between which backups must be copied.

• The target backup repository must have enough free space to store copied backups. To receive alerts
about low space on the backup repository, configure global notification settings. For more information,
see Specifying Other Notification Settings.

• For Veeam Plug-in backup copy jobs, you cannot select a Veeam Cloud Connect repository as a backup
copy target.

• If you have upgraded the backup files, make sure that you have upgraded Veeam Plug-in on the source
server. If the plug-in is not upgraded to version 11 and you convert backup copy files to backup files, then
the next backup job runs will fail.

81 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 1. Launch Backup Copy Job Wizard
To create a backup copy job, do the following:

1. In the Veeam Backup & Replication console, open the Home view.

2. Click the Backup Copy tab and select Application backup.

82 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 2. Specify Job Name and Description
At the Job step of the wizard, specify a name and description for the backup copy job.

1. In the Name field, enter a name for the job.

2. In the Description field, enter a description for the job. The default description contains information about
the user who created the job, date and time when the job was created.

83 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 3. Selects Backups to Process
At the Object step of the wizard, select machines whose backups you want to copy to the target repository.

1. Click the Add button and select from which entity you want to process the machines.

o From jobs: You can select Veeam Plug-in backup jobs. When a backup copy job runs, Veeam Backup &
Replication will search for backup files created by selected jobs.

o From repositories: You can select repositories where Veeam Plug-in backups are stored. When a
backup copy job runs, Veeam Backup & Replication will search for backup files created by Veeam
Plug-in in selected repositories.
[Optional] If you have added jobs from a repository and want to exclude from processing some of the
backup jobs on the selected repository, click Exclusions and select the jobs that you want to exclude.

2. Use the Remove button if you want to remove selected jobs or repositories from processing.

84 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 4. Define Backup Copy Target
At the Target step of the wizard, configure the target repository settings.

1. From the Backup repository list, select a backup repository in the target site where copied backups must
be stored. When you select a target backup repository, Veeam Backup & Replication automatically checks
how much free space is available on it. Make sure that you have enough free space to store copied
backups.

IMPORTANT

For Veeam Plug-in backup copy jobs, you cannot select a Veeam Cloud Connect repository as a
backup copy target.

2. [Optional] If the target repository contains a Veeam Plug-in backup that was excluded from the backup
copy job, and if you don't want to transfer duplicate data, you can use the mapping feature.
After you configure mapping, if some of backup files (.VAB) of the source backup are missing in the target
backup copy, these files are uploaded to the target backup copy.

NOTE

Veeam Plug-in backup copy jobs does not use WAN accelerators.

To map a backup copy job to the backup:

a. Click the Map backup link.

b. Point the backup copy job to the backup in the target backup repository. Backups in the target backup
repository can be easily identified by backup job names. To facilitate search, you can use the search
field at the bottom of the window.

IMPORTANT
• Used account must have access to Veeam backup repositories that you plan to use.
• Encryption must be disabled on the repository.

Otherwise, the repositories will not be listed as available. To learn how to configure access
permissions and encryption settings on repositories, see Access and Encryption Settings on
Repositories.

85 | Veeam Plug-ins for Enterprise Applications | User Guide

 3. You can specify the number of days after which the backup copy will be deleted from the repository. Note
that the countdown starts from the moment when source backup has been created.

86 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 5. Specify Advanced Settings
At the Target step of the wizard, click Advanced to configure compression, RPO and notifications settings.

• Compression and Deduplication

• RPO

• Notifications

Compression and Deduplication

At the Storage tab, define compression and deduplication settings.

By default, Veeam Backup & Replication performs deduplication before storing copied data on the target backup
repository. Deduplication provides a smaller size of the resulting backup file but may reduce the job
performance.

1. You can disable data deduplication. To do this, clear the Enable inline data deduplication check box.

2. From the Compression level list, choose a compression level to be used: Auto, None, Dedupe-friendly,
Optimal, High or Extreme. The recommended level of compression for backup copy jobs is Auto. In this
case, Veeam Backup & Replication uses compression settings of the copied backup files. For more
information, see Compression and Deduplication.

RPO Monitor
At the RPO Monitor tab, specify RPO warning settings.

87 | Veeam Plug-ins for Enterprise Applications | User Guide

Enable the Warn me if backup is not copied within check box and specify the time period in minutes, hours, or
days.

If the backup copy is not created within the specified time period, the backup copy job will finish with the
Warning status. The countdown starts from the moment when the required backup is finished and ready to be
copied.

Notifications
At the Notifications tab, to specify notification settings for the backup copy job:

1. At the Target step of the wizard, click Advanced.

2. Click the Notifications tab.

3. Select the Send SNMP notifications for this job check box if you want to receive SNMP traps when the job
completes successfully. SNMP traps will be sent if you specify global SNMP settings in Veeam Backup &
Replication and configure software on recipient's machine to receive SNMP traps. For more information,
see Specifying SNMP Settings.

4. Select the Send email notifications to the following recipients check box if you want to receive
notifications by email in case of job failure or success. In the field below, specify a recipient’s email
address. You can enter several addresses separated by a semicolon.

5. Veeam Backup & Replication sends a consolidated email notification once for the specified backup copy
interval. Even if the synchronization process is started several times within the interval, for example, due
to job retries, only one email notification will be sent.

6. Email notifications will be sent if you configure global email notification settings in Veeam Backup &
Replication. For more information, see Configuring Global Email Notification Settings.

88 | Veeam Plug-ins for Enterprise Applications | User Guide

 7. At the Send at field, specify the time when you want to receive notifications. Note that you will receive a
notification on a status of the job status once a day.

8. You can choose to use global notification settings or specify custom notification settings.

o To receive a typical notification for the job, select Use global notification settings. In this case, Veeam
Backup & Replication will apply to the job global email notification settings specified for the backup
server. For more information, see Configuring Global Email Notification Settings.

o To configure a custom notification for a job, select Use custom notification settings specified below.
You can specify the following notification settings:

i. In the Subject field, specify a notification subject. You can use the following variables in the
subject: %Time% (completion time), %JobName%, %JobResult%, %VmCount% (number of
machines in the job) and %Issues% (number of machines in the job that have been processed
with the Warning or Failed status).

ii. Select the Notify on success, Notify on warning and Notify on error check boxes to receive email
notification if data processing within the backup copy interval completes successfully, fails or
completes with a warning.

89 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 6. Define Backup Copy Schedule
At the Schedule step of the wizard, define a time span in which the backup copy job must not transport data
between source and target backup repositories. For more information, see Backup Copy Window.

To define a backup window for the backup copy job:

1. Select the During the following time periods only option.

2. In the schedule box, select the desired time area.

3. Use the Enable and Disable options to mark the selected area as allowed or prohibited for the backup copy
job.

90 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 7. Finish Working with the Wizard
At the Summary step of the wizard, complete the procedure of backup copy job configuration.

1. Review details of the backup copy job.

2. Select the Enable the job when I click Finish check box if you want to start the job right after you finish
working with the wizard.

3. Click Finish to close the wizard.

91 | Veeam Plug-ins for Enterprise Applications | User Guide

Converting Backup Copy to Backup
If you have imported Veeam Plug-in backup copies from another server, you can convert them into regular
backup files. When you convert a backup copy to a backup, Veeam Plug-in creates a backup job with the
converted backup. You can use this backup job to continue a backup chain and use the converted backup as a
restore point.

You can convert unbind Veeam Plug-in backups into regular Veeam Plug-in backup files in the following cases:

• If you have deleted a backup copy job which created the backup copy.

• If you have excluded a backup job from a backup copy job that used multiple backup jobs as a source.

• If you imported a Veeam Plug-in backup copy from another host.

NOTE

If you want to restore from a backup copy, you don't need to convert the backup copy to backup. For
details, see Restore from Backup Copy.

Converting Backup Copy to Backup for SAP HANA

To convert a backup copy to a primary backup, use the --promote-backup-copy-to-primary parameter as shown
below:

SapBackintConfigTool --promote-backup-copy-to-primary
Backup copies available for promotion to primary backup:
1. Backup Copy Job 1\saprhel01-localdomain SAP backint backup (Default Backup R
epository)
Select backup: 1
Promotion of backup copy to a primary backup will reconfigure the plug-in to us
e a different repository. Continue? (y/N): y

IMPORTANT

[For backups of scale-out clusters and servers with the customServerName option] To avoid failure of
conversion of backup copies, the cluster name must be the same as the name used in the backup copy.

92 | Veeam Plug-ins for Enterprise Applications | User Guide

Veeam Plug-in for Oracle RMAN
Veeam Backup & Replication offers two options to protect Oracle databases:

• Veeam Plug-in for Oracle RMAN

• Built-in backup and restore of Veeam Backup & Replication or Veeam Agents

You can use both or one of the options depending on your environment specifics and approach to handle Oracle
databases.

Veeam Plug-in for Oracle RMAN

Veeam Plug-in uses the backup and restore functionality of Oracle Recovery Manager (RMAN) and transfers
backups to Veeam backup repositories.

Use Veeam Plug-in to back up Oracle databases in the following cases:

• If you want the Oracle database administrator to fully control the backup and recovery processes.

• If you want to use existing Oracle RMAN scripts or external schedulers.

• If you use Oracle RAC.

• If you use ASM disks on a physical server.

Built-in Backup and Restore of Veeam Backup & Replication or

Veeam Agents
Veeam Backup & Replication (or Veeam Agent) performs image-level or file-level backup and restore of Oracle
servers. Use Veeam Backup & Replication or Veeam Agents to back up Oracle servers in the following cases:

• If you do not have Oracle database administrators.

• If you want to control backup and restore processes on the Veeam Backup & Replication side.

If you want to use Veeam Backup & Replication or Veeam Agents to protect Oracle servers, see Veeam Backup &
Replication User Guide.

93 | Veeam Plug-ins for Enterprise Applications | User Guide

How Veeam Plug-in for Oracle RMAN
Works
Veeam Plug-in functions as an agent between Oracle RMAN and Veeam backup repository. After you deploy
Veeam Plug-in on an Oracle server, you can perform all backup and restore operations in the Oracle RMAN
console. Veeam Plug-in compresses, deduplicates database backups and transfers them to a backup repository
connected to Veeam Backup & Replication.

When use Oracle RMAN integrated with Veeam Plug-in, the database backup is performed in the following way:

1. After you launch a database backup process in the Oracle RMAN console, RMAN launches Veeam Plug-in
services.

2. Veeam Plug-in connects to the Veeam Backup & Replication server and creates a backup job (if it hasn't
been created earlier).

3. Veeam Plug-in starts Veeam Data Movers on the Oracle server and on the Veeam backup repository.
Depending on the configured limit of RMAN channels, there will be multiple connections started in
parallel.

4. Veeam Data Movers transport the backup data to the backup repository.

94 | Veeam Plug-ins for Enterprise Applications | User Guide

Multiple Repositories Deployment
Veeam Plug-in allows you to add up to 4 backup repositories. The backup process can be run in multiple
channels. For each channel Veeam Plug-in creates a separate agent process.

95 | Veeam Plug-ins for Enterprise Applications | User Guide

Planning and Preparation
Before you start to use Veeam Plug-in for Oracle RMAN, read the environment planning recommendations and
make sure that your environment meets system requirements.

• System Requirements

• Required Permissions

• Used Ports

• Licensing

• Oracle Environment Planning

• Veeam Environment Planning

96 | Veeam Plug-ins for Enterprise Applications | User Guide

System Requirements
Before you start using Veeam Plug-in for Oracle RMAN, consider the following requirements.

Supported OSes
Veeam Plug-in for Oracle RMAN is supported for the following OSes:

• Microsoft Windows:

o Microsoft Windows Server 2008 R2

o Microsoft Windows Server 2012/2012 R2

o Microsoft Windows Server 2016

o Microsoft Windows Server 2019

• Linux:

o SUSE Linux Enterprise Server 11, 12, 15 (x86 and x86_64)

o Red Hat Enterprise Linux 6.4–8.x (x86 and x86_64)

o Oracle Linux 6.4–8.x (x86 and x86_64)

o CentOS 6.4–8.x (x86 and x86_64): For non-production environments, as it is not officially supported
by Oracle for their databases.

• Unix:

o Oracle Solaris 10, 11 (x86_64, SPARC)

o AIX 6.1, 7.1, 7.2

NOTE

[For Windows OS] The Veeam Plug-in for Oracle RMAN installation wizard also installs Microsoft .NET
Framework 4.6 if it does not detect this component on the machine during the product installation.

Oracle Database
Veeam Plug-in for Oracle RMAN supports Oracle Database 11gR2, 12c, 18c, 19c: Standard and Enterprise Edition
(Express Edition is not supported).

Supported Oracle RMAN features

Veeam Plug-in for Oracle RMAN will be registered as an SBT_TAPE device. All Oracle RMAN functionality that is
supported with the SBT_TAPE device type will work (including RAC, ASM and Container DBS).

Veeam Backup & Replication

Mind the following compatibility of Veeam Backup & Replication and Veeam Plug-in versions:

• Veeam Plug-in for Oracle RMAN 11 supports integration only with Veeam Backup & Replication version 11.

97 | Veeam Plug-ins for Enterprise Applications | User Guide

 • 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 10 (earlier than 10.0.1.4854) supports integration only with Veeam
Backup & Replication version 10.

• 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.

Note that if you want to use the latest functionality, you must update both Veeam Backup & Replication and
Veeam Plug-in to the latest version.

98 | Veeam Plug-ins for Enterprise Applications | User Guide

Required Permissions
Mind the required permissions for the following user accounts:

• OS User that Configures Veeam Plug-in

• User that Launches Backup/Restore in RMAN

• Veeam Backup Server User

OS User That Configures Veeam Plug-in

The account used for configuring Veeam Plug-in must have the following permissions.

• For Linux and Unix machines:

To configure Veeam Plug-in on a Linux or Unix machine, use an account which is a member of the OSDBA
(typically called as “dba”) group and has SYSDBA privileges.

• For Microsoft Windows machines:

To configure Veeam Plug-in on a Microsoft Windows machine, use an account which is a member of the
ORA_DBA group and has SYSDBA privileges.

User That Launches Backup/Restore in RMAN

The account used for starting Oracle RMAN backup and restore processes Veeam Plug-in must have the
following permissions.

• For Linux and Unix:

To launch RMAN backup or restore, you can use any user account that has required set of privileges for
backup operations on the Oracle side. Starting from Oracle Database 12c, Oracle recommends to use the
SYSBACKUP role. For details, see the Configuring Privilege and Role Authorization section of the Oracle
Database Security Guide.
During the backup process, Veeam Plug-in connects to the database to get DB properties. Thus,
Linux/Unix user that started the RMAN client must be a member of the OSDBA (typically called as “dba”)
group and has SYSDBA privileges.

IMPORTANT

If you use the CONNECT string with the channel allocation command in the Oracle RAC environment,
the plug-in manager process will be started by the owner of the Oracle listener, not by the user that
started the RMAN client. Thus, if the listener is owned by a cluster service user (grid) that is not a
member of the OSDBA group and doesn’t have SYSDBA privileges, the plug-in manager will not be
able to collect database properties and the backup will fail. As a workaround, you can add DBA
privileges to the grid user.

• For Microsoft Windows:

To launch RMAN backup or restore, you can use any user account that has required set of privileges for
backup operations on the Oracle side. Starting from Oracle Database 12c, Oracle recommends to use the
SYSBACKUP role. For details, see the Configuring Privilege and Role Authorization section of the Oracle
Database Security Guide.

99 | Veeam Plug-ins for Enterprise Applications | User Guide

 During the backup process, Veeam Plug-in connects to the database to get DB properties. Thus, the Oracle
Home user must be a member of the ORA_DBA group and the OS authentication must be enabled for this
user.

Veeam Backup Server User

The account which is used to authenticate against Veeam Backup & Replication must have access permissions on
required Veeam repository servers. To learn how to configure permissions on repositories, see Granting Access
to Repositories.

The Veeam Plug-in for Oracle RMAN uses Windows authentication methods of the Veeam Backup & Replication
server to establish a connection to this server and to the backup target. It is recommended to create one user
for each Veeam Plug-in server or RAC.

To work with backups created by Veeam Plug-in, you can use only the account used for creating the backup. If
you want to use another account, assign the Veeam Backup Administrator role or Veeam Backup Operator and
Veeam Restore Operator roles to the account. To learn how to assign Veeam Backup & Replication roles, see the
Roles and Users section of the Veeam Backup & Replication Guide.

100 | Veeam Plug-ins for Enterprise Applications | User Guide

Used Ports
To enable proper work of Veeam Plug-ins, make sure that the following ports are open.

Oracle Database Server

The following table describes network ports that must be opened to ensure proper communication of the Oracle
server and backup infrastructure components.

From To Protocol Port Notes

Default port used for communication with

Veeam the Veeam Backup & Replication server.
Backup & Note that data between Veeam Plug-ins
TCP 10006
Oracle Replication and backup repositories is transferred
server server directly, bypassing the Veeam Backup &
where Replication server.
Veeam
Plug-in is
installed Backup
Default range of ports used as data
repository
2500 to transmission channels. For every TCP
server or TCP
3300** connection that a backup process uses,
gateway
one port from this range is assigned.
server*

* For NFS share, SMB share repositories, and Dell EMC Data Domain, HPE StoreOnce deduplication storage appliances,
Veeam Backup & Replication uses an auxiliary backup infrastructure component — gateway server. For details, see the
Gateway Server section of the Veeam Backup & Replication User Guide.
** This range of ports applies to newly added backup infrastructure components. If you upgrade to Veeam Backup &
Replication 10.0 from earlier versions of the product, the range of ports from 2500 to 5000 applies to the already added
components.

Backup Repositories and Gateway Servers

Depending on the type of backup repositories that you use for Veeam Plug-in backups, the following ports must
be open to allow communication between backup infrastructure components.

From To Protocol Port Notes

Direct Attached Storage

Linux server
Veeam used as a
Port used as a control channel from the
Backup & backup
TCP 22 Veeam Plug-in server to the target Linux
Replication repository or
host.
server gateway
server

101 | Veeam Plug-ins for Enterprise Applications | User Guide

 From To Protocol Port Notes

Microsoft Ports used as a management channel from

TCP 135, 137 to the Veeam Plug-in server to the
Windows
server used UDP 139, 445 Repository/Gateway server. Also, the ports
as a backup are used to deploy Veeam components.
repository or
gateway Default ports used by the Veeam Installer
server TCP 6160, 6162
Service and Veeam Data Mover Service

Network Attached Storage

Gateway Default port used by SMB transport

TCP 445
server protocol.

(specified in
the SMB SMB server SMB/Netbios name resolution for SMB
share TCP 135, 137 to protocol (needed in some cases). For
repository UDP 139 details, see the Used Ports section of the
settings) Veeam Backup & Replication User Guide.

Gateway
server

(specified in TCP Standard NFS ports used as a transmission

the NFS NFS server 111, 2049 channel from the gateway server to the
UDP target NFS share.
share
repository
settings)

Dell EMC Data Domain

Port used to assign a random port for the

mountd service used by NFS and
TCP 111
DDBOOST. Mountd service port can be
statically assigned.
Veeam Dell EMC
Backup & Data Domain Main port used by NFS. To change the
Replication
port, you can use the ‘nfs set server-
server For more TCP 2049
port’ command. Note that the command
or information,
see Dell EMC requires SE mode.
Gateway
server Documents.
Main port used by NFS MOUNTD. To
change the port, you can use the 'nfs
TCP 2052
set mountd-port' command. Note
that the command requires SE mode.

HPE StoreOnce

102 | Veeam Plug-ins for Enterprise Applications | User Guide

 From To Protocol Port Notes

Veeam Default command port used for

9387
Backup & communication with HPE StoreOnce.
Replication
HPE
server TCP
StoreOnce
or Default data port used for communication
Gateway 9388
with HPE StoreOnce.
server

ExaGrid

Veeam
Backup & Default command port used for
ExaGrid TCP 22
Replication communication with ExaGrid.
server

Quantum
DXi

Veeam
Backup & Default command port used for
Quantum DXi TCP 22
Replication communication with Quantum DXi.
server

For detailed list of ports used by Veeam Backup & Replication server and backup repositories, see the Used Ports
section of the Veeam Backup & Replication User Guide.

103 | Veeam Plug-ins for Enterprise Applications | User Guide

Licensing
To use the Veeam Plug-in functionality, you must have a valid Veeam Backup & Replication license. The licenses
are installed and managed on the Veeam Backup & Replication instance that is connected to the Veeam Plug-in
server. If there are no available license instances or sockets, Veeam Plug-in backup jobs fail.

For details on Veeam licensing terminology and available packages, see:

• For the full list of license types, see Veeam Licensing Policy

• For the full list of license packages, see Pricing and Packaging

Licensed Objects
An Oracle server is assumed protected if it has been processed by a Veeam Plug-in backup job in the last 31
days.

If you are using any instance-based (Veeam Universal Licensing) license on your Veeam Backup & Replication,
you don't need to install any additional licenses.

A protected Oracle server consumes one instance unit from the license. Oracle servers processed by backup
copy jobs are not regarded as protected VMs, these types of jobs provide an additional protection level for VMs
that are already protected with Veeam Plug-in backup jobs.

A machine protected by both Veeam Plug-in and Veeam Backup & Replication will consume a license only once.
For example, you have an Oracle server that you back up using Veeam Plug-in. You also back up this server using
image-level backup functionality of Veeam Backup & Replication. In this case, only one license will be
consumed.

NOTE

[For Perpetual per-socket licenses] If you are using a legacy perpetual per-socket license, a license is
required for each hypervisor CPU socket occupied by protected Oracle servers.

A socket is consumed from the license only if the hypervisor where protected servers reside is added to the
Veeam Backup & Replication infrastructure. If the hypervisor is not added to the Veeam Backup &
Replication infrastructure, an instance unit will be consumed from the license. To learn how to add a
hypervisor to the Veeam Backup & Replication infrastructure, see the Virtualization Servers and Hosts
section of the Veeam Backup & Replication User Guide.

IMPORTANT

[For Oracle RAC] The license is required for all cluster nodes, even if Veeam Plug-in is installed only on one
of the nodes.

104 | Veeam Plug-ins for Enterprise Applications | User Guide

Supported License Types
You can use Veeam Plug-ins with the following license types and packages.

• For Veeam Universal Licensing:

You can use Veeam Plug-ins with all license packages (Veeam Backup Essentials, Veeam Backup &
Replication, Veeam Availability Suite).
Note that if you use the Rental license type, the license package must be the Enterprise Plus edition.

• For Perpetual Socket license:

You can use Veeam Plug-in with the Enterprise Plus edition license.

Installing and Managing Licenses

To learn how to install a license and how to monitor licensed objects, see the Licensing section in the Veeam
Backup & Replication User Guide.

105 | Veeam Plug-ins for Enterprise Applications | User Guide

Oracle Environment Planning
Before you deploy Veeam Plug-in, mind the following requirements and limitations.

Deployment
[For Linux OS and Unix] To install Veeam Plug-in, the /opt/veeam directory must be writable.

Oracle Temp Tablespace

Veeam performs SQL queries on the Oracle database to collect statistical information about the RMAN job
process. As with any other SQL query, Oracle can decide based on RAM and other resource availability to use
Oracle Temp Tablespace for these queries. Make sure you configure the Temp Tablespace resources to avoid
shortage of temporary tablespace.

Scheduling
You can schedule backup processes with all Oracle RMAN relevant scheduling options like Cron, Windows Task
Scheduler, UC4 and TWS.

Also, you can schedule and run existing Oracle RMAN backup scripts within image-level or file-level backup job
of Veeam Backup & Replication or Veeam Agent. For details, see Pre-Freeze and Post-Thaw Scripts.

Oracle RAC
• It is recommended to install Veeam Plug-in on each RAC server that is responsible for the backup
operations. If the plug-in is not installed on all nodes, the backup may fail when RMAN selects another
node.

• Veeam Plug-in supports parallel execution of all operations supported by Oracle RMAN: backup, restore,
crosscheck, remove. This applies to execution of listed commands on one or multiple databases residing
on one or multiple RAC nodes.

• If you perform restoring with different settings of RAC from a Veeam Plug-in backup using Veeam
Explorer for Oracle, it will not be restored as a cluster database. It will be restored as a standalone
database.

Backup File Naming

The plug-in configuration wizard reads out the repositoryID parameter from the plug-in configuration file
(/opt/veeam/VeeamPluginforOracleRMAN/veeam_config.xml or
%PROGRAMFILES%\Veeam\VeeamPluginforOracleRMAN\veeam_config.xml for Windows). In the
veeam_config.xml file, the repository ID is stored in the following format: repositoryID=“xxxxxxxx-
xxxx-xxxx-xxxx-xxxxxxxxxxxx”.

106 | Veeam Plug-ins for Enterprise Applications | User Guide

To name backup files, Veeam Plug-in uses the following schema by default:

CONFIGURE CHANNEL DEVICE TYPE sbt PARMS 'SBT_LIBRARY=/opt/veeam/VeeamPluginforO

racleRMAN/libOracleRMANPlugin.so’ FORMAT 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/
RMAN_%I_%d_%T_%U.vab’;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F_RMAN_AU
TOBACKUP.vab’;

• If you select multiple Veeam backup repositories and disable RMAN copy processing:
Backup files will be read by default from the first selected repository. Same naming rules apply as in the
single repository scenario.

• If you select multiple Veeam backup repositories and enable RMAN copy processing, you must use the
repository ID with the “/” sign as a prefix for the backup file names (see the example above). This allows
RMAN to directly access the requested backup file on one of the copy extents.

NOTE

[For Linux, Unix, Windows] In a backup file name, you cannot use symbols reserved by Microsoft Windows:
"<" , ">", ":", "/", "\", "|", "?", "*". To learn more about file naming conventions, see Microsoft Docs.

Autobackup File Naming

If you perform the restore with different name and settings using Veeam Explorers for Oracle, you must enable
Controlfile Autobackup. If you use the Controlfile Autobackup option, the Veeam Plug-in configuration wizard
creates the following RMAN configuration entry:

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F_RMAN_AU

TOBACKUP.vab’;

If you enable the control file autobackup after configuring Veeam Plug-in, you can start the configuration
wizard again. The control file backup naming option will be set to default.

Parallel Processing
Veeam Plug-in supports parallel backup processing for up to 4 backup repositories or scale-out backup
repositories. In the plug-in configuration wizard, if you select more than one repository, the parallelism
functionality will be enabled automatically.

Note that your Oracle Enterprise Edition must be able to use RMAN parallel processing.

TIP

If you want to recover the Veeam Plug-in job folder to a specific point in time state, you can use Storage
Replication (plus import) or the File Backup to Tape job of Veeam Backup & Replication.

107 | Veeam Plug-ins for Enterprise Applications | User Guide

Additional Files to Back up
Oracle Home
• It is recommended to back up the Oracle home folder in addition to RMAN backups. You can back it up
with Veeam Backup & Replication or Veeam Agents.

• If the Oracle home folder is on a shared disk, you can use the file-level backup functionality of Veeam
Agent for Linux. Alternatively, you can copy the Oracle home folder to a non-shared disk before the
backup.

Oracle Recovery Catalog

You can back up the Oracle Recovery Catalog with Veeam Plug-in on the Recovery Catalog server according to
the Oracle procedures. For details, see the Managing a Recovery Catalog section of the Database Backup and
Recovery User's Guide.

Oracle Server for Disaster Recovery

To create an image-level backup of the Oracle server, you can use the image-level backup functionality of
Veeam Backup & Replication or Veeam Agents.

Veeam Plug-in for RMAN Configuration

You can back up the Veeam Plug-in configuration file. The file is located in the following directory:

• [Linux or Unix]: /opt/veeam/VeeamPluginforOracleRMAN/veeam_config.xml

• [Windows]: %PROGRAMFILES%\Veeam\VeeamPluginforOracleRMAN\veeam_config.xml

Multiple Oracle Versions on One Server

Multiple Oracle Database versions deployed on the same machine are supported only for Linux or Unix based
operating systems.

Disabling Veeam Explorer Processing

You can disable Veeam Explorer based restore for specific Oracle servers. To disable the restore on the Veeam
Explorer for Oracle side, do the following:

• [Linux or Unix] On the Oracle server, log in as a user with the Oracle Administrator rights and create an
empty file in the following directory: /etc/veeam/disablerestore

• [Windows] On the Oracle server, create an empty file in the following directory:
%ProgramData%\Veeam\disablerestore

Oracle Data Guard

Since version 11, Veeam Plug-in for Oracle RMAN has an official support of Oracle Data Guard.

108 | Veeam Plug-ins for Enterprise Applications | User Guide

Veeam Environment Planning
Before you deploy Veeam Plug-in, keep in mind the following requirements and limitations.

• RMAN Channels and Resource Consumption

• Veeam Backup Job Name

• Hosting Environments

RMAN Channels and Resource Consumption

Any parallel channel started by RMAN will use one Veeam backup repository task slot. By design, Oracle
Standard Edition can work with one channel. Oracle Enterprise Edition has the option to use multiple channels
and you can configure them in the Veeam Plug-in configuration wizard or at the ALLOCATE CHANNEL definition
in RMAN scripts. It is recommended to carefully plan repository task slots, so that Oracle RMAN can work with
multiple channels in parallel when configured.

The following hardware resources are recommended based on tests on Skylake processors:

• Oracle server: 1 CPU core and 200 MB of RAM per currently used channel. Note that resource
consumption on the Oracle server depends on hardware and Oracle settings.

• Backup repository server: 1 CPU core and 1 GB of RAM per 5 currently used channels.
These resources are recommended only if you use a dedicated backup repository for Veeam Plug-in
backups. If you use the same backup repository for Veeam Plug-in backups and VM backups created by
Veeam Backup & Replication or Veeam Agents, consider adding the mentioned above hardware resources
based on usual load on your backup repository. For details on hardware requirements for a backup
repository, see the System Requirements section of the Veeam Backup & Replication User Guide.
We recommend to contact your Veeam system engineer to optimize the channel settings and resource
allocation. Also, mind the following:

o It is recommended to use a separate backup repository for Veeam Plug-in backups.

o The control file does not use a repository task slot and will be processed even if there are no free task
slots.

• Veeam Backup & Replication server: during manual metadata operations such as import of backup files,
the Veeam Backup & Replication server needs additional 15 GB of RAM per 1 million files located in the
same backup job folder.

Veeam Backup Job Name

• On the Veeam Backup & Replication server, the backup job name will be created automatically based on
the server or cluster name and selected repository.

• For environments that use Oracle RMAN copy processing, one job per repository is created.

Backup Files
• A .VAB file stores compressed and deduplicated copy of an Oracle database. Veeam Plug-in creates VAB
files for both full and incremental backups.

109 | Veeam Plug-ins for Enterprise Applications | User Guide

 • A .VASM file stores metadata that contain information about the backup. A .VASM file is created for each
.VAB file. The .VASM files are used by Veeam Backup & Replication to get data about Veeam Plug-in
backups.

• A .VACM file stores metadata of a backup job object.

Hosting Environments
By default, Veeam Plug-in uses the Oracle server hostname to create a Veeam Backup & Replication job object
and backup folder. To be able to distinguish individual servers, it is recommended to set the following entry
within the Veeam configuration XML file: <PluginParameters
customServerName="hostname.domain.tld" />

• [Linux or Unix]: /opt/veeam/VeeamPluginforOracleRMAN/veeam_config.xml

• [Windows]: %PROGRAMFILES%\Veeam\VeeamPluginforOracleRMAN\veeam_config.xml

If your servers that have the same hostname in multiple environments, you must add the following entries in the
plug-in configuration file:

<PluginParameters useFQDNInServerName="true" />

IMPORTANT

For security reasons, it is recommended to use separate repositories for different customers and limit the
Veeam Repository Authentication to the specific customer.

110 | Veeam Plug-ins for Enterprise Applications | User Guide

Veeam Backup Repositories
Veeam Plug-ins store backup files in repositories added to the Veeam Backup & Replication infrastructure. In
this section, you can find the list of supported backup repositories and limitations for Veeam Plug-in backups.

Supported Backup Repositories

Veeam Plug-in for Oracle RMAN supports integration with the following types of repositories added to the
Veeam Backup & Replication infrastructure:

• Windows Server

• Linux Server

• CIFS (SMB) Share

• Dell EMC Data Domain Boost

• Quantum DXi

• ExaGrid

• HPE StoreOnce. If you plan to use HPE StoreOnce as a backup repository for Veeam Plug-in for Oracle
RMAN, the total number of stored files (data and metadata) must not exceed 1,000,000 per storage
system.

• NFS File Share

You can also use scale-out backup repositories that contain supported repository types.

Backup Repositories Limitations

• For Veeam Plug-in backups, the warning which indicates that free space on a storage device has reached a
specified threshold is configured in the veeam_config.xml file of Veeam Plug-in. The warning settings
in the Veeam Backup & Replication console does not affect this setting.
To configure the warning settings, add the following parameter in the veeam_config.xml file.

<PluginParameters repositoryFreeSpacePercentWarning="10" />

• The plug-in configuration wizard will not show repositories where the Encrypt backups stored in this
repository option is enabled. To learn how to disable the encryption option, see Access and Encryption
Settings on Repositories.
If you want to use the same backup target with the repository-based encryption and Veeam Plug-ins,
create a second repository in the subfolder for Veeam Plug-in backups.

• If you use Veeam Plug-in version 9.5 Update 4, Veeam backup copy jobs are not able to process and copy
the backups created by the plug-in.

• Veeam extract utility cannot extract Veeam Plug-in backup files. By design of Oracle RMAN, these files
cannot be imported “as files” to RMAN as they contain additional metadata bound to the used SBT device.

111 | Veeam Plug-ins for Enterprise Applications | User Guide

Veeam Scale-Out Backup Repositories
If you want to store Veeam Plug-in backups in the scale-out backup repositories, mind the following:

• If you want to migrate backup repositories to a scale-out backup repository and Veeam Plug-in backups
are present on the repository, you must do the following:

a. Transfer the folders that include backups to an existing scale-out backup repository extent.

b. Rescan the scale-out backup repository.

c. Set the scale-out backup repository as a target in the Veeam Plug-in settings.

d. Rescan the repository that you want to add.

e. Migrate the repository to the scale-out backup repository.

• For Veeam Plug-in backups and backup copies, the Performance policy of a scale-out repository functions
a little differently:

a. Veeam Backup & Replication checks if there are extents without warning on free space insufficiency. If
all extents have the warning, Veeam Backup & Replication uses an extent with the largest amount of
free space that has a free task slot.

b. If there are extents without the warning, Veeam Backup & Replication checks if there are incremental
extents with free task slots. If there are no incremental extents with free task slots, Veeam Backup &
Replication uses a full extent with least amount of used task slots.

c. If there are incremental extents with free task slots, Veeam Backup & Replication will send backup
files to an incremental extent with least amount of used task slots. If the amount of used tasks is the
same, an extent with the most amount of free space.
To learn more about file placement policies of scale-out repositories, see Backup File Placement section of
the Veeam Backup & Replication guide.

• If a scale-out repository is configured in the Data locality policy, repository extents will be selected
according to the amount of free space for each Oracle RMAN connection. If there are two extents with one
slot on each extent, the backup will be launched on two streams (one on each extent).

Capacity Tier
You can configure Veeam Backup & Replication to transfer Veeam Plug-in backup files to a capacity tier. Both
policies (Move policy, Copy policy) are supported for Veeam Plug-in backups with the following limitations:

• For Veeam Plug-in backup files, capacity tier does not verify whether data that is being moved is unique
and has not been offloaded earlier. Thus, it is highly recommended to check the pricing plans of your
cloud storage provider to avoid additional costs for offloading and downloading backup data.

• Capacity tier does not track dependencies of full and incremental Veeam Plug-in backup files. Thus, mind
the following:

o [For the Move policy] When backup files are transferred to the capacity tier, Veeam Backup &
Replication takes into account only the creation time of backup files. Make sure that the
operational restore window is not longer than the whole backup chain cycle period. Otherwise, you
may encounter the scenario when full backup files are transferred to the capacity tier and their
increment backup files still remain in the performance tier.

o The capacity tier immutability expiration date does not have the additional block generation period.
The immutability expiration date is based only on the number of days specified in settings of the
object storage backup repository.

112 | Veeam Plug-ins for Enterprise Applications | User Guide

 • If a scale-out repository is down, you cannot restore from the Veeam Plug-in backup files stored on the
capacity tier. In this case, you can only import the backup files to Veeam Backup & Replication manually
and then perform data recovery operations.

• If you use a capacity tier that has been created in Veeam Backup & Replication version 10, you cannot
transfer Veeam Plug-in backup files to a capacity tier. However, if you want to transfer them manually,
do the following:

o If the backup files are created by Veeam Plug-in version 10, upgrade the metadata of backup files
as described in Upgrading Metadata Files to New Format.

o Run the Set-VBRScaleOutBackupRepository PowerShell command with the -

EnablePluginBackupOffload parameter to offload backup files to the capacity tier.

113 | Veeam Plug-ins for Enterprise Applications | User Guide

Access and Encryption Settings on Repositories
When you configure Veeam Plug-in, you specify an account that must be used to connect to the Veeam Backup
& Replication server. To be able to store backups on a backup repository, the specified account must have access
permissions on the target backup repository.

To grant access permissions, do the following:

1. In Veeam Backup & Replication, open the Backup Infrastructure view.

2. In the inventory pane, click the Backup Repositories node or the Scale-out Repositories node.

3. In the working area, select the necessary backup repository, click Set Access Permissions on the ribbon or
right-click the backup repository and select Access permissions.

4. In the Access Permissions window, specify to whom you want to grant access permissions on this backup
repository:

o Allow to everyone — select this option if you want to grant repository access to any user. This option
is equal to granting access rights to the Everyone group in Microsoft Windows (anonymous users are
excluded). For security reasons, the option is not recommended for production environments.

o Allow to the following accounts or groups only — select this option if you want only specific users to
be able to store backups on this repository. Click Add to add the necessary users and groups to the
list.

114 | Veeam Plug-ins for Enterprise Applications | User Guide

 5. Veeam Plug-ins cannot send backups or backup copies to a repository where encryption is enabled. Thus,
unselect the Encrypt backups stored in this repository check box.

115 | Veeam Plug-ins for Enterprise Applications | User Guide

Deployment and Configuration
Veeam Plug-in for Oracle RMAN is a feature of Veeam Backup & Replication. This guide gives instructions on
how to deploy Veeam Plug-in assuming that you already have deployed Veeam Backup & Replication and
configured a backup repository. To learn how to deploy Veeam Backup & Replication, see the Veeam Backup &
Replication User Guide for your platform.

To be able to use Veeam Plug-in for Oracle RMAN, you must install the plug-in on the Oracle server and
configure the plug-in settings:

• Installing Veeam Plug-in for Oracle RMAN

• Configuring Veeam Plug-in for Oracle RMAN

116 | Veeam Plug-ins for Enterprise Applications | User Guide

Installing Veeam Plug-in for Oracle RMAN
See one of the following guides depending on which OS is installed on the target machine.

• Installing Veeam Plug-in on Linux machines

• Installing Veeam Plug-in on Solaris machines

• Installing Veeam Plug-in on Windows machines

• Installing Veeam Plug-in on IBM AIX machine

Installing Plug-in on Linux

Veeam Plug-in for Oracle RMAN is an additional component of Veeam Backup & Replication, and the installation
package of the plug-in is included in the Veeam Backup & Replication installation ISO file.

Veeam Plug-in for Oracle RMAN must be installed on a machine where the target Oracle Database is deployed.

NOTE

To install Veeam Plug-in, the /opt/veeam directory must be writable.

To install Veeam Plug-in on a Linux machine, perform the following steps.

1. Mount the Veeam Backup & Replication installation disk.

If you deploy Veeam backup infrastructure for the first time, you can download Veeam Backup &
Replication at: https://www.veeam.com/backup-replication-vcp-download.html.

2. In the installation disk folder, go to Plugins\Oracle RMAN\Linux.

3. You can install the plug-in using the RPM package or .TAR.GZ bundle. Do one of the following, depending
on the type of package suitable for your OS. Note that operations in the terminal of the Linux machine
require root privileges.

o To install from the RPM package:

i. Upload the VeeamPluginforOracleRMAN-X.X.X.XXXX.x86_64.rpm package to the Oracle

server. If you need the 32-bit version, choose the i386 package.

ii. To install Veeam Plug-in, run the following command:

rpm -i VeeamPluginforOracleRMAN-X.X.X.XXXX.x86_64.rpm

o To install from the TAR.GZ bundle:

i. Upload the VeeamPluginforOracleRMAN.tar.gz file to the Oracle server.

ii. Create the /opt/veeam directory.

mkdir /opt/veeam

117 | Veeam Plug-ins for Enterprise Applications | User Guide

 iii. Unpack the bundle to the /opt/veeam directory:

tar -xzvf -i VeeamPluginforOracleRMAN.tar.gz -C /opt/veeam

Installing Plug-in on Microsoft Windows

You can install Veeam Plug-in for Oracle RMAN on Windows machines using a wizard or in an unattended mode.
For instructions, see:

• Installing Veeam Plug-in on Windows machines

• Installing Veeam Plug-in in an unattended mode

NOTE

When you launch the installation file, it also installs Microsoft .NET Framework 4.6 if it does not detect this
component on the machine during the product installation. In some cases, installation of .NET Framework
requires a reboot of the machine. This can happen, for example, if you have an earlier version of .NET
Framework installed on the machine and during the installation process it is used by third-party software.

Installing Plug-in on Windows Machine

Veeam Plug-in for Oracle RMAN is an additional component of Veeam Backup & Replication, and the installation
package of the plug-in is included in the Veeam Backup & Replication installation ISO file.

To install Veeam Plug-in for Oracle RMAN on a Windows machine, do the following:

1. Mount the Veeam Backup & Replication installation disk.

If you deploy Veeam backup infrastructure for the first time, you can download Veeam Backup &
Replication at: https://www.veeam.com/backup-replication-vcp-download.html.

2. In the installation disk folder go to Plugins\Oracle RMAN\Windows.

3. To launch the installation wizard, run the VeeamPluginforOracleRMAN.exe file.

118 | Veeam Plug-ins for Enterprise Applications | User Guide

 4. At the welcome screen of the installation wizard, click Next.

5. At the License Agreement step of the wizard, accept the terms of license agreements and click Next.

119 | Veeam Plug-ins for Enterprise Applications | User Guide

 6. At the Custom Setup step of the wizard, specify the installation path for Veeam Plug-in and click Next.

7. At the Ready to Install the Program step of the wizard, click Install.

Installing the Plug-in in Unattended Mode

You can install Veeam Plug-in for Oracle RMAN on a Windows machine in the unattended mode using the
command line. Go to folder where the VeeamPluginforOracleRMAN.exe file resides and run the following
command:

<path_to_exe>\VeeamPluginforOracleRMAN.exe /silent /accepteula /acceptthirdpart

ylicenses

120 | Veeam Plug-ins for Enterprise Applications | User Guide

where <path_to_exe> is a path to the Veeam Plug-in for Oracle RMAN installation file.

Parameter Description

/silent Enables the silent mode.

/accepteula Accepts EULA terms.

/acceptthirdpartylicenses Accepts terms of third-party licenses.

Veeam Plug-in for Oracle RMAN uses the following codes to report about the installation results:

• 1000 — Veeam Plug-in for Oracle RMAN has been successfully installed.

• 1001 — prerequisite components required for Veeam Plug-in for Oracle RMAN have been installed on the
machine. Veeam Plug-in for Oracle RMAN has not been installed. The machine needs to be rebooted.

• 1002 — Veeam Plug-in for Oracle RMAN installation has failed.

• 1101 — Veeam Plug-in for Oracle RMAN has been installed. The machine needs to be rebooted.

Installing Plug-in on Oracle Solaris

Veeam Plug-in for Oracle RMAN is an additional component of Veeam Backup & Replication, and the installation
package of the plug-in is included in the Veeam Backup & Replication installation ISO file.

Veeam Plug-in for Oracle RMAN must be installed on a machine where the target Oracle Database is deployed.

NOTE

To install Veeam Plug-in, the /opt/veeam directory must be writable.

To install Veeam Plug-in for Oracle RMAN on a Solaris machine, do the following:

1. Mount the Veeam Backup & Replication installation disk.

If you deploy Veeam Backup & Replication infrastructure for the first time, you can download Veeam
Backup & Replication at: https://www.veeam.com/backup-replication-vcp-download.html.

2. In the installation disk folder, go to Plugins\Oracle RMAN\Solaris. Select your system: i386 or
SPARC.

3. Copy the Veeam Plug-in installation package (VeeamPluginforOracleRMAN-XX.X.X.XXXX-1.SPARC.pkg) to

Oracle Solaris server.

4. Install the plug-in from package with root privileges. Make sure the root user has privileges to add the
PKG file.

pkgadd -d /tmp/VeeamPluginforOracleRMAN-X.X.X.XXXX.SPARC.pkg

5. Once Veeam Plug-in is installed, you can configure the plug-in settings. For details, see Configuring Plug-
in on Linux and Unix Machines.

121 | Veeam Plug-ins for Enterprise Applications | User Guide

Installing Plug-in on IBM AIX
Veeam Plug-in for Oracle RMAN is an additional component of Veeam Backup & Replication, and the installation
package of the plug-in is included in the Veeam Backup & Replication installation ISO file.

Veeam Plug-in for Oracle RMAN must be installed on a machine where the target Oracle Database is deployed.

NOTE

To install Veeam Plug-in, the /opt/veeam directory must be writable.

To install Veeam Plug-in for Oracle RMAN on an IBM AIX machine, do the following:

1. Mount the Veeam Backup & Replication installation disk.

If you deploy Veeam backup infrastructure for the first time, you can download Veeam Backup &
Replication at: https://www.veeam.com/backup-replication-vcp-download.html.

2. In the installation disk folder, go to Plugins\Oracle RMAN\AIX\ppc64.

3. Copy the Veeam Plug-in installation package (VeeamPluginforOracleRMAN-XX.X.X.XXX-1.aix6.1.ppc.rpm)

to the AIX server where the target Oracle database is deployed.

4. Install the plug-in from package with root privileges. Make sure the root user has privileges to add the
PKG file.

rpm -i VeeamPluginforOracleRMAN-X.X.X.XXX-1.aix6.1.ppc.rpm

5. Once Veeam Plug-in is installed, you can configure the plug-in settings. For details, see Configuring Plug-
in on Linux and Unix Machines.

122 | Veeam Plug-ins for Enterprise Applications | User Guide

Configuring Veeam Plug-in for Oracle RMAN
To use Veeam Plug-in you must configure the connection between the Oracle server, Veeam Backup &
Replication server and backup repositories where backup files will be stored.

• Configuring Veeam Plug-in for Oracle RMAN on Linux or Unix Machines

• Configuring Veeam Plug-in for Oracle RMAN on Windows Machines

Configuring Plug-in on Linux or Unix

To configure Veeam Plug-in, you can use OracleRMANConfigTool. The tool configures Oracle RMAN integration
settings and creates the veeam_config.xml file which is stored in the installation folder of the plug-in:
/opt/veeam/VeeamPluginforOracleRMAN.

Note that the Veeam Plug-in configuration tool changes the settings of Oracle RMAN. All original settings of
Oracle RMAN are saved in the /opt/veeam/VeeamPluginforOracleRMAN/RMANParameters.xml file.

To configure Veeam Plug-in for Oracle RMAN, do the following:

1. Log in to the Oracle server with an account which is a member of the DBA group.

2. Launch the configuration wizard:

OracleRMANConfigTool --wizard

3. Specify the DNS name or IP address of the Veeam Backup & Replication server.

Enter backup server name or IP address: 172.24.164.68

4. Specify the port which will be used to communicate with the Veeam Backup & Replication server. Default
port: 10006.

Enter backup server port number: 10006

5. Specify credentials to authenticate against the Veeam Backup & Replication server. The account must have
the local Administrator permissions on the Veeam Backup & Replication server.
Also, note that the account must have access permissions on the required backup repository. To learn how
to configure access permissions and encryption settings on repositories, see Access and Encryption
Settings on Repositories.

Enter username: serv17\administrator

Enter password for serv17\administrator:

123 | Veeam Plug-ins for Enterprise Applications | User Guide

 IMPORTANT

You can work with backups created by Veeam Plug-in only with the account used for creating the
backups. If you want to use another account, assign the Veeam Backup Administrator role or Veeam
Backup Operator and Veeam Restore Operator roles to the account.
To learn how to assign Veeam Backup & Replication roles, see the Roles and Users section of the
Veeam Backup & Replication Guide.

6. Select the backup repository where you want to store the backups. In the wizard dialog, enter the number
of the repository from the list of available repositories. If you want to add several repositories, enter the
required numbers separated by blank spaces.
If you want to use the Oracle RMAN Backup Duplexing functionality, you can select up to four repositories.
The copies of backups will be sent to all selected repositories. Note that Oracle Database Standard Edition
does not allow using more than one RMAN channel. Thus, if you use Standard Edition, you can select only
one repository.

Available repositories are:

1. serv10_repo
2. serv02_repo
Specify up to 4 Veeam repositories to use as target using whitespace as a
separator: 2

IMPORTANT
• The account must have access to backup repositories that you plan to use.
• Encryption must be disabled on the repository.

Otherwise, the repositories will not be listed as available. To learn how to configure access
permissions and encryption settings on repositories, see Access and Encryption Settings on
Repositories.

7. Specify the number of parallel data streams for each backup repository. Note that Oracle Database
Standard Edition does not allow using more than one RMAN channel. Thus, if you use Standard Edition,
you can select only one data stream.

Enter the number of data streams (From 1 to 254) to run in parallel for ea
ch repository (RMAN DEVICE PARALLELISM value).
Channel count per device: 4

8. If you want to enable Veeam compression of backup files, type y. For details, see the Data Compression
and Deduplication section of Veeam Backup & Replication User Guide.

Do you want to use Veeam compression (Y/n):y

9. At the last step of the plug-in wizard, you can export configuration files (the Veeam Plug-in configuration
file and RMAN configuration file). You can import these configuration files to other servers to apply the
same settings.

124 | Veeam Plug-ins for Enterprise Applications | User Guide

 Save configuration?
1. Apply configuration to the Oracle environment
2. Export configuration into a file for manual setup
3. Cancel without saving
Enter:1
*** Database instance ORCL is configured ***

NOTE

When you export the configuration files, Veeam Plug-in automatically enables Oracle's Controlfile
Autobackup feature. This feature is required for restoring with different settings using Veeam
Explorer for Oracle.

TIP

It is recommended to save the configuration files, so that you can use it as a reference. For example,
if you are planning to manually allocate channels for backup and restore operations, you will need
the repository UUID. The RMAN configuration file (rman_config.txt) contains an example for
channel allocation definition for the target repository. You can use this statement in your
backup/restore scripts.

Configuration Tool Commands

Apart from running a configuration wizard, you can use the OracleRMANConfigTool tool to change a specific
parameter in the veeam_config.xml file or enable/disable Veeam Plug-in features.

See the list of available commands for OracleRMANConfigTool:

Command Description

--help Shows the list of parameters of the plug-in configuration tool.

--show-config Shows configuration parameters.

Starts the wizard to configure the plug-in settings. This wizard edits the
--wizard veeam_config.xml file or creates a new one if the configuration file was
removed from the /opt/veeam/VeeamPluginforOracleRMAN directory.

--set-credentials Specifies credentials to connect to the Veeam backup server.

<"serv\username">
<"password">

--set-host <hostname> Specifies the host of the Veeam backup server.

--set-port <port_number> Specifies the host to connect to the Veeam Backup & Replication server.

125 | Veeam Plug-ins for Enterprise Applications | User Guide

 Command Description

Launches a wizard to select a backup repository. A backup repository is

--set-repositories selected from repositories which are available in the connected Veeam Backup
& Replication instance.

--set-parallelism Configures RMAN parallelism settings.

<number_of_channels>

--compression <y/n> Enables/disables Veeam proprietary feature which compresses backup files.

--map-backup Maps the imported backups.

--set-force-delete Configures the auto-deletion of backup files after specified days.

Enables restore from backup copy. Note that if you enable restore from
--configure-restore-from-
backup copy, you cannot back up databases with Veeam Plug-in. To revert
copy
changes, you must disable restore from backup copy.

--promote-backup-copy- Maps the imported backup copy to a regular Veeam Plug-in backup chain.
to-primary

Example:

To specify credentials that will be used to log in to the Veeam Backup & Replication server, use the plug-in
configuration tool with the following command.

OracleRMANConfigTool --set-credentials "serv04\joelle" "password"

Configuring Plug-in on Windows

To configure backup and restore settings, use the Veeam Plug-in for Oracle RMAN configuration wizard. The
wizard configures Oracle RMAN settings and creates the veeam_config.xml file which is stored in the
%PROGRAMFILES%\Veeam\VeeamPluginforOracleRMAN folder.

Note that configuration wizard of Veeam Plug-in for Oracle RMAN changes the settings of Oracle RMAN. All
original settings of Oracle RMAN are saved in the
%PROGRAMFILES%\Veeam\VeeamPluginforOracleRMAN\RMANParameters.xml file.

To configure Veeam Plug-in, do the following:

1. On the Oracle server, click launch the Veeam RMAN Configuration Wizard
(%PROGRAMFILES%\Veeam\VeeamPluginforOracleRMAN\Veeam.Backup.RMAN.Configuration.
exe).

126 | Veeam Plug-ins for Enterprise Applications | User Guide

 2. At the Backup Server step of the wizard, specify the DNS name of the Veeam Backup & Replication server
and credentials that will be used to connect to the server. The specified account must have the local
Administrator permissions on the Veeam Backup & Replication server.

3. At the Backup Repository step of the wizard:

a. Click Add and select the required repository. For Oracle Database Standard Edition, you can select
only one repository. If you want to use the Oracle RMAN Backup Duplexing functionality, you can
select up to four repositories. The copies of backups will be sent to all selected repositories.
You must allow access to Veeam backup repositories that you plan to use. Also, the encryption on the
repository must be disabled. To learn how to configure access and encryption on repositories, see
Access and Encryption Settings on Repositories.

b. If you want to use another repository, select the repository from the list and click Remove. Then, you
can add another repository

c. At the Channels per repository field, specify the number of allowed parallel data streams for each
repository.

d. If you want to enable Veeam Plug-in compression, select the Enable backup compression by the plug-
in check box.
Note that if you use Veeam Plug-in compression in combination with Oracle RMAN integrated
compression (BACKUP AS COMPRESSED commands), it can slow down processing.

127 | Veeam Plug-ins for Enterprise Applications | User Guide

 e. Click Next.

IMPORTANT

You can work with backups created by Veeam Plug-in only with the account used for creating the
backups. If you want to use another account, assign the Veeam Backup Administrator role or Veeam
Backup Operator and Veeam Restore Operator roles to the account.
To learn how to assign Veeam Backup & Replication roles, see the Roles and Users section of the
Veeam Backup & Replication Guide.

4. At the Summary step of the wizard, you can export the plug-in and Oracle RMAN configuration files. You
can use the configuration files to apply the plug-in settings on other servers.

a. To export the veeam_config.xml file click Export and select Veeam Config.

128 | Veeam Plug-ins for Enterprise Applications | User Guide

 b. Click Finish.

NOTE

When you export the configuration files, Veeam Plug-in automatically enables Oracle's Controlfile
Autobackup feature. This feature is required for restoring with different settings using Veeam
Explorer for Oracle.

TIP

It is recommended to save the configuration files, so that you can use it as a reference. For example,
if you are planning to manually allocate channels for backup and restore operations, you will need
the repository UUID. The RMAN configuration file (rman_config.txt) contains an example for
channel allocation definition for the target repository. You can use this statement in your
backup/restore scripts.

Configuration Tool Commands

Apart from running a configuration wizard, you can use the OracleRMANConfigTool.exe tool to change a specific
parameter in the veeam_config.xml file or enable/disable Veeam Plug-in features.

To run a specific command, do the following:

1. On the Oracle server, go to %PROGRAMFILES%\Veeam\VeeamPluginforOracleRMAN.

129 | Veeam Plug-ins for Enterprise Applications | User Guide

 2. Run the required OracleRMANConfigTool.exe command from the table below.
For example, to specify credentials that will be used to log in to the Veeam Backup & Replication server,
use the plug-in configuration tool with the following command:

OracleRMANConfigTool.exe --set-credentials "serv02\Joelle" "pas

sword"

Command Description

--help Shows the list of parameters of the plug-in configuration tool.

--show-config Shows configuration parameters.

Starts the wizard to configure the plug-in settings. This wizard edits the
veeam_config.xml file or creates a new one if the configuration file
--wizard
was removed from the /opt/veeam/VeeamPluginforOracleRMAN
directory.

--set-credentials Specifies credentials to connect to the Veeam Backup & Replication

<"serv\username"> server.
<"password">

--set-host <hostname> Specifies the host of the Veeam Backup & Replication server.

--set-port <port_number> Specifies the host to connect to the Veeam Backup & Replication server.

Launches a wizard to select a backup repository. A backup repository is

--set-repositories selected from repositories which are available in the connected Veeam
Backup & Replication instance.

--set-parallelism Configures Oracle RMAN parallelism settings.

<number_of_channels>

Enables/disables Veeam proprietary feature which compresses backup

--compression <y/n>
files.

--map-backup Maps the imported backups.

--set-force-delete Deletes backup files after specified days.

Enables restore from backup copy. Note that if you enable restore from
--configure-restore-from-
backup copy, you cannot back up databases with Veeam Plug-in. To
copy
revert changes, you must disable restore from backup copy.

130 | Veeam Plug-ins for Enterprise Applications | User Guide

 OracleRMANConfigTool.exe --set-credentials "serv02\Joelle" "pas
sword"

--promote-backup-copy- Maps the imported backup copy to a regular Veeam Plug-in backup chain.
to-primary

131 | Veeam Plug-ins for Enterprise Applications | User Guide

Updating Veeam Plug-in for Oracle RMAN
Periodically, Veeam releases a new version of Veeam Backup & Replication that contains new features and bug
fixes. The release package also contains a new version of Veeam Plug-ins.

If you want to update Veeam Plug-in, note that Veeam Backup & Replication must be the same or newer that
the version of Veeam Plug-in. If you want to use the latest functionality, you must update both Veeam Backup &
Replication and to the latest version. After the update, you don't need to to re-run the Veeam Plug-in
configuration wizard, the plug-in configuration files will be preserved.

For instructions on how to update the plug-in, see the following guides:

• Updating Plug-in on Linux

• Updating Plug-in on Oracle Solaris

• Updating Plug-in on Microsoft Windows

• Updating Plug-in on IBM AIX

Updating Plug-in on Linux

To update Veeam Plug-in for Oracle RMAN on a Linux machine, do the following:

1. Upload the VeeamPluginforOracleRMAN-X.X.X.XXXX.x86_64.rpm package to the Oracle server. If

you need the 32-bit version, choose the i386 package.

2. To update Veeam Plug-in, run the following command. Note that the operation requires root privileges.

rpm -U VeeamPluginforOracleRMAN-X.X.X.XXXX.x86_64.rpm

TIP

To find out which version of Veeam Plug-in is installed on your server, you can use the following
command: rpm -qa | grep VeeamPlugin*

Updating Plug-in on Oracle Solaris

To update Veeam Plug-in for Oracle RMAN on an Oracle Solaris machine, do the following:

1. Upload the VeeamPluginforOracleRMAN-X.X.X.XXXX.SPARC.pkg package to the Oracle server. If

you need the 32-bit version, choose the i386 package.

2. Make sure the pkgadd administration file (admin_file) contains the following entry:
"instance=overwrite". For details, see the Avoiding User Interaction When Adding Packages section
of the Oracle Solaris Administration Guide.

3. To update Veeam Plug-in, run the following command:

pkgadd -a admin_file -d /tmp/VeeamPluginforOracleRMAN-X.X.X.XXXX.SPARC.pkg

132 | Veeam Plug-ins for Enterprise Applications | User Guide

Updating Plug-in on Windows
To update Veeam Plug-in for Oracle RMAN on a Windows machine, download the
VeeamPluginforOracleRMAN.exe file of the new version and install it. The old version will be replaced with
the new version automatically.

You can update Veeam Plug-in for Oracle RMAN to a newer version in the unattended mode using the same
command that is used for unattended installation. For details, see Installing Veeam Plug-in on Windows
Machine in Unattended Mode.

Updating Plug-in on IBM AIX

To update Veeam Plug-in for Oracle RMAN on an IBM AIX machine, do the following:

1. Upload the VeeamPluginforOracleRMAN-X.X.X.XXX-1.aix6.1.ppc.rpm package to the Oracle

server.

2. To update Veeam Plug-in, run the following command. Note that the operation requires root privileges.

rpm -U VeeamPluginforOracleRMAN-X.X.X.XXX-1.aix6.1.ppc.rpm

133 | Veeam Plug-ins for Enterprise Applications | User Guide

Uninstalling Veeam Plug-in for Oracle RMAN
You can uninstall the Veeam Plug-in and undo the configuration changes made by Veeam Plug-in.

When you configure Veeam Plug-in, original settings of Oracle RMAN are saved in the
/opt/veeam/VeeamPluginforOracleRMAN/RMANParameters.xml file (or in the C:\Program
Files\Veeam\VeeamPluginforOracleRMAN\RMANParameters.xml for Windows). If you uninstall Veeam
Plug-in for Oracle RMAN, original settings of Oracle RMAN are restored from the RMANParameters.xml file.

Uninstalling Veeam Plug-in on Linux or IBM AIX Machines

To uninstall Veeam Plug-in and undo the configuration changes, run the following command. Note that the
operation requires root privileges.

rpm -e VeeamPluginforOracleRMAN

Uninstalling Veeam Plug-in on Windows Machines

To uninstall Veeam Plug-in and undo the configuration changes, do the following:

1. Open the Control Panel and click Programs and Features.

2. In the list of programs, select Veeam Plug-in for Oracle RMAN and click Uninstall.

Uninstalling Veeam Plug-in on Solaris Machines

To uninstall Veeam Plug-in and undo the configuration changes, run the following command:

pkgrm VeeamPluginforOracleRMAN

134 | Veeam Plug-ins for Enterprise Applications | User Guide

Importing/Exporting Plug-in Settings
You can export a Veeam Plug-in configuration file and apply the plug-in settings to other severs.

IMPORTANT

The password included in the configuration file is encrypted. Thus, after you import the configuration file,
you must set the credentials manually in the Veeam Plug-in configuration wizard.

To export the configuration file to another Linux server, do the following:

[For Linux and Unix]:

a. On the server where Veeam Plug-in is installed, go to

/opt/veeam/VeeamPluginforOracleRMAN.

b. Copy the veeam_config.xml file to the server where you want to configure the plug-in.

c. Install Veeam Plug-in on the new server and place the copied XML file in the
/opt/veeam/VeeamPluginforOracleRMAN folder.

d. Set new credentials using the following command:

OracleRMANConfigTool --set-credentials "serv\username" "password"

[For Windows]:

a. On the server where Veeam Plug-in is installed, go to

%PROGRAMFILES%\Veeam\VeeamPluginforOracleRMAN\.

b. Copy the veeam_config.xml file to the server where you want to configure the plug-in.

c. Install Veeam Plug-in on the new server and place the copied XML file in the
%PROGRAMFILES%\Veeam\VeeamPluginforOracleRMAN\ folder.

d. Set new credentials using the following command:

C:\Program Files\Veeam\VeeamPluginforOracleRMAN\OracleRMANConfigTool.exe -
-set-credentials "serv\username" "password"

135 | Veeam Plug-ins for Enterprise Applications | User Guide

Importing Backups
If you have lost the Veeam Backup & Replication database or want to import backup files on another Veeam
Backup & Replication server, do the following:

1. Move the folder with the backup file to the required backup repository or create a new backup repository
with this folder as a subfolder.

TIP

Starting from version 11, each Veeam Plug-in backup file (.vab) has its own metadata file (.vasm).
Make sure you import backup files and all related metadata files. Also, you must import the backup
job metadata file (.vacm) which is stored in the same folder.

2. In the Veeam Backup & Replication console, open the Backup Infrastructure view.

3. In the inventory pane of the Backup Infrastructure view, select the Backup Repositories node.

4. In the working area, select the required backup repository and click Rescan on the ribbon. Alternatively,
you can right-click the backup repository and select Rescan.

5. On the Oracle server, start the Veeam Plug-in configuration wizard with the --map-backup parameter:

o For Windows:

"C:\Program Files\Veeam\VeeamPluginforOracleRMAN\OracleRMANConfigTool"
--map-backup

o For Linux and Unix:

136 | Veeam Plug-ins for Enterprise Applications | User Guide

 OracleRMANConfigTool --map-backup

IMPORTANT

If backup files are not imported according to instructions given above, the backup and restore
processes can fail.

137 | Veeam Plug-ins for Enterprise Applications | User Guide

Upgrading Backup Files
Since version 11, Veeam Plug-in uses a new format of backup files: instead of one metadata file for all backup
files there are separate metadata files (.vasm) for each database backup file (.vab). The new metadata format
allows to optimize the productivity of backup and restore operations.

For Veeam Plug-in 11, the backup files upgrade is not obligatory. However, in the next version, backup files
created by Veeam Plug-in version 10 will not be supported.

Prerequisites
Before upgrading backup files, make sure the following requirements are met.

• Make sure that you have upgraded Veeam Plug-in on the source server. If the plug-in is not upgraded to
version 11 and you upgrade the backup files, then all next backup job runs will fail.

• Make sure that you have disabled the backup job whose backup files you want upgrade. You must also
disable the backup copy jobs that use these backup files as a source.

• If the backup files reside on the scale-out backup repository, all repository extents must be available.
Also, the extents must not be in the Seal or Maintenance mode.

• If you want to upgrade backup files created by a backup copy job, you must meet the same requirements
as for the backup job files.

• During the process of the metadata upgrade, you cannot run the target backup job and you cannot restore
from the backup files.
The upgrade process duration depends on the number of backup files in the backup set, type of the
backup repository and workload level on the file system.
For example, there are backup files of an Oracle server that contains 10 instances and is backed up every
15 minutes with the retention policy set for 2 weeks. The upgrade of backup files can have the following
duration on not overloaded file systems:

o Microsoft Windows: 30 minutes

o Linux: from 30 minutes to 3 hours

o SMB/NFS: 1.5 hours

o Data Domain Boost/Quantum DXi/ExaGrid/CIFS (SMB)/NFS file share: 3-4 hours

o HPE StoreOnce: up to 10 hours (due to specifics of this repository type for processing large number of
files)

Upgrading Backup Files in Veeam Backup & Replication

Console
To upgrade backup files in the Veeam Backup & Replication console, do the following:

1. Open the Home view.

2. In the inventory pane, expand the Backups view and select Disk.

138 | Veeam Plug-ins for Enterprise Applications | User Guide

 3. In the working area, right-click the job or the restore point and select Upgrade.
Alternatively, you can select the job or the restore point and click Upgrade on the ribbon.

139 | Veeam Plug-ins for Enterprise Applications | User Guide

Database Protection
After you configure Veeam Plug-in, you can use the Oracle RMAN functionality to back up databases. Veeam
Plug-in will automatically transfer the backup files to the Veeam backup repository.

The examples given below are for demonstration purposes only. The backup process is performed on the Oracle
RMAN side. Consider configuring required RMAN-specific parameters that may affect the backup process. For
details on the backup functionality of Oracle RMAN, see the Backing Up the Database section of the Oracle's
Database Backup and Recovery User's Guide.

NOTE

Mind the following:

• In the Veeam Plug-in configuration wizard, you can enable/disable Veeam Plug-in Data Compression
and Deduplication. If you enable the Veeam Plug-in compression, do not use Oracle RMAN integrated
compression as well. It can slow down the backup and restore processes.
• It is Oracle's best practice to add the EXIT; command at the bottom of the script to shut down the
RMAN utility. Without the EXIT; command in the script, it is up to Oracle RMAN to decide when to
close the backup session, which can lead to multiple unclosed RMAN backup sessions.

TIP

If you have configured the retention policy, run the DELETE OBSOLETE command after the database
backup to delete obsolete backups from the repository.

In this Section
• Oracle RMAN Full Backup

• Oracle RMAN Channel Allocation

• Backup Job in Veeam Backup & Replication

140 | Veeam Plug-ins for Enterprise Applications | User Guide

Oracle RMAN Full Backup
After you configure Veeam Plug-in, you can use the Oracle RMAN functionality to back up databases. Veeam
Plug-in will automatically transfer the backup files to the Veeam backup repository.

The examples given below are for demonstration purposes only. The backup process is performed on the Oracle
RMAN side. Consider configuring required RMAN-specific parameters that may affect the backup process. For
details on the backup functionality of Oracle RMAN, see the Backing Up the Database section of the Oracle's
Database Backup and Recovery User's Guide.

Consistent Backup of Oracle Database in ARCHIVELOG Mode

To create a consistent backup of an Oracle database and redo logs in the ARCHIVELOG mode, run the following
script:

rman TARGET /
RUN {
BACKUP DATABASE PLUS ARCHIVELOG;
}
EXIT;

In this example, Oracle RMAN will back up the entire database and available archived redo logs. The current
online redo log will be archived to make sure all redo changes are transferred to the archived redo log chain. In
the ARCHIVELOG mode, there will be no downtime as you don't have to shut down the database. For details on
the backup process in different modes, see the Choosing Between NOARCHIVELOG and ARCHIVELOG Mode
section of the Oracle's Database Administrator's Guide.

Consistent Backup of Oracle Database in NOARCHIVELOG

Mode
To create a consistent backup of an Oracle database operating in NOARCHIVELOG mode, start the Oracle RMAN
console and run the following script. Note that the database will be unavailable during the backup. In this
example, the database instance will be started after the backup process is complete.

rman TARGET /
RUN {
SHUTDOWN TRANSACTIONAL;
STARTUP MOUNT;
BACKUP DATABASE;
STARTUP;
}
EXIT;

141 | Veeam Plug-ins for Enterprise Applications | User Guide

Oracle RMAN Channel Allocation
If you want to manually allocate channels for backup operations, you must specify the Veeam backup repository
UUID in the channel parameters. The ALLOCATE CHANNEL command must be issued within a RUN block. It
allocates a channel only in the block where the command is issued. See the following example.

RUN {
ALLOCATE CHANNEL ch1 DEVICE TYPE SBT_TAPE PARMS 'SBT_LIBRARY=/opt/veeam/Ve
eamPluginforOracleRMAN/libOracleRMANPlugin.so' FORMAT 'd8338780-1aec-4c36-b17c-
e1ea3ea2ca93/RMAN_%I_%d_%T_%U.vab';
BACKUP DATABASE;
RELEASE CHANNEL ch1;
}
EXIT;

Run the Oracle RMAN script with the following parameters:

1. Use the ALLOCATE CHANNEL command to manually allocate a channel or channels between RMAN and
the database instance. Specify the following parameters:

a. Specify the channel ID. For example: ch1.

b. Specify the SBT_TAPE option for the DEVICE TYPE parameter.

c. Specify PARMS to define other parameters for the sbt_tape channel.

d. Specify which media library must be used for this sbt_tape channel: set the path to the
libOracleRMANPlugin.so file as the SBT_LIBRARY.

e. Use the Veeam backup repository UUID in the argument for the FORMAT parameter. You can find the
required backup repository UUID in the rman_config.txt file saved during the Veeam Plug-in
configuration process or in logs.
[For Linux] If you have exported Veeam Plug-in configuration files, run the following command to see
open the configuration file.

cat /tmp/rman_config.txt

Alternatively, you can find the repository UUID in logs:

grep "received repos" /tmp/veeam_plugin_logs/oracle/OracleRMANConfigToo

l.log | tail

[For Windows] If you have exported Veeam Plug-in configuration files, find the channel allocation
definition in the configuration file.
Alternatively, you can find the repository UUID in logs. Go to the
%\ProgramData\Veeam\Backup\RmanPluginLogs\SERV_NAME directory and search for
"received repos id" in the OracleRMANConfigToolLib.log file.

2. Use the BACKUP command with required parameters to create a database backup.

3. Using the RELEASE CHANNEL command within RUN is optional, because RMAN automatically releases all
normal channels when the RUN command terminates.

142 | Veeam Plug-ins for Enterprise Applications | User Guide

Backup Job in Veeam Backup & Replication
After you start a backup process in Oracle RMAN, Veeam Backup & Replication creates a backup job. You can use
this job to view the statistics on the backup process, generate backup job reports or you can also disable the
backup job.

You cannot start or edit Oracle RMAN backup jobs in the Veeam Backup & Replication console. You can manage
backup operations only on the Oracle side using RMAN.

NOTE

The progress bar of a running Oracle database backup job is available only for backups of standalone Oracle
databases. It is not available for Oracle RAC backups.

In this section:

• Viewing Backup Job Statistics

• Generating Backup Job Reports

• Disabling Backup Job

Viewing Backup Job Statistics

To view details of a backup job process, do the following.

1. Open the Veeam Backup & Replication console.

2. In the Home view, expand the Jobs node and click Backup.

3. In the list of jobs, select the Oracle RMAN backup job to see details of the current backup process or the
last backup job session.

143 | Veeam Plug-ins for Enterprise Applications | User Guide

Generating Backup Job Reports
You can generate reports with details about an Oracle RMAN backup job session performance. The session
report contains the following session statistics: session duration details, details of the session performance,
amount of read, processed and transferred data, backup size, compression ratio, list of warnings and errors (if
any).

1. Open the Home view.

2. In the inventory pane, select Jobs.

3. In the working area, select the necessary job and click Report on the ribbon. You can also right-click the
job and select Report.

Disabling Backup Job

You can disable Oracle RMAN backup jobs in the Veeam Backup & Replication console. If you disable the job, you
will not be able to run RMAN backup commands on the Oracle server.

To disable a backup job:

1. Open the Home view.

2. In the inventory pane, select Jobs.

144 | Veeam Plug-ins for Enterprise Applications | User Guide

 3. In the working area, select the necessary job and click Disable on the ribbon. You can also right-click the
job and select Disable.

145 | Veeam Plug-ins for Enterprise Applications | User Guide

Database Recovery
With the configured Veeam Plug-in for Oracle RMAN, you can perform all kinds of database restore operations
available in Oracle RMAN. You can also restore from database backups in the Veeam Backup & Replication
console.

• Restore to Original Server

• Restore to Another Server

• Restore from Backup Copy

• Restore with Veeam Explorer for Oracle

• Restore of Control File from Autobackup

146 | Veeam Plug-ins for Enterprise Applications | User Guide

Restore to Original Server
Veeam Plug-in for Oracle RMAN allows to restore databases using built-in Oracle RMAN functionality. When you
launch the restore, RMAN restores the selected database from the backup stored on the Veeam backup
repository.

If you want to change the repository or channel settings, you must configure the Veeam Plug-in settings. For
details, see Configuring Veeam Plug-in for Oracle RMAN.

To restore the Oracle database, connect to the database with RMAN and run the restore command. You may
need to run additional commands depending on your database infrastructure. Consider configuring required
RMAN-specific parameters that may affect the backup process. For details on all restore capabilities of Oracle
RMAN, see the Performing Complete Database Recovery section of the Oracle's Database Backup and Recovery
User's Guide.

rman TARGET /
RUN {
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
RESTORE DATABASE;
RECOVER DATABASE;
}
EXIT;

NOTE

If you use the SEND command on the target server to point to the source server, you can run operations
like DUPLICATE. For details, see Restore to Another Server Using RMAN.

147 | Veeam Plug-ins for Enterprise Applications | User Guide

Restore to Another Server
If you want to restore Oracle databases from a Veeam Plug-in backup to another server, follow instructions in
the Restoring a Database on a New Host section of Oracle's Database Backup and Recovery User's Guide and
mind the peculiarities described below:

• Restore from Backup to Another Server

• Restore from Backup Copy to Another Server

Restore from Backup to Another Server

After you allocate channels, you must use the SEND command with the srcSrv=originalServerName
parameter, where originalServerName is the hostname of the protected server. In case of RAC, use the
SCAN name as originalServerName.

TIP

Veeam Plug-in backup job name contains the name of the original server. You can find out what to use as
originalServerName if you look at the first part of the Veeam Plug-in backup job name.

Example of a script for restoring Oracle database to another server using the SEND command:

rman TARGET /
RUN {
ALLOCATE CHANNEL a1 TYPE sbt_tape PARMS "SBT_LIBRARY=/opt/veeam/VeeamPluginforO
racleRMAN/libOracleRMANPlugin.so" SEND "srcSrv=ora";
RESTORE DATABASE;
RECOVER DATABASE;
}
EXIT;

Restore from Backup Copy to Another Server

If you want to restore a database from a backup copy to another server, do the following:

1. On the Oracle server, go to

the \Veeam\VeeamPluginforOracleRMAN folder (/opt/veeam/VeeamPluginforOracleRMAN/ for
Linux OS).

1. Open the veeam_config.xml file with a text editor.

2. Change the <PluginParameters /> line as follows:

o For a standalone Oracle Server:

<PluginParameters customServerName="original_server_hostname" />

o For Oracle RAC:

<PluginParameters customServerName="original_cluster_scan_name" />

148 | Veeam Plug-ins for Enterprise Applications | User Guide

 IMPORTANT

Mind the following:

• Veeam Plug-in for Oracle RMAN must be installed and configured on the target server.
• Before you perform any other backup or restore job, revert back the changes in the
veeam_config.xml file. The default configuration is: <PluginParameters />

4. Enable the restore from backup copy option, as described in Restore from Backup Copy.

5. Perform the restore.

rman TARGET /
RUN {
ALLOCATE CHANNEL a1 TYPE sbt_tape PARMS "SBT_LIBRARY=/opt/veeam/VeeamPlugi
nforOracleRMAN/libOracleRMANPlugin.so";
RESTORE DATABASE;
RECOVER DATABASE;
}
EXIT;

149 | Veeam Plug-ins for Enterprise Applications | User Guide

Restore from Backup Copy
You can restore from backups and backup copies. To restore from backup copies, you must enable the restore
from backup copy option in the Veeam Plug-in wizard.

If the restore from backup copy option is enabled, you cannot back up databases using Veeam Plug-in, and you
cannot restore from backups created by primary Veeam Plug-in backup jobs. You can restore only from backup
copy files until you disable the restore from backup copy option.

• Enabling Restore from Backup Copy

• Disabling Restore from Backup Copy

IMPORTANT

Mind the following:

• You can restore from Veeam Plug-in backups using Veeam Explorer for Oracle, even if the restore
from backup copy option is enabled.
• If you want to restore from a backup copy to another server, see Restore from Backup Copy to
Another Server.

Enabling Restore from Backup Copy

To be able to restore from backup copies, do the following.

• For Linux or Unix OS:

a. Open the terminal and launch the following command:

OracleRMANConfigTool --configure-restore-from-copy

b. Select the number of the required backup copy job:

Select secondary job for failover:

0. Disable
1. Plug-ins backup copy job\SERV02 Oracle backup <serv10_repo>
Select secondary job for failover:1

IMPORTANT

The account used to connect to the Veeam Backup & Replication server must have access permissions on
the required repository.

• For Windows OS:

a. Go to the Veeam Plug-in installation directory (by default, C:\Program

Files\Veeam\VeeamPluginforOracleRMAN\) and launch the following command:

OracleRMANConfigTool.exe --configure-restore-from-copy

150 | Veeam Plug-ins for Enterprise Applications | User Guide

 b. Select the number of the required backup copy job:

Select secondary job for failover:

0. Disable
1. Plug-ins backup copy job\SERV02 Oracle backup <serv10_repo>
Select secondary job for failover:1

Disabling Restore from Backup Copy

To be able to back up with Veeam Plug-in and restore from backups, disable the restore from backup copies:

• For Linux or Unix OS:

OracleRMANConfigTool --configure-restore-from-copy
Select secondary job for failover:
0. Disable
1. Plug-ins backup copy job\SERV02 Oracle backup <serv10_repo>
Select secondary job for failover:0

• For Windows OS:

a. Go to the Veeam Plug-in installation directory (by default, C:\Program

Files\Veeam\VeeamPluginforOracleRMAN\).

b. Run the following command and select 0 as a secondary job for failover:

OracleRMANConfigTool.exe --configure-restore-from-copy
Select secondary job for failover:
0. Disable
1. Plug-ins backup copy job\SERV02 Oracle backup <serv10_repo>
Select secondary job for failover:0

151 | Veeam Plug-ins for Enterprise Applications | User Guide

Restore with Veeam Explorer for Oracle
You can restore Oracle databases from Veeam Plug-in backups in the Veeam Backup & Replication console. To
restore Oracle databases Veeam Backup & Replication uses Veeam Explorer for Oracle. For details, see the
Restoring Oracle RMAN Backups section of the Veeam Explorers User Guide.

IMPORTANT

[For Solaris OS and IBM AIX] Veeam Explorer for Oracle does not support restore of Oracle databases
deployed on Solaris OS and IBM AIX. You can restore Oracle databases on Solaris OS and IBM AIX only with
RMAN. For details, see the Restore with Oracle RMAN section of the Veeam Plug-ins for Enterprise
Applications User Guide.

TIP
• To perform restore from Oracle databases you can also use Veeam Explorer's cmdlets. For details,
see the Veeam Explorer for Oracle section of the Veeam Explorers Powershell Reference.
• For details on Veeam Explorer for Oracle, see the Veeam Explorer for Oracle section of the Veeam
Explorers User Guide.

152 | Veeam Plug-ins for Enterprise Applications | User Guide

Restore of Control File from Autobackup
You may need to restore the Oracle database control file in the following cases:

• If you want to restore the database to a new location where the control file does not exist

• If the database control file is lost or corrupted

If you use Veeam Plug-in for Oracle RMAN and want to restore the Oracle database control file from
autobackup, the autobackup format must be set to the SBT_TAPE device type.

To check if persistent configuration for the control file autobackup format is set to the SBT_TAPE device type,
you can run the SHOW ALL or SHOW CONTROLFILE AUTOBACKUP FORMAT commands in the RMAN console. If
the persistent configuration is set, you don't need to set the control file autobackup format before the restore
command. If it is not set, you must run the SET CONTROLFILE AUTOBACKUP command before the restore
process. See the following examples.

NOTE

To restore the control file from autobackup, the database must be in the NOMOUNT state.

Restoring Control File if Persistent Configuration Setting is

NOT Set
If the persistent configuration for the control file autobackup format is NOT set to the SBT_TAPE device type,
you must set the autobackup format before running the control file restore.

RUN {
ALLOCATE CHANNEL c0 DEVICE TYPE sbt PARMS 'SBT_LIBRARY=/opt/veeam/VeeamPluginfo
rOracleRMAN/libOracleRMANPlugin.so';
SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F_RMAN_AUTOBA
CKUP.vab';
RESTORE controlfile FROM 'c-4097408439-20200410-00_RMAN_AUTOBACKUP.vab';
}
EXIT;

Restoring Control File if Persistent Configuration Setting is Set

If persistent configuration for the control file autobackup format is set to the SBT_TAPE device type, you must
set the autobackup format before running the control file restore. To restore the control file, run the following
script in the RMAN console:

RUN {
ALLOCATE CHANNEL c0 DEVICE TYPE sbt PARMS 'SBT_LIBRARY=/opt/veeam/VeeamPluginfo
rOracleRMAN/libOracleRMANPlugin.so';
RESTORE controlfile FROM 'c-4097408439-20200410-00_RMAN_AUTOBACKUP.vab';
}
EXIT;

153 | Veeam Plug-ins for Enterprise Applications | User Guide

See Also
• For details on restoring the control file, see the RMAN Restore: Restoring Lost Database Files from Backup
section of the Database Backup and Recovery Basics guide.

• For details on the control file autobackup format, see the Configuring the Control File Autobackup Format
section of the Database Backup and Recovery Basics.

154 | Veeam Plug-ins for Enterprise Applications | User Guide

Retention of RMAN Backups
In the main scenario, when using Veeam Plug-in for Oracle RMAN, you must configure retention policies for
RMAN backups and archived redo logs using native Oracle RMAN functionality:

• Configuring Retention Policy

• Configuring Archived Redo Log Retention

Also, you can manually delete backups from a backup repository using the Veeam Backup & Replication console
and enable the force deletion functionality of Veeam Plug-in for Oracle RMAN. For details, see:

• Configuring Force Deletion of Backups

• Deleting Backups Manually

• Deleting Backups from Configuration

155 | Veeam Plug-ins for Enterprise Applications | User Guide

Configuring Retention Policy
If you want to edit a retention policy for Oracle RMAN backups, you must connect to the target database in
RMAN console and run set one of the following retention policies:

• Redundancy-Based Retention: The redundancy parameter specifies how many full or level 0 backups of
each data file and control file should RMAN keep in the repository. If the number of backups exceeds the
specified value, RMAN considers the oldest backups as obsolete. By default, the redundancy parameter is
set to 1. To configure a redundancy-based retention policy, run the following command:

CONFIGURE RETENTION POLICY TO REDUNDANCY 7;

• Recovery Window-Based Retention: The recovery window parameter specifies the number of days
between the current time and the earliest point of recoverability. RMAN does not consider any full or level
0 incremental backups as obsolete if it falls within the recovery window. To configure a window-based
retention policy, run the following command:

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 days;

Deleting Obsolete Backups

To delete obsolete backups, run the following command after each backup:

DELETE OBSOLETE;

Disabling Retention Policy

To disable retention policy for RMAN backups, run the following command:

CONFIGURE RETENTION POLICY TO NONE;

For details, see the Configuring the Backup Retention Policy section of the Oracle Database Backup and recovery
User's Guide.

156 | Veeam Plug-ins for Enterprise Applications | User Guide

Configuring Redo Log Retention
By default, archivelog deletion policy is disabled. While the archivelog deletion policy is disabled, RMAN deletes
archived redo log backups according to the backup retention policy. If the backup retention policy is not
configured, RMAN stores only the latest archived log backup.

To configure archivelog deletion policy, run the following command. When the number of archived log backups
exceeds the specified number, RMAN deletes the oldest archived log backup.

CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 3 TIMES TO SBT;

To disable archivelog deletion policy, run the following command:

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

For details, see the Configuring the Backup Retention Policy section of the Oracle Database Backup and recovery
User's Guide.

157 | Veeam Plug-ins for Enterprise Applications | User Guide

Configuring Force Deletion of Backups
In the main scenario, when using Veeam Plug-in for Oracle RMAN, you must configure the retention policy using
native Oracle RMAN tools. For details, see Configuring Retention Policy.

Veeam Plug-in for Oracle RMAN has a functionality that automatically force deletes backup files which are older
than specified number of days. For example, you can use it if a backup repository contains backup files that are
no longer in the backup catalog.

To enable force deletion of backup files, do the following:

1. On the Oracle server, run the following command.

o For Linux and Unix:

OracleRMANConfigTool --set-force-delete

o For Microsoft Windows:

OracleRMANConfigTool.exe --set-force-delete

By default, the OracleRMANConfigTool.exe file is located in C:\Program

Files\Veeam\VeeamPluginforOracleRMAN.

2. Enter the number of days after which Veeam Plug-in will force delete backup files on all configured
Veeam backup repositories.

Garbage collector automatically deletes backup files older than the specif
ied number of days.
Make sure the number of days value exceeds your retention policy.
To disable this functionality, set the number of days to 0.
Enter the number of days to delete backups after, between 7 and 999 [0]:

By default, the force delete functionality is disabled (set to 0).

IMPORTANT
• A value for the number of days setting must be at least 1 backup generation period longer than the
retention period for your Oracle Database backups. Otherwise, Veeam Plug-in will delete earliest
backups created within the retention period.
• If a backup repository contains backups older than the specified retention period, Veeam Plug-in
removes old backup files only after the next run of the RMAN backup.

158 | Veeam Plug-ins for Enterprise Applications | User Guide

Deleting Backups Manually
If you want to delete backups files, you can use the Oracle RMAN housekeeping functionality. For details, see
the Deleting RMAN Backups and Archived Redo Logs section of the Oracle Database Backup and Recovery User's
Guide.

If you have lost the backup catalog, you can remove the backups manually from Veeam backup repositories.

NOTE

If you remove backups from a Veeam backup repository manually, the backup catalog will not be updated.

To remove a backup from Veeam backups repository, do the following:

1. In the Veeam Backup & Replication console, open the Home view.

2. In the Inventory pane, select Backups.

3. In the working area, right-click the backup job object name and select Delete from disk.

159 | Veeam Plug-ins for Enterprise Applications | User Guide

Removing Backups from Configuration
If you want to remove records about backups from the Veeam Backup & Replication console and configuration
database, you can use the Remove from configuration operation.

When you remove a backup from the configuration, backup files (VAB, VBM) remain on the backup repository.
You can import the backup later and restore data from it.

To remove a backup from the configuration:

1. Open the Home view.

2. In the inventory pane, select Backups.

3. In the working area, select the backup and click Remove from > Configuration on the ribbon. You can also
right-click the backup and select Remove from configuration.

160 | Veeam Plug-ins for Enterprise Applications | User Guide

Backup Copy for Oracle RMAN Backups
Having just one backup does not provide the necessary level of safety. The primary backup may get destroyed
together with production data, and you will have no backups from which you can restore data.

To build a successful data protection and disaster recovery plan, it is recommended that you follow the 3-2-1
rule:

• 3: You must have at least three copies of your data: the original production data and two backups.

• 2: You must use at least two different types of media to store the copies of your data, for example, local
disk and cloud.

• 1: You must keep at least one backup offsite, for example, in the cloud or in a remote site.

Thus, you must have at least two backups and they must be in different locations. If a disaster takes out your
production data and local backup, you can still recover from your offsite backup.

To help you adopt the 3-2-1 rule, Veeam Backup & Replication offers the backup copy functionality that allows
you to create several instances of the same backup in different locations, whether onsite or offsite. Backup
copies have the same format as those created by backup jobs and you can recover your data from them when
you need it.

Veeam Backup & Replication fully automates the backup copy process and lets you specify retention settings to
maintain the desired number of restore points, as well as full backups for archival purposes. Backup copy is a
job-driven process. When enabled, the backup copy job for Veeam Plug-in backups runs continuously.

For details on how it works, see the Backup Copy section of the Veeam Backup & Replication User Guide.

161 | Veeam Plug-ins for Enterprise Applications | User Guide

Creating Backup Copy Job
To copy backups to a secondary location, you must configure a backup copy job. The backup copy job defines
how, where and when to copy backups. One job can be used to process backups of one or more machines.

You can configure a job and start it immediately or save the job to start it later.

Before creating a job, check prerequisites. Then use the New Backup Copy Job wizard to configure a backup
copy job.

1. Launch Backup Copy Job wizard.

2. Specify a job name and description.

3. Selects backups to process.

4. Define backup copy target.

5. Specify advanced settings.

6. Define backup copy schedule.

7. Finish working with the wizard.

Before You Begin

Before you create a backup copy job, check the prerequisites and limitations:

• If you create a backup copy job for a backup of Veeam Plug-in version 9.5 Update 4, the backups will not
be copied. Veeam Plug-in will issue a warning that you must upgrade Veeam Plug-in to version 10. After
you upgrade the plug-in and create a new restore point, backup copy job will start to function and copy
backup files created by both plug-in versions.

• Backup infrastructure components that will take part in the backup copy process must be added to the
backup infrastructure and properly configured. These include source and target backup repositories
between which backups must be copied.

• The target backup repository must have enough free space to store copied backups. To receive alerts
about low space on the backup repository, configure global notification settings. For more information,
see Specifying Other Notification Settings.

• For Veeam Plug-in backup copy jobs, you cannot select a Veeam Cloud Connect repository as a backup
copy target.

• If you have upgraded the backup files, make sure that you have upgraded Veeam Plug-in on the source
server. If the plug-in is not upgraded to version 11 and you convert backup copy files to backup files, then
the next backup job runs will fail.

162 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 1. Launch Backup Copy Job Wizard
To create a backup copy job, do the following:

1. In the Veeam Backup & Replication console, open the Home view.

2. Click the Backup Copy tab and select Application backup.

163 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 2. Specify Job Name and Description
At the Job step of the wizard, specify a name and description for the backup copy job.

1. In the Name field, enter a name for the job.

2. In the Description field, enter a description for the job. The default description contains information about
the user who created the job, date and time when the job was created.

164 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 3. Selects Backups to Process
At the Object step of the wizard, select machines whose backups you want to copy to the target repository.

1. Click the Add button and select from which entity you want to process the machines.

o From jobs: You can select Veeam Plug-in backup jobs. When a backup copy job runs, Veeam Backup &
Replication will search for backup files created by selected jobs.

o From repositories: You can select repositories where Veeam Plug-in backups are stored. When a
backup copy job runs, Veeam Backup & Replication will search for backup files created by Veeam
Plug-in in selected repositories.
[Optional] If you have added jobs from a repository and want to exclude from processing some of the
backup jobs on the selected repository, click Exclusions and select the jobs that you want to exclude.

2. Use the Remove button if you want to remove selected jobs or repositories from processing.

165 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 4. Define Backup Copy Target
At the Target step of the wizard, configure the target repository settings.

1. From the Backup repository list, select a backup repository in the target site where copied backups must
be stored. When you select a target backup repository, Veeam Backup & Replication automatically checks
how much free space is available on it. Make sure that you have enough free space to store copied
backups.

IMPORTANT

For Veeam Plug-in backup copy jobs, you cannot select a Veeam Cloud Connect repository as a
backup copy target.

2. [Optional] If the target repository contains a Veeam Plug-in backup that was excluded from the backup
copy job, and if you don't want to transfer duplicate data, you can use the mapping feature.
After you configure mapping, if some of backup files (.VAB) of the source backup are missing in the target
backup copy, these files are uploaded to the target backup copy.

NOTE

Veeam Plug-in backup copy jobs does not use WAN accelerators.

To map a backup copy job to the backup:

a. Click the Map backup link.

b. Point the backup copy job to the backup in the target backup repository. Backups in the target backup
repository can be easily identified by backup job names. To facilitate search, you can use the search
field at the bottom of the window.

IMPORTANT
• Used account must have access to Veeam backup repositories that you plan to use.
• Encryption must be disabled on the repository.

Otherwise, the repositories will not be listed as available. To learn how to configure access
permissions and encryption settings on repositories, see Access and Encryption Settings on
Repositories.

166 | Veeam Plug-ins for Enterprise Applications | User Guide

 3. You can specify the number of days after which the backup copy will be deleted from the repository. Note
that the countdown starts from the moment when source backup has been created.

167 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 5. Specify Advanced Settings
At the Target step of the wizard, click Advanced to configure compression, RPO and notifications settings.

• Compression and Deduplication

• RPO

• Notifications

Compression and Deduplication

At the Storage tab, define compression and deduplication settings.

By default, Veeam Backup & Replication performs deduplication before storing copied data on the target backup
repository. Deduplication provides a smaller size of the resulting backup file but may reduce the job
performance.

1. You can disable data deduplication. To do this, clear the Enable inline data deduplication check box.

2. From the Compression level list, choose a compression level to be used: Auto, None, Dedupe-friendly,
Optimal, High or Extreme. The recommended level of compression for backup copy jobs is Auto. In this
case, Veeam Backup & Replication uses compression settings of the copied backup files. For more
information, see Compression and Deduplication.

RPO Monitor
At the RPO Monitor tab, specify RPO warning settings.

168 | Veeam Plug-ins for Enterprise Applications | User Guide

Enable the Warn me if backup is not copied within check box and specify the time period in minutes, hours, or
days.

If the backup copy is not created within the specified time period, the backup copy job will finish with the
Warning status. The countdown starts from the moment when the required backup is finished and ready to be
copied.

Notifications
At the Notifications tab, to specify notification settings for the backup copy job:

1. At the Target step of the wizard, click Advanced.

2. Click the Notifications tab.

3. Select the Send SNMP notifications for this job check box if you want to receive SNMP traps when the job
completes successfully. SNMP traps will be sent if you specify global SNMP settings in Veeam Backup &
Replication and configure software on recipient's machine to receive SNMP traps. For more information,
see Specifying SNMP Settings.

4. Select the Send email notifications to the following recipients check box if you want to receive
notifications by email in case of job failure or success. In the field below, specify a recipient’s email
address. You can enter several addresses separated by a semicolon.

5. Veeam Backup & Replication sends a consolidated email notification once for the specified backup copy
interval. Even if the synchronization process is started several times within the interval, for example, due
to job retries, only one email notification will be sent.

6. Email notifications will be sent if you configure global email notification settings in Veeam Backup &
Replication. For more information, see Configuring Global Email Notification Settings.

169 | Veeam Plug-ins for Enterprise Applications | User Guide

 7. At the Send at field, specify the time when you want to receive notifications. Note that you will receive a
notification on a status of the job status once a day.

8. You can choose to use global notification settings or specify custom notification settings.

o To receive a typical notification for the job, select Use global notification settings. In this case, Veeam
Backup & Replication will apply to the job global email notification settings specified for the backup
server. For more information, see Configuring Global Email Notification Settings.

o To configure a custom notification for a job, select Use custom notification settings specified below.
You can specify the following notification settings:

i. In the Subject field, specify a notification subject. You can use the following variables in the
subject: %Time% (completion time), %JobName%, %JobResult%, %VmCount% (number of
machines in the job) and %Issues% (number of machines in the job that have been processed
with the Warning or Failed status).

ii. Select the Notify on success, Notify on warning and Notify on error check boxes to receive email
notification if data processing within the backup copy interval completes successfully, fails or
completes with a warning.

170 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 6. Define Backup Copy Schedule
At the Schedule step of the wizard, define a time span in which the backup copy job must not transport data
between source and target backup repositories. For more information, see Backup Copy Window.

To define a backup window for the backup copy job:

1. Select the During the following time periods only option.

2. In the schedule box, select the desired time area.

3. Use the Enable and Disable options to mark the selected area as allowed or prohibited for the backup copy
job.

171 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 7. Finish working with the wizard
At the Summary step of the wizard, complete the procedure of backup copy job configuration.

1. Review details of the backup copy job.

2. Select the Enable the job when I click Finish check box if you want to start the job right after you finish
working with the wizard.

3. Click Finish to close the wizard.

172 | Veeam Plug-ins for Enterprise Applications | User Guide

Converting Backup Copy to Backup
If you have imported Veeam Plug-in backup copies from another server, you can convert them into regular
backup files. When you convert a backup copy to a backup, Veeam Plug-in creates a backup job with the
converted backup. You can use this backup job to continue a backup chain and use the converted backup as a
restore point.

You can convert unbind Veeam Plug-in backups into regular Veeam Plug-in backup files in the following cases:

• If you have deleted a backup copy job which created the backup copy.

• If you have excluded a backup job from a backup copy job that used multiple backup jobs as a source.

• If you imported a Veeam Plug-in backup copy from another host.

NOTE

If you want to restore from a backup copy, you don't need to convert the backup copy to backup. For
details, see Restore from Backup Copy.

Procedure
To convert a backup copy to a primary backup, use the --promote-backup-copy-to-primary parameter as shown
below:

1. Run the OracleRMANConfigTool with the --promote-backup-copy-to-primary parameter and type a

backup copy number from the list of available backup copies.

OracleRMANConfigTool --promote-backup-copy-to-primary
Backup copies available for promotion to the primary backup target:
1. Backup Copy Job 1\ORCLSERV01 Oracle backup (Default Backup Repository)
Select a backup copy: 1
Changes to be applied to the RMAN configuration
CONFIGURE CHANNEL DEVICE TYPE SBT_TAPE
PARMS 'SBT_LIBRARY=C:\PROGRA~1\Veeam\VEEAMP~1\ORACLE~2.DLL'
FORMAT '94a7ac5a-2cb5-418b-8395-fb362d3aa182/RMAN_%I_%d_%T_%U.vab';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F_RM
AN_AUTOBACKUP.vab';
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1;
RMAN configuration to be applied:
SQL "alter system set backup_tape_io_slaves=false deferred scope=both";

173 | Veeam Plug-ins for Enterprise Applications | User Guide

 2. Converting a backup copy into regular backup file, requires changes in the RMAN configuration. You can
allow the command to change RMAN configuration automatically, or you can change it manually. Select
one of the options:

Proceed with the action?

1. Promote backup copy destination to the primary backup target and apply
required configuration to RMAN automatically
2. Promote backup copy destination to the primary backup target and export
required RMAN configuration (RMAN will have to be configured manually)
3. Cancel
Enter selection: 1
Promoting backup copy destination
Configuring RMAN
Done

174 | Veeam Plug-ins for Enterprise Applications | User Guide

Veeam Plug-in for SAP on Oracle
Veeam Plug-in for SAP on Oracle is a SAP-certified backup tool for SAP products running on Oracle Database.
Veeam Plug-in integrates with SAP BR*Tools and transfers database and log backups to repositories connected
to Veeam Backup & Replication.

TIP

If you want to protect the SAP server itself, you can use the image-level backup functionality of Veeam
Backup & Replication or Veeam Agent for Linux.

175 | Veeam Plug-ins for Enterprise Applications | User Guide

How Veeam Plug-in for SAP on Oracle
Works
Veeam Plug-in for SAP on Oracle functions as an agent between SAP BR*Tools and Veeam backup repositories.
After you install and configure Veeam Plug-in, you can perform all backup and restore operations with
BR*Tools. Veeam Plug-in compresses, deduplicates database backups and transfers them to a backup repository
connected to Veeam Backup & Replication.

Veeam Plug-in for SAP on Oracle supports the following tools:

• brtools

• brbackup

• brrestore

• brarchive

For details about these tools, see the SAP Database Guide: Oracle.

Procedure
After you configure Veeam Plug-in for SAP on Oracle, SAP BR*Tools performs the backup in the following way:

1. When you launch a database backup, BRTOOLS starts the services of Veeam Plug-in.

2. Veeam Plug-in connects to the Veeam Backup & Replication server and creates a backup job object (if it
has not been created before). Veeam Backup & Replication administrators can use this backup job object
to monitor the backup process, manage backup files and copy the database backup to secondary
repositories.

3. BRTOOLS launches the backint BRBACKUP tool that uses the Veeam Plug-in configuration file as an
initialization profile.

4. Veeam Plug-in starts Veeam Data Mover on the SAP server and on the backup repository. Veeam Data
Movers create communication channels for each backup data stream. Depending on the number of
channels specified in Veeam Plug-in settings, there can be 1 or up to 32 parallel channels.

176 | Veeam Plug-ins for Enterprise Applications | User Guide

 5. Veeam Data Movers transport database backup files to the backup repository.

177 | Veeam Plug-ins for Enterprise Applications | User Guide

Planning and Preparation
Before you start to use Veeam Plug-in for SAP on Oracle, read the environment planning recommendations and
make sure that your environment meets system requirements.

• System Requirements

• Required Permissions

• Used Ports

• Licensing

• Environment Planning

• Veeam Backup Repositories

• Granting Permissions on Veeam Backup Repositories

178 | Veeam Plug-ins for Enterprise Applications | User Guide

System Requirements
Before you start using Veeam Plug-in for SAP on Oracle, consider the following requirements.

Supported OSes
Veeam Plug-in for SAP on Oracle is supported for the following OSes:

• SUSE Linux Enterprise Server 11, 12, 15 (x86_64)

• Red Hat Enterprise Linux for SAP Applications 6, 7 (x86_64)

• Oracle Linux 6, 7

BR*Tools
Veeam Plug-in for SAP on Oracle supports BR*Tools 7.20 Patch 42 or later.

Oracle DB
Veeam Plug-in for SAP on Oracle supports Oracle Database 11gR2, 12c, 18c, 19c: Standard and Enterprise Edition
(Express Edition is not supported).

Veeam Backup & Replication

The version of Veeam Backup & Replication must be the same or newer than version of Veeam Plug-in. Veeam
Plug-in for SAP on Oracle version 11 is compatible with Veeam Backup & Replication 11 or later.

179 | Veeam Plug-ins for Enterprise Applications | User Guide

Required Permissions
User Rights on the SAP on Oracle Server
The account used for installing and updating Veeam Plug-in must have root privileges.

User That Starts BR*Tools Operations

The account used to start BR*Tools backup and restore operations must have permissions described in the
Starting BR*Tools section of the SAP Database Guide: Oracle.

Veeam Backup Server User

• The account specified in the Veeam Plug-in configuration settings must be able to authenticate against
the Veeam Backup & Replication server. For details, see Configuring Veeam Plug-in for SAP on Oracle.

• The account specified in the Veeam Plug-in configuration settings must be granted access rights on the
Veeam backup repository where you want to store backups.

To learn how to grant permissions on Veeam repositories, see Granting Permissions on Repositories.

• You can work with backups created by Veeam Plug-in only with the account used for creating the backups.
If you want to use another account, see required permissions in Configuring Veeam Plug-in for SAP on
Oracle.

180 | Veeam Plug-ins for Enterprise Applications | User Guide

Used Ports
To enable proper work of Veeam Plug-ins, make sure that the following ports are open.

SAP on Oracle Server

The following table describes network ports that must be opened to ensure proper communication of the SAP
on Oracle server and backup infrastructure components.

From To Protocol Port Notes

Default port used for communication with

Veeam the Veeam Backup & Replication server.
Backup & Note that data between Veeam Plug-ins
SAP on TCP 10006
Replication and backup repositories is transferred
Oracle server directly, bypassing the Veeam Backup &
server
Replication server.
where
Veeam
Plug-in is Backup
installed Default range of ports used as data
repository
2500 to transmission channels. For every TCP
server or TCP
3300** connection that a backup process uses,
gateway
one port from this range is assigned.
server*

* For NFS share, SMB share repositories, and Dell EMC Data Domain, HPE StoreOnce deduplication storage appliances,
Veeam Backup & Replication uses an auxiliary backup infrastructure component — gateway server. For details, see the
Gateway Server section of the Veeam Backup & Replication User Guide.
** This range of ports applies to newly added backup infrastructure components. If you upgrade to Veeam Backup &
Replication 10.0 from earlier versions of the product, the range of ports from 2500 to 5000 applies to the already added
components.

Backup Repositories and Gateway Servers

Depending on the type of backup repositories that you use for Veeam Plug-in backups, the following ports must
be open to allow communication between backup infrastructure components.

From To Protocol Port Notes

Direct Attached Storage

Linux server
Veeam used as a
Port used as a control channel from the
Backup & backup
TCP 22 Veeam Plug-in server to the target Linux
Replication repository or
host.
server gateway
server

181 | Veeam Plug-ins for Enterprise Applications | User Guide

 From To Protocol Port Notes

Microsoft Ports used as a management channel from

TCP 135, 137 to the Veeam Plug-in server to the
Windows
server used UDP 139, 445 Repository/Gateway server. Also, the ports
as a backup are used to deploy Veeam components.
repository or
gateway Default ports used by the Veeam Installer
server TCP 6160, 6162
Service and Veeam Data Mover Service

Network Attached Storage

Gateway Default port used by the SMB transport

TCP 445
server protocol.

(specified in
the SMB SMB server SMB/Netbios name resolution for the SMB
share TCP 135, 137 to protocol (needed in some cases). For
repository UDP 139 details, see the Used Ports section of the
settings) Veeam Backup & Replication User Guide.

Gateway
server

(specified in TCP Standard NFS ports used as a transmission

the NFS NFS server 111, 2049 channel from the gateway server to the
UDP target NFS share.
share
repository
settings)

Dell EMC Data Domain

Port used to assign a random port for the

mountd service used by NFS and
TCP 111
DDBOOST. Mountd service port can be
statically assigned.
Veeam Dell EMC
Backup & Data Domain Main port used by NFS. To change the
Replication
port, you can use the ‘nfs set server-
server For more TCP 2049
port’ command. Note that the command
or information,
see Dell EMC requires SE mode.
Gateway
server Documents.
Main port used by NFS MOUNTD. To
change the port, you can use the 'nfs
TCP 2052
set mountd-port' command. Note
that the command requires SE mode.

HPE StoreOnce

182 | Veeam Plug-ins for Enterprise Applications | User Guide

 From To Protocol Port Notes

Veeam Default command port used for

9387
Backup & communication with HPE StoreOnce.
Replication
HPE
server TCP
StoreOnce
or Default data port used for communication
Gateway 9388
with HPE StoreOnce.
server

ExaGrid

Veeam
Backup & Default command port used for
ExaGrid TCP 22
Replication communication with ExaGrid.
server

Quantum DXi

Veeam
Backup & Default command port used for
Quantum DXi TCP 22
Replication communication with Quantum DXi.
server

For detailed list of ports used by Veeam Backup & Replication server and backup repositories, see the Used Ports
section of the Veeam Backup & Replication User Guide.

183 | Veeam Plug-ins for Enterprise Applications | User Guide

Licensing
To use the Veeam Plug-in functionality, you must have a valid Veeam Backup & Replication license. Licenses are
installed and managed on the Veeam Backup & Replication server that is connected to the Veeam Plug-in server.
If the license is not valid or out of resources, Veeam Plug-in backup jobs fail.

This guide provides information only on specifics of Veeam licenses for Veeam Plug-ins. For terminology and
general information about Veeam Licensing, see Veeam Licensing Policy.

In this section:

• Licensed Objects

• Supported License Types and Packages

• Obtaining and Managing Licenses

Licensed Objects
An SAP on Oracle server is assumed protected if it has been processed by a Veeam Plug-in backup job in the last
31 days.

If you are using any instance-based (Veeam Universal Licensing) license on your Veeam Backup & Replication,
you don't need to install any additional licenses.

A protected SAP on Oracle server consumes one instance unit from the license. SAP on Oracle servers processed
by backup copy jobs are not regarded as protected VMs, these types of jobs provide an additional protection
level for VMs that are already protected with Veeam Plug-in backup jobs.

A machine protected by both Veeam Plug-in and Veeam Backup & Replication will consume a license only once.
For example, you have an SAP on Oracle server that you back up using Veeam Plug-in. You also back up this
server using image-level backup functionality of Veeam Backup & Replication. In this case, only one license will
be consumed.

NOTE

[For Perpetual per-socket licenses] If you are using a legacy perpetual per-socket license, a license is
required for each hypervisor CPU socket occupied by protected SAP on Oracle servers.

A socket is consumed from the license only if the hypervisor where protected servers reside is added to the
Veeam Backup & Replication infrastructure. If the hypervisor is not added to the Veeam Backup &
Replication infrastructure, an instance unit will be consumed from the license. To learn how to add a
hypervisor to the Veeam Backup & Replication infrastructure, see the Virtualization Servers and Hosts
section of the Veeam Backup & Replication User Guide.

Supported License Types and Packages

You can use Veeam Plug-ins with the following license types and packages. Note that this guide contains
information on peculiarities of Veeam license packages only for Veeam Plug-ins. For the full list of license
packages, see Pricing and Packaging.

• For Veeam Universal Licensing:

You can use Veeam Plug-ins with all license packages (Veeam Backup Essentials, Veeam Backup &
Replication, Veeam Availability Suite).

184 | Veeam Plug-ins for Enterprise Applications | User Guide

 Note that if you use the Rental license type, functionality of Veeam Plug-ins is supported only for the
Enterprise Plus edition of Veeam Backup & Replication.

• For Perpetual Socket license:

Functionality of Veeam Plug-ins is supported only for the Enterprise Plus edition of Veeam Backup &
Replication.

Obtaining and Managing Licenses

To learn how to install a license and monitor licensed objects, see the Licensing section in the Veeam Backup &
Replication User Guide.

185 | Veeam Plug-ins for Enterprise Applications | User Guide

Environment Planning
Integration of SAP on Oracle and Veeam Plug-in requires additional environment planning. When you deploy the
plug-in, keep in mind the following requirements and limitations.

Scheduling
You can schedule backup processes using Cron.

Also, you can schedule and run existing SAP BR*Tools backup scripts within image-level or file-level backup job
of Veeam Backup & Replication or Veeam Agent. For details, see the Pre-Freeze and Post-Thaw Scripts section
of the Veeam Backup & Replication.

Veeam Backup & Replication Users and Roles

Veeam Plug-in for SAP on Oracle uses the Windows authentication methods of the Veeam Backup & Replication
server to establish a connection to this server and to the backup target.

If this user will be later changed manually, the new user must have at least the Veeam Backup Operator and
Veeam Restore Operator rights within the Veeam Backup & Replication user management. To learn how to
assign Veeam Backup & Replication roles, see the Roles and Users section of the Veeam Backup & Replication
User Guide.

Parallel Data Streams and Backup Repository Task Slots

Any parallel data stream started by SAP Backint will use one backup repository task slot. It is recommended to
carefully plan repository task slots, so that SAP Backint can work with multiple channels in parallel.

The following hardware resources are recommended based on tests on Skylake processors:

• SAP on Oracle server: 1 CPU core and 200 MB of RAM per currently used channel. Note that resource
consumption on the SAP on Oracle server depends on hardware and Oracle settings.

• Backup repository server: 1 CPU core and 1 GB of RAM per 5 currently used channels.
These resources are recommended only if you use a dedicated backup repository for Veeam Plug-in
backups. If you use the same backup repository for Veeam Plug-in backups and VM backups created by
Veeam Backup & Replication or Veeam Agents, consider adding the mentioned above hardware resources
based on usual load on your backup repository. For details on hardware requirements for a backup
repository, see the System Requirements section of the Veeam Backup & Replication User Guide.
It is recommended to contact your Veeam system engineer to optimize the channel settings and resource
allocation.
It is recommended to use a separate backup repository for Veeam Plug-in backups.

• Veeam Backup & Replication server: during manual metadata operations such as import of backup files,
the Veeam Backup & Replication server needs additional 15 GB of RAM per 1 million files located in the
same backup job folder.

186 | Veeam Plug-ins for Enterprise Applications | User Guide

Backup Files
Veeam Plug-in stores backup files in the following formats:

• A .VAB file stores compressed and deduplicated copy of an Oracle database. Veeam Plug-in creates VAB
files for both full and incremental backups.

• A .VASM file stores metadata that contain information about the backup. A .VASM file is created for each
.VAB file. The .VASM files are used by Veeam Backup & Replication to get data about Veeam Plug-in
backups.

• A .VACM file stores metadata of a backup job object.

Veeam Plug-in generates a name for a .VAB backup file and stores up to 1000 FIB's (file in backup) in one .VAB
file. The FIB file names match the external backup ID's (EBID) generated by Veeam Plug-in during the backup.

Also, for each backup file, Veeam Plug-in creates a metadata file that has the same name as the backup file but
a different extension (.VASM).

187 | Veeam Plug-ins for Enterprise Applications | User Guide

Backup Repositories Planning
Veeam Plug-ins store backup files in repositories added to the Veeam Backup & Replication infrastructure. In
this section, you can find the list of supported backup repositories and limitations for Veeam Plug-in backups.

Supported Backup Repositories

Veeam Plug-in for SAP HANA supports integration with the following types of repositories added to the Veeam
Backup & Replication infrastructure:

• Windows Server

• Linux Server

• CIFS (SMB) Share

• Dell EMC Data Domain Boost

• Quantum DXi

• ExaGrid

• HPE StoreOnce. If you plan to use HPE StoreOnce as a backup repository for Veeam Plug-in backups, the
total number of stored files (data and metadata) must not exceed 1,000,000 per storage system.

• NFS File Share

You can also use scale-out backup repositories that contain repositories supported by Veeam Backup &
Replication.

Backup Repositories Limitations

• The plug-in configuration wizard will not show repositories where the Encrypt backups stored in this
repository option is enabled. To learn how to disable the encryption option, see Access and Encryption
Settings on Repositories.
If you want to use the same backup target with the repository-based encryption and Veeam Plug-ins,
create a second repository in the subfolder for Veeam Plug-in backups.

• Veeam extract utility cannot extract Veeam Plug-in backup files.

Veeam Scale-Out Backup Repositories

If you want to store Veeam Plug-in backups in the scale-out backup repositories, mind the following:

• If you want to migrate backup repositories to a scale-out backup repository and Veeam Plug-in backups
are present on the repository, you must do the following:

a. Transfer the folders that include backups to an existing scale-out backup repository extent.

b. Rescan the scale-out backup repository.

c. Set the scale-out backup repository as a target in the Veeam Plug-in settings.

d. Rescan the repository that you want to add.

e. Migrate the repository to the scale-out backup repository.

188 | Veeam Plug-ins for Enterprise Applications | User Guide

 • For Veeam Plug-in backups and backup copies, the Performance policy of a scale-out repository functions
a little differently:

a. Veeam Backup & Replication checks if there are extents without warning on free space insufficiency. If
all extents have the warning, Veeam Backup & Replication uses an extent with the largest amount of
free space that has a free task slot.

b. If there are extents without the warning, Veeam Backup & Replication checks if there are incremental
extents with free task slots. If there are no incremental extents with free task slots, Veeam Backup &
Replication uses a full extent with least amount of used task slots.

c. If there are incremental extents with free task slots, Veeam Backup & Replication will send backup
files to an incremental extent with least amount of used task slots. If the amount of used tasks is the
same, an extent with the most amount of free space.
To learn more about file placement policies of scale-out repositories, see Backup File Placement section of
the Veeam Backup & Replication guide.

• If a scale-out repository is configured in the Data locality policy, each time BR*Tools starts a new channel
for transferring backup files, Veeam Plug-in checks the free space in the extents and selects a scale-out
backup repository extent that has the largest amount of free space. If there are two extents with one slot
on each extent, the backup will be launched in two parallel streams (one on each extent).

Capacity Tier
You can configure Veeam Backup & Replication to transfer Veeam Plug-in backup files to a capacity tier. Both
policies (Move policy, Copy policy) are supported for Veeam Plug-in backups with the following limitations:

• For Veeam Plug-in backup files, capacity tier does not verify whether data that is being moved is unique
and has not been offloaded earlier. Thus, it is highly recommended to check the pricing plans of your
cloud storage provider to avoid additional costs for offloading and downloading backup data.

• Capacity tier does not track dependencies of full and incremental Veeam Plug-in backup files. Thus, mind
the following:

o [For the Move policy] When backup files are transferred to the capacity tier, Veeam Backup &
Replication takes into account only the creation time of backup files. Make sure that the
operational restore window is not longer than the whole backup chain cycle period. Otherwise, you
may encounter the scenario when full backup files are transferred to the capacity tier and their
increment backup files still remain in the performance tier.

o The capacity tier immutability expiration date does not have the additional block generation period.
The immutability expiration date is based only on the number of days specified in settings of the
object storage backup repository.

• If a scale-out repository is down, you cannot restore from the Veeam Plug-in backup files stored on the
capacity tier. In this case, you can only import the backup files manually and then perform the data
recovery operations.

189 | Veeam Plug-ins for Enterprise Applications | User Guide

Access and Encryption Settings on Repositories
When you configure Veeam Plug-in, you specify an account that must be used to connect to the Veeam Backup
& Replication server. To be able to store backups on a backup repository, the specified account must have access
permissions on the target backup repository.

To grant access permissions, do the following:

1. In Veeam Backup & Replication, open the Backup Infrastructure view.

2. In the inventory pane, click the Backup Repositories node or the Scale-out Repositories node.

3. In the working area, select the necessary backup repository, click Set Access Permissions on the ribbon or
right-click the backup repository and select Access permissions.

4. In the Access Permissions window, specify to whom you want to grant access permissions on this backup
repository:

o Allow to everyone — select this option if you want to grant repository access to any user. This option
is equal to granting access rights to the Everyone group in Microsoft Windows (anonymous users are
excluded). For security reasons, the option is not recommended for production environments.

o Allow to the following accounts or groups only — select this option if you want only specific users to
be able to store backups on this repository. Click Add to add the necessary users and groups to the
list.

190 | Veeam Plug-ins for Enterprise Applications | User Guide

 5. Veeam Plug-ins cannot send backups or backup copies to a repository where encryption is enabled. Thus,
unselect the Encrypt backups stored in this repository check box.

191 | Veeam Plug-ins for Enterprise Applications | User Guide

Deployment and Configuration
To deploy Veeam Plug-in, you must install the plug-in on a SAP on Oracle server and configure plug-in
integration settings. In this section:

• Installing Veeam Plug-in for SAP on Oracle

• Configuring Veeam Plug-in for SAP on Oracle

• Importing Backups

• Uninstalling Veeam Plug-in for SAP on Oracle

This guide gives instructions on how to deploy Veeam Plug-in assuming that you have already deployed a
Veeam Backup & Replication server and configured a backup repository. If you need instructions on how to
deploy Veeam Backup & Replication, see the Veeam Backup & Replication User Guide for your platform.

192 | Veeam Plug-ins for Enterprise Applications | User Guide

Installing Veeam Plug-in for SAP on Oracle
Veeam Plug-in for SAP on Oracle is an additional component of Veeam Backup & Replication, and the
installation package of the plug-in is included in the Veeam Backup & Replication installation ISO file. You must
install the plug-in on the Oracle Database server.

To install Veeam Plug-in, do the following:

1. Mount the Veeam Backup & Replication installation ISO file.

If you deploy Veeam backup infrastructure for the first time, you can download Veeam Backup &
Replication at: https://www.veeam.com/backup-replication-vcp-download.html.

2. In the mounted ISO, go to /Plugins/SAP on Oracle/x64. You can install the plug-in using the RPM
package. Note that the install operations in the terminal of the Linux machine require root privileges.

3. You can install the plug-in using the RPM package or .TAR.GZ bundle. Do one of the following, depending
on the type of package suitable for your OS. Note that operations in the terminal of the Linux machine
require root privileges.

o To install from the RPM package:

i. Upload the VeeamPluginforSAPOracle-XX.X.X.XXX.x86_64.rpm file to the Oracle

Database server.

ii. Run the following command to install the plug-in:

rpm -i VeeamPluginforSAPOracle-XX.X.X.XXX.x86_64.rpm

o To install from the TAR.GZ bundle:

i. Upload the VeeamPluginforSAPOracle.tar.gz file to the Oracle Database server.

ii. Create the /opt/veeam directory.

mkdir /opt/veeam

iii. Unpack the bundle to the /opt/veeam directory:

tar -xzvf -i VeeamPluginforSAPOracle.tar.gz -C /opt/veeam

193 | Veeam Plug-ins for Enterprise Applications | User Guide

Configuring Plug-in for SAP on Oracle
When you configure Veeam Plug-in settings, you set up integration settings between the SAP on Oracle server,
Veeam Backup & Replication server and backup repositories where backup files will be stored.

Veeam Plug-in uses the SapOracleBackintConfigTool wizard to configure the integration settings. The wizard
searches for all SAP on Oracle systems deployed on the server and creates the veeam_initSID.sap file for
each system. Then, this file is used as an initialization profile for brbackup, brrestore and brarchive tools.

Depending on which version of Oracle Database is used, Veeam Plug-in stores the configuration file in the
following directories.

• For Oracle 12 and later, the configuration file is stored at SAPDATA_HOME/sapprof.

• For Oracle 11, the configuration file is stored at ORACLE_HOME/dbs.

IMPORTANT

In some cases when Oracle Database and SAP central instance are running on different hosts, Veeam Plug-
in may not be able to detect SAP instances during the configuration. In this case, you must perform the
following:

1. Complete all the steps of the Veeam Plug-in configuration wizard described in this section. As a
result, Veeam Plug-in will create a new veeam_initSID.sap initialization profile and save it in the
/tmp/ directory.
2. Manually copy all lines from the new initialization profile to the default initialization profile. Or you
can specify the path to the veeam_initSID.sap file in each BRBACKUP, BRRESTORE and
BRARCHIVE command.

Veeam Plug-in Configuration

To configure Veeam Plug-in, do the following. Note that the configuration of Veeam Plug-in must be performed
by a user with database administrator rights on the Oracle Database server:

1. Log in to the Oracle Database server as a user with database administrator rights and run the following
command to launch the Veeam Plug-in configuration tool. You do not need root privileges if you have
configured group access as described in the Required Permissions section.

sudo SapOracleBackintConfigTool --wizard

2. Specify the DNS name or IP address of the Veeam Backup & Replication server that you want to use.

Enter backup server name or IP address: serv02.tech.local

3. Specify the port which will be used to communicate with the Veeam Backup & Replication server. Default
port: 10006.

Enter backup server port number: 10006

194 | Veeam Plug-ins for Enterprise Applications | User Guide

 4. Specify credentials to authenticate against the Veeam Backup & Replication server.

Enter username: serv02\administrator

Enter password for serv02\administrator:

IMPORTANT

You can work with backup files created by Veeam Plug-in only with the account that was used to
create the backups. If you want to use another account, assign the Veeam Backup Administrator role
or the Veeam Backup Operator and Veeam Restore Operator roles to the account.

To learn how to assign Veeam Backup & Replication roles, see the Roles and Users section of the
Veeam Backup & Replication Guide.

5. Select a backup repository where you want to store backups.

In the wizard dialog, you will see a list of available repositories. Enter the number of the target repository
from the list.

Available backup repositories:

1. serv10_repo
2. serv07_repo
Enter repository number: 1

IMPORTANT

Mind the following:

• The account used to connect to the Veeam Backup & Replication server must have access to
the target backup repositories.
• Encryption must be disabled on the target backup repositories.

Otherwise, backup repositories will not be listed as available. To learn how to configure access and
encryption settings on repositories, see Access and Encryption Settings on Repositories.

6. Specify the number of parallel data streams for each backup repository.

Enter number of data streams (From 1 to 32) to run in parallel: 4

Configuration result:
An auxiliary initialization profile has been successfully created for SAP
system "ODB": /oracle/ODB/sapprof/veeam_initODB.sap
The created profile must be leveraged to perform backup and restore tasks
by BR*Tools.

Note that this parallelism setting applies only to backup and restore of Oracle datafiles. If you want to
configure parallel channels for backup and restore of redo logs, see Configuring Parallelism for Redo Logs.

Configuration Tool Commands

Apart from running a configuration wizard, you can use the SapOracleBackintConfigTool tool to change a
specific parameter in the veeam_config.xml file or enable/disable Veeam Plug-in features.

195 | Veeam Plug-ins for Enterprise Applications | User Guide

See the list of available commands for SapOracleBackintConfigTool:

Command Description

--help Shows the list of tool parameters.

--show-config Shows configuration parameters.

--wizard Starts the wizard to configure the plug-in settings. This wizard edits the
veeam_config.xml file or creates a new one if the configuration file was
removed from the /opt/veeam/VeeamPluginforSAPOracle/ directory.

--set-credentials Specifies credentials to log in to the Veeam Backup & Replication server.
<"serv\username">
<password>

--set-host <hostname> Specifies the IP address or hostname of the Veeam Backup & Replication
server.

--set-port <port_number> Specifies a port number that will be used to communicate with the Veeam
Backup & Replication server.

--set-repository Launches a wizard to select a backup repository. A backup repository is

selected from repositories which are available in the connected Veeam Backup
& Replication instance.

--set-restore-server [for System Copy] Specifies the backup that will be copied.

--set-parallelism Define the number of parallel channels that must be used to transfer Oracle
<number_of_channels> datafiles during the backup and restore operations.

You can set up to 32 channels.

Note that the parallelism for redo logs is configured separately. For details, see
Configuring Parallelism for Redo Logs.

--map-backup Maps the imported backup.

--set-force-delete Deletes backup files after specified days.

--configure-restore-from- Enables restore from backup copy. Note that if you enable restore from backup
copy copy, you cannot back up databases with Veeam Plug-in. To revert changes,
you must disable restore from backup copy.

Note that when you launch the command, the wizard will ask you to
reconfigure the catalog backup from backint to disk.

196 | Veeam Plug-ins for Enterprise Applications | User Guide

 Command Description

--promote-backup-copy- Maps the imported backup copy to a regular Veeam Plug-in backup chain.
to-primary

Example:
The following example shows how to specify credentials that will be used to log in to the Veeam Backup &
Replication server.

SapOracleBackintConfigTool --set-credentials "serv02\Administrator" "password"

197 | Veeam Plug-ins for Enterprise Applications | User Guide

Configuring Parallelism for Redo Logs
To configure backup or restore of redo logs through multiple channels, you can change the parallelism
parameter in the veeam_config.xml file.

1. In the machine where Veeam Plug-in is installed, go to the /opt/veeam/VeeamPluginforSAPOracle/

directory and open the veeam_config.xml file with a text editor.

2. Set the necessary values for the parallelism values:

<PluginParameters Parallelism="4" LogsParallelism="4" />

where the LogsParallelism parameter value defines the number of parallel channels for backup and
restore of redo logs.
Note that the first Parallelism value configures the parallelism for backup and restore of Oracle
datafiles. This setting is configured in the Veeam Plug-in configuration wizard.

198 | Veeam Plug-ins for Enterprise Applications | User Guide

Importing Backups
Importing backup files can be helpful if the Veeam Backup & Replication configuration database is corrupted or
if you want to import Veeam Plug-in backup files to another backup repository.

To import Veeam Plug-in backup files to another backup repository, do the following:

1. Copy the folder that contains backup files to the target backup repository connected to Veeam Backup &
Replication.

2. Use the Veeam Backup & Replication console to log on to target Veeam Backup & Replication.

3. Open the Backup Infrastructure view.

4. In the inventory pane of the Backup Infrastructure view, select the Backup Repositories node.

5. In the working area, select the required backup repository and click Rescan on the ribbon. Alternatively,
you can right-click the backup repository and select Rescan.

6. On the SAP on Oracle server, change the target backup repository in the Veeam Plug-in settings:

sudo SapOracleBackintConfigTool --set-repository

Available backup repositories:
1. serv10_repo
2. serv07_repo
Enter repository number: 1
Configuration result:
SID SH2 has been configured

199 | Veeam Plug-ins for Enterprise Applications | User Guide

 7. Run the --map-backup command:

sudo SapOracleBackintConfigTool --map-backup

IMPORTANT

If backup files are not imported according to instructions given above, the backup and restore processes
can fail.

200 | Veeam Plug-ins for Enterprise Applications | User Guide

Uninstalling Plug-in for SAP on Oracle
To uninstall Veeam Plug-in for SAP on Oracle, go to the directory with the Veeam Plug-in installation package
and run the following command. Note that the operation requires root privileges.

rpm -e VeeamPluginforSAPOracle

201 | Veeam Plug-ins for Enterprise Applications | User Guide

Database Protection
After you configure Veeam Plug-in for SAP on Oracle, you can back up databases using SAP BR*Tools. Veeam
Plug-in will automatically transfer backup files to a backup repository and store them in the Veeam proprietary
format. The backup process itself is performed by SAP BR*Tools.

Keep in mind that examples in this section are provided only for demonstrating purposes. For details on full
backup functionality of SAP BR*Tools, see the BR*Tools for Oracle DBA Guide.

In this section

• Backing Up Databases Using BRBACKUP

• Backing Up Databases Using BRBACKUP with rman_util

• Backing Up Redo Logs

• Backup Job in Veeam Backup & Replication Console

NOTE

This guide contains examples of SAP BR*Tools commands. Apart from BR*Tools scripts, you can perform
backup operations using BRTOOLS interactive wizard and BR*Tools Studio. For details, see the Backing Up
the Databases with BR*Tools section of the SAP Database Guide: Oracle.

202 | Veeam Plug-ins for Enterprise Applications | User Guide

SAP on Oracle Full Backup
Veeam Plug-in for SAP on Oracle integrates with the BRBACKUP tool and transfers backup files to backup
repositories connected to Veeam Backup & Replication. The backup process itself is performed by the
BRBACKUP tool. To perform the backup you can use BR*TOOLS or BR*TOOLS Studio.

For details on how the backup is performed, see How Veeam Plug-in for SAP on Oracle Works.

IMPORTANT

Mind the following limitations:

• ASM is supported only with the rman_util parameter. If you want to back up ASM instances, see
SAP on Oracle Backup (RMAN_UTIL).
• RAC backup is not supported.
• Volume backup (-d util_vol, util_vol_online) is not supported.
• Backup of directories is not supported.
• If you remove backups from the primary storage, they will also be removed from cloud.

To back up Oracle databases, you can use the interactive wizard of BRTOOLS or you can directly run the backup
command using BRBACKUP. For details, see the following guides.

Performing SAP on Oracle Full Backup Using BRBACKUP

When you back up the database using the BRBACKUP tool, it uses the Veeam Plug-in configuration file as an
initialization profile.

Examples
The following examples are only for demonstration purposes. To see the description of all BRBACKUP
parameters, see the Backing Up the Database with BR*Tools for Oracle DBA Guide.

Example 1. Performing Full Database Backup in Offline Mode

brbackup -p $Oracle_HOME/dbs/veeam_initSID.sap -d util_file -t offline_force -m

all

Run the brbackup command with the following parameters:

1. Specify the path to the initialization profile file ($Oracle_HOME/dbs/veeam_initSID.sap) as the

argument for the -p (-profile) parameter.

2. Specify util_file as the argument for the -d (-device) parameter. This option defines that a file-by-
file backup will be performed using Veeam Plug-in.

3. Specify offline_force as the argument for the -t (-type) parameter. With this option, BRBACKUP
shuts down the database and performs an offline backup.

4. Specify all as the argument for the -m (-mode) parameter. With this option, BRBACKUP performs backup
of files in all tablespaces, but not the control files and online redo log files.

203 | Veeam Plug-ins for Enterprise Applications | User Guide

Example 2. Performing Full Database Backup in Online Mode

brbackup -p $Oracle_HOME/dbs/veeam_initSID.sap -d util_file_online -t online -m

all

Run the brbackup command with the following parameters:

1. Specify the path to the initialization profile file ($Oracle_HOME/dbs/veeam_initSID.sap) as the

argument for the -p (-profile) parameter.

2. Specify util_file_online as the argument for the -d (-device) parameter.

3. Specify all as the argument for the -m (-mode) parameter. With this option, BRBACKUP performs backup
of files in all tablespaces, but not the control files and online redo log files.

4. Specify credentials that must be used to connect to the database as the argument for the -u (-user)
parameter.

IMPORTANT
When you use BRBACKUP, you must specify the full directory path to the Veeam Plug-in initialization
profile file (-p $Oracle_HOME/dbs/veeam_initSID.sap). If the profile file is in the default directory,
you can specify only the file name.

204 | Veeam Plug-ins for Enterprise Applications | User Guide

SAP on Oracle Incremental Backup
Perform an incremental backup by using the BRBACKUP command with the rman_util parameter.

An incremental backup contains the changed data from the last full backup. Incremental backups use less media
and resources than full backups.

To see all brbackup command options, see the Command Options for BRBACKUP section of the SAP Database
Guide: Oracle.

NOTE

You can make incremental backups only with the rman_util parameter. For details, see the RMAN Backup
Strategies section of the SAP Database Guide: Oracle.

Example: Performing Incremental Backup in Online Mode

brbackup -p $Oracle_HOME/dbs/veeam_initSID.sap -t online -d rman_util -m incr -

u <user>/<password>

Run the brbackup command with the following parameters:

1. Specify the path to the initialization profile file ($Oracle_HOME/dbs/veeam_initSID.sap) as the

argument for the -p (-profile) parameter.

2. Specify online_force as the argument for the -t (-type) parameter. With this option, BRBACKUP
performs backup of the database in the online state.

3. Specify util_file as the argument for the -d (-device) parameter.

4. Set incr as the argument for the -m (-mode) parameter.

5. Specify credentials that must be used to connect to the database as the argument for the -u (-user)
parameter.

205 | Veeam Plug-ins for Enterprise Applications | User Guide

SAP on Oracle Backup (RMAN_UTIL)
The rman_util parameter allows to back up Oracle databases using Oracle RMAN in combination with Veeam
Plug-in for Oracle RMAN. BACKINT provides an interface for Veeam Plug-in for Oracle RMAN and is also used to
back up profiles, log files and control files.

For full description of the rman_util parameter, see RMAN Backup with an External Backup Library.

In the Veeam Backup & Replication console, the rman_util backup operation will create two backup jobs:
Veeam Plug-in for Oracle RMAN backup job for database file backups and another Veeam Plug-in for SAP on
Oracle backup job that backups up BR*Tools control data files. Note that if you want to create a backup copy job
for SAP on Oracle database, make sure that you have added both jobs to the backup copy job.

Prerequisites

IMPORTANT

Before you back up the Oracle database with the rman_util parameter, you must install and configure
Veeam Plug-in for Oracle RMAN on the SAP on Oracle server.

When you perform the backup using the RMAN_UTIL, RMAN_STAGE or RMAN_DISK parameter, by default,
BR*Tools creates one backup set for each log or datafile. This means that every backup piece will contain only
one file. This results in a large amount of backup files and significantly slows down backup and restore
processes. To avoid this problem, do the following:

1. In the SAP on Oracle server, open the /oracle/ODB/sapprof/veeam_initSID.sap file using a text
editor.

2. Change the default values for the following parameters:

rman_filesperset = 10
rman_filesperset_arch = 100

For example: set the rman_filesperset value to 10 for datafiles and the rman_filesperset_arch
value to 100 for logs.

Also, you must add the SBT_LIBRARY directory to the rman_parms setting in the veeam_initSID.sap file:

1. In the SAP on Oracle server, open the /oracle/ODB/sapprof/veeam_initSID.sap file using a text
editor.

2. Add the following line in the veeam_initSID.sap file:

rman_parms = 'SBT_LIBRARY=/opt/veeam/VeeamPluginforOracleRMAN/libOracleRMA
NPlugin.so'

How It Works
When you launch the BRBACKUP or BRARCHIVE tool with the RMAN_UTIL parameter, the following happens:

1. SAP BR*Tools launches the RMAN backup script.

2. Oracle RMAN launches Veeam Plug-in for Oracle RMAN services.

206 | Veeam Plug-ins for Enterprise Applications | User Guide

 3. Oracle RMAN starts the backup process:

a. Veeam Plug-in compresses, deduplicates database backup files or redo logs and sends them to the
target backup repository through one or multiple channels.

b. Veeam Plug-in for Oracle RMAN connects to Veeam Backup & Replication and creates a backup job
object that shows the job progress and logs.

4. BR*Tools launches the Veeam Plug-in for SAP on Oracle services.

5. BR*Tools start the control data files backup:

a. Control file, BR*Tools logs are compressed and sent to a backup repository.

b. Veeam Plug-in for SAP on Oracle connects to Veeam Backup & Replication and creates a backup job
object that shows the job progress and logs.

Example: Performing Full Backup with RMAN_UTIL Parameter

To backup an SAP on Oracle database using RMAN, you must use the brbackup tool with the rman_util
parameter and with the defined directory for SBT library.

brbackup -p $Oracle_HOME/dbs/veeam_initSID.sap -t online -d rman_util -m full -

u /

1. Specify the path to the initialization profile file (veeam_initSID.sap) as the argument for the -p (-
profile) parameter.

2. Specify rman_util as the argument for the -d (-device) parameter. This option defines that the backup
will be performed using Oracle RMAN.

3. Specify online as the argument for the -t (-type) parameter. With this option, BRBACKUP performs
backup of the database in the online state.

4. Specify full as the argument for the -m (-mode) parameter. With this option, BRBACKUP performs
backup of files in all tablespaces, control files and redo log files.

207 | Veeam Plug-ins for Enterprise Applications | User Guide

 5. Specify / as the argument for the -u (-user) parameter. With this option BRBACKUP uses the $OPS
user to log on to the database.

For the fill list of BRBACKUP parameters, see the Command Options for BRBACKUP section of the SAP Database
Guide: Oracle.

208 | Veeam Plug-ins for Enterprise Applications | User Guide

SAP on Oracle Redo Logs Backup
If you want to back up redo log files of Oracle databases, you can use the BRARCHIVE tool. When Veeam Plug-in
for SAP on Oracle is configured, the plug-in transfers the redo logs to a backup repository connected to Veeam
Backup & Replication.

NOTE

For redo log backup operations, it is recommended to set 4 or less parallel channels. For details on
configuring parallel channels, see Configuring Parallelism.

Example: Performing Backup of Archived Redo Logs

To back up redo log files, run the following command.

brarchive -p $Oracle_HOME/dbs/veeam_initSID.sap -save -d util_file -u /

1. Specify the path to the initialization profile file ($Oracle_HOME/dbs/veeam_initSID.sap) as the

argument for the -p (-profile) parameter.

2. Specify util_file as the argument for the -d (-device) parameter. This option defines that a file-by-
file backup will be performed using Veeam Plug-in.

3. Specify / as the argument for the -u (-user) parameter. With this option BRBACKUP uses the $OPS
user to log on to the database.

209 | Veeam Plug-ins for Enterprise Applications | User Guide

Backup Job in Veeam Backup & Replication
Console
After you start a backup process with BRBACKUP, Veeam Backup & Replication creates a backup job object. You
can use this job to view the statistics on the backup process, generate backup job reports or you can also disable
the backup job.

You cannot launch or edit SAP on Oracle backup job objects in the Veeam Backup & Replication console. You can
manage backup operations only on the SAP on Oracle side using BR*Tools.

NOTE

Due to specifics of the SAP on Oracle backup process, the progress bar of a running SAP on Oracle backup
job is not available.

To view details of a backup job process, do the following.

1. Open the Veeam Backup & Replication console.

2. In the Home view, expand the Jobs node and click Backup.

3. In the list of jobs, select the BR*Tools backup job to see details of the current backup process or the last
backup job session.

210 | Veeam Plug-ins for Enterprise Applications | User Guide

Generating Backup Job Reports
You can generate reports with details about an BR*Tools backup job session performance. The session report
contains the following session statistics: session duration details, details of the session performance, amount of
read, processed and transferred data, backup size, compression ratio, list of warnings and errors (if any).

1. Open the Home view.

2. In the inventory pane, select Jobs.

3. In the working area, select the necessary job and click Report on the ribbon. You can also right-click the
job and select Report.

Disabling Backup Job

You can disable BR*Tools backup jobs in the Veeam Backup & Replication console. If you disable the job, you
will not be able to run BR*Tools backup commands on the SAP on Oracle server.

To disable a backup job:

1. Open the Home view.

2. In the inventory pane, select Jobs.

3. In the working area, select the necessary job and click Disable on the ribbon. You can also right-click the
job and select Disable.

211 | Veeam Plug-ins for Enterprise Applications | User Guide

Database Recovery
With the configured Veeam Plug-in you can restore Oracle databases from the backups that reside on backup
repositories. All restore operations are performed on the SAP BR*Tools side.

Keep in mind that examples provided in this section are for demostration purposes only. To see the full restore
functionality of SAP BR*Tools, see the BR*Tools for Oracle DBA Guide.

To learn how to recover Oracle databases from backups created by Veeam Plug-in for SAP on Oracle, see:

• Restoring Oracle Databases

• Restoring Redo Logs

• Recovering Databases to Other Servers (System Copy)

• Restore from Backup Copy

212 | Veeam Plug-ins for Enterprise Applications | User Guide

Oracle Databases Restore
Veeam Plug-in for SAP on Oracle allows to restore databases using the BRRESTORE tool functionality. When you
launch the restore, BRRESTORE restores the selected database from backup files stored on the backup
repository.

By default, BRRESTORE uses the initSID.sap initialization profile. Thus, you must specify the -p
$Oracle_HOME/dbs/veeam_initSID.sap parameter in the restore commands.

For details on all restore options, see the Command Options for BRRESTORE section of the SAP DATABASE
Guide: Oracle.

Example: Performing SAP on Oracle Full Database Restore

brrestore -d -util_file -p $Oracle_HOME/dbs/veeam_initSID.sap -b last -m full

Run the brrestore command with the following parameters:

1. Specify util_file as the argument for the -d (-device) parameter. This option defines that a file-by-
file restore will be performed using Veeam Plug-in.

2. Specify the path to the initialization profile file ($Oracle_HOME/dbs/veeam_initSID.sap) as the

argument for the -p (-profile) parameter.

3. Specify last as the argument for the -b (-backup) parameter. With this option, BRRESTORE uses the
last successful database backup for the restore.

4. Specify full as the argument for the -m (-mode) parameter. With this option, BRRESTORE performs
restore of files in all tablespaces, control files and redo log files.

213 | Veeam Plug-ins for Enterprise Applications | User Guide

Redo Logs Restore
If you want to restore redo log files that were backed up with BRARCHIVE, you can use the BRRESTORE tool. For
details, see the Names of BRRESTORE Details Logs section of the SAP Database Guide: Oracle.

Example: Performing SAP on Oracle Redo Logs Restore

brrestore -d util_file -a 1-100

Run the brrestore command with the following parameters:

1. Specify util_file as the argument for the -d (-device) parameter. This option defines that a file-by-
file restore will be performed using Veeam Plug-in.

2. Specify the log sequence number interval as the argument for the -a (-archive) parameter. This option
defines which log files must be restored.

214 | Veeam Plug-ins for Enterprise Applications | User Guide

Database Restore to Another Server (System
Copy)
You can restore SAP on Oracle databases from Veeam Plug-in backups to another server. To restore databases
to another server, you must reconfigure settings of Veeam Plug-in as shown below.

For security reasons, you can restore databases to another server only in the following condition. The account
you use to connect to Veeam Backup & Replication server must be the same account that performed the backup
of the source system. If you want to use another account, you can assign the Veeam Backup Administrator or
Veeam Restore Operator roles to the required account. For details on assigning Veeam Backup & Replication
roles, see the Roles and Users section of the Veeam Backup & Replication User Guide.

Procedure
To restore databases to another server, you must reconfigure settings of Veeam Plug-in as shown below:

1. Go to /opt/veeam/VeeamPluginforSAPOracle and run the following command to select the source

server whose backups you want to use during restore.

VM2ADM:/opt/veeam/VeeamPluginforSAPOracle> SapOracleBackintConfigTool --se

t-restore-server

2. Select the required SAP on Oracle server.

Select source SAP on Oracle server to be used as a restore target:

0. To disable this functionality.
1. saporacle01
Enter server number: 1

3. Specify a backup repository where the required backup files are stored.

Available backup repositories:

1. win_repo02
2. main_repo
Enter server number: 2

NOTE
• The account used to connect to Veeam Backup & Replication server must have access
permissions on the required repository. Otherwise the repository will not be displayed in the
list of available repositories. To learn how to configure access permissions on repositories, see
Setting Up User Permissions on Backup Repositories.
• The wizard does not import existing backups from the repository. To perform a System Copy
restore from the imported backup, you must map the backup. For details, see Importing
Backups.

4. Perform the restore to another server.

215 | Veeam Plug-ins for Enterprise Applications | User Guide

 5. After the restore, you must revert back the restore-server option of the Veeam Plug-in configuration
wizard. Otherwise, you will not be able to restore data from the actual server backup file. If you perform
only restore to other server, leave this setting enabled. It will not affect the backups of the actual system.
To disable the functionality, run the --set-restore-server command and enter 0.

SapOracleBackintConfigTool --set-restore-server
Select source SAP on Oracle server to be used as a restore target:
0. To disable this functionality.
1. saporacle01
Enter server number: 0

216 | Veeam Plug-ins for Enterprise Applications | User Guide

Restore from Backup Copy
You can restore Oracle databases from backups and backup copies. To restore from backup copies, you must
enable the restore from backup copy option in the Veeam Plug-in wizard.

IMPORTANT

If the restore from backup copy option is enabled, you cannot back up databases using Veeam Plug-in, and
you cannot restore from backups created by primary Veeam Plug-in backup jobs. You can restore only from
backup copy files until you disable the restore from backup copy option.

For instruction on how to enable/disable the restore from backup copy option, see the following guides:

• Enabling Restore from Backup Copy

• Disabling Restore from Backup Copy

Enabling Restore from Backup Copy

To be able to restore from backup copies, do the following:

1. In the machine where Veeam Plug-in is installed, open the terminal and run the following command:

SapOracleBackintConfigTool --configure-restore-from-copy

2. Select the number of the backup copy job you want to use:

Select secondary job for failover:

0. Disable
1. Plug-ins backup copy job\linuxq01 SAP Oracle backup <serv10_repo>
Select secondary job for failover:1

IMPORTANT

The account used to connect to the Veeam Backup & Replication server must have access
permissions on the required repository.

Disabling Restore from Backup Copy

To be able to back up with Veeam Plug-in and restore from backups, disable the restore from backup copies (set
the parameter back to 0):

SapOracleBackintConfigTool --configure-restore-from-copy
Select secondary job for failover:
0. Disable
1. Plug-ins backup copy job\linuxq01 SAP Oracle backup <serv10_repo>
Select secondary job for failover:0

217 | Veeam Plug-ins for Enterprise Applications | User Guide

Retention of SAP on Oracle Backups
To set an automatic removal of old backups, you can use the retention policy of Veeam Plug-in for SAP on
Oracle. The --set-force-delete command of Veeam Plug-in automatically deletes backup files which are
older than specified number of days. For details, see Configuring Retention Policy for Backups.

Also, you can manually delete backups from a backup repository using the Veeam Backup & Replication console
and. For details, see Deleting Backups Manually Using Veeam Backup & Replication Console.

218 | Veeam Plug-ins for Enterprise Applications | User Guide

Configuring Retention Policy for Backups
Veeam Plug-in for SAP on Oracle has a functionality that automatically deletes backup files which are older than
specified number of days. For example, you can use it if a backup repository contains backup files that are no
longer in the backup catalog.

1. To enable automatic deletion of backup files, run the following command.

SAPOracleBackintConfigTool --set-force-delete

2. Enter the number of days after which Veeam Plug-in will delete backup files on all configured backup
repositories.

Garbage collector automatically deletes backup files older than the specif
ied number of days.
Make sure the number of days value exceeds your retention policy.
To disable this functionality, set the number of days to 0.
Enter the number of days to delete backups after, between 7 and 999 [0]:

By default, the force delete functionality is disabled (set to 0).

IMPORTANT

A value for the number of days setting must be at least 1 backup generation period longer than the
retention period for your Oracle Database backups. Otherwise, Veeam Plug-in will delete earliest backups
created within the retention period.

219 | Veeam Plug-ins for Enterprise Applications | User Guide

Deleting Backups Manually
Apart from configuring the retention policy, you can delete backups manually from backup repositories using
the Veeam Backup & Replication console.

NOTE

If you remove backups from a backup repository manually, the backup catalog will not be updated.

To remove a backup from a backup repository, do the following:

1. In the Veeam Backup & Replication console, open the Home view.

2. In the Inventory pane, select Backups.

3. In the working area, right-click the backup job object name and select Delete from disk.

220 | Veeam Plug-ins for Enterprise Applications | User Guide

Removing Backups from Configuration
If you want to remove records about backups from the Veeam Backup & Replication console and configuration
database, you can use the Remove from configuration operation.

When you remove a backup from the configuration, backup files (VAB, VASM) remain on the backup repository.
You can import backup files later and restore from them.

To remove a backup from the configuration:

1. Open the Home view.

2. In the inventory pane, select Backups.

3. In the working area, select the backup and click Remove from > Configuration on the ribbon. You can also
right-click the backup and select Remove from configuration.

221 | Veeam Plug-ins for Enterprise Applications | User Guide

Backup Copy for SAP on Oracle Backups
Having just one backup does not provide the necessary level of safety. The primary backup may get destroyed
together with production data, and you will have no backups from which you can restore data.

To build a successful data protection and disaster recovery plan, it is recommended that you follow the 3-2-1
rule:

• 3: You must have at least three copies of your data: the original production data and two backups.

• 2: You must use at least two different types of media to store the copies of your data, for example, local
disk and cloud.

• 1: You must keep at least one backup offsite, for example, in the cloud or in a remote site.

Thus, you must have at least two backups and they must be in different locations. If a disaster takes out your
production data and local backup, you can still recover from your offsite backup.

To help you adopt the 3-2-1 rule, Veeam Backup & Replication offers the backup copy functionality that allows
you to create several instances of the same backup in different locations, whether onsite or offsite. Backup
copies have the same format as those created by backup jobs and you can recover your data from them when
you need it.

Veeam Backup & Replication fully automates the backup copy process and lets you specify retention settings to
maintain the desired number of restore points, as well as full backups for archival purposes. Backup copy is a
job-driven process. When enabled, the backup copy job for Veeam Plug-in backups runs continuously.

For details on how it works, see the Backup Copy section of the Veeam Backup & Replication User Guide.

222 | Veeam Plug-ins for Enterprise Applications | User Guide

Creating Backup Copy Job
To copy backups to a secondary location, you must configure a backup copy job. The backup copy job defines
how, where and when to copy backups. One job can be used to process backups of one or more machines.

You can configure a job and start it immediately or save the job to start it later.

Before creating a job, check prerequisites. Then use the New Backup Copy Job wizard to configure a backup
copy job.

1. Launch Backup Copy Job wizard.

2. Specify a job name and description.

3. Selects backups to process.

4. Define backup copy target.

5. Specify advanced settings.

6. Define backup copy schedule.

7. Finish working with the wizard.

Before You Begin

Before you create a backup copy job, check the prerequisites and limitations:

• Backup infrastructure components that will take part in the backup copy process must be added to the
backup infrastructure and properly configured. These include source and target backup repositories
between which backups must be copied.

• The target backup repository must have enough free space to store copied backups. To receive alerts
about low space on the backup repository, configure global notification settings. For more information,
see Specifying Other Notification Settings.

• For Veeam Plug-in backup copy jobs, you cannot select a Veeam Cloud Connect repository as a backup
copy target.

IMPORTANT

[For BR*Tools backup with the rman_util parameter] To have the whole set of backup files, you must
add both jobs to the backup copy job:

1. The job created by Veeam Plug-in for Oracle RMAN that contains database files or redo logs

2. The job created by Veeam Plug-in for SAP on Oracle that contains data control files and BR*Tools logs.

223 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 1. Launch Backup Copy Job Wizard
To create a backup copy job, do the following:

1. In the Veeam Backup & Replication console, open the Home view.

2. Click the Backup Copy tab and select Application backup.

224 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 2. Specify Job Name and Description
At the Job step of the wizard, specify a name and description for the backup copy job.

1. In the Name field, enter a name for the job.

2. In the Description field, enter a description for the job. The default description contains information about
the user who created the job, date and time when the job was created.

225 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 3. Selects Backups to Process
At the Object step of the wizard, select machines whose backups you want to copy to the target repository.

1. Click the Add button and select from which entity you want to process the machines.

o From jobs: You can select Veeam Plug-in backup jobs. When a backup copy job runs, Veeam Backup &
Replication will search for backup files created by selected jobs.

o From repositories: You can select repositories where Veeam Plug-in backups are stored. When a
backup copy job runs, Veeam Backup & Replication will search for backup files created by Veeam
Plug-in in selected repositories.
[Optional] If you have added jobs from a repository and want to exclude from processing some of the
backup jobs on the selected repository, click Exclusions and select the jobs that you want to exclude.

2. Use the Remove button if you want to remove selected jobs or repositories from processing.

226 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 4. Define Backup Copy Target
At the Target step of the wizard, configure the target repository settings.

1. From the Backup repository list, select a backup repository in the target site where copied backups must
be stored. When you select a target backup repository, Veeam Backup & Replication automatically checks
how much free space is available on it. Make sure that you have enough free space to store copied
backups.

IMPORTANT

For Veeam Plug-in backup copy jobs, you cannot select a Veeam Cloud Connect repository as a
backup copy target.

2. [Optional] If the target repository contains a Veeam Plug-in backup that was excluded from the backup
copy job, and if you don't want to transfer duplicate data, you can use the mapping feature.
After you configure mapping, if some of backup files (.VAB) of the source backup are missing in the target
backup copy, these files are uploaded to the target backup copy.

NOTE

Veeam Plug-in backup copy jobs does not use WAN accelerators.

To map a backup copy job to the backup:

a. Click the Map backup link.

b. Point the backup copy job to the backup in the target backup repository. Backups in the target backup
repository can be easily identified by backup job names. To facilitate search, you can use the search
field at the bottom of the window.

IMPORTANT
• Used account must have access to Veeam backup repositories that you plan to use.
• Encryption must be disabled on the repository.

Otherwise, the repositories will not be listed as available. To learn how to configure access permissions and
encryption settings on repositories, see Access and Encryption Settings on Repositories.

227 | Veeam Plug-ins for Enterprise Applications | User Guide

 3. You can specify the number of days after which the backup copy will be deleted from the repository. Note
that the countdown starts from the moment when source backup has been created.

228 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 5. Specify Advanced Settings
At the Target step of the wizard, click Advanced to configure compression, RPO and notifications settings.

• Compression and Deduplication

• RPO

• Notifications

Compression and Deduplication

At the Storage tab, define compression and deduplication settings.

By default, Veeam Backup & Replication performs deduplication before storing copied data on the target backup
repository. Deduplication provides a smaller size of the resulting backup file but may reduce the job
performance.

1. You can disable data deduplication. To do this, clear the Enable inline data deduplication check box.

2. From the Compression level list, choose a compression level to be used: Auto, None, Dedupe-friendly,
Optimal, High or Extreme. The recommended level of compression for backup copy jobs is Auto. In this
case, Veeam Backup & Replication uses compression settings of the copied backup files. For more
information, see Compression and Deduplication.

RPO Monitor
At the RPO Monitor tab, specify RPO warning settings.

229 | Veeam Plug-ins for Enterprise Applications | User Guide

Enable the Warn me if backup is not copied within check box and specify the time period in minutes, hours, or
days.

If the backup copy is not created within the specified time period, the backup copy job will finish with the
Warning status. The countdown starts from the moment when the required backup is finished and ready to be
copied.

Notifications
At the Notifications tab, to specify notification settings for the backup copy job:

1. At the Target step of the wizard, click Advanced.

2. Click the Notifications tab.

3. Select the Send SNMP notifications for this job check box if you want to receive SNMP traps when the job
completes successfully. SNMP traps will be sent if you specify global SNMP settings in Veeam Backup &
Replication and configure software on recipient's machine to receive SNMP traps. For more information,
see Specifying SNMP Settings.

4. Select the Send email notifications to the following recipients check box if you want to receive
notifications by email in case of job failure or success. In the field below, specify a recipient’s email
address. You can enter several addresses separated by a semicolon.

5. Veeam Backup & Replication sends a consolidated email notification once for the specified backup copy
interval. Even if the synchronization process is started several times within the interval, for example, due
to job retries, only one email notification will be sent.

6. Email notifications will be sent if you configure global email notification settings in Veeam Backup &
Replication. For more information, see Configuring Global Email Notification Settings.

230 | Veeam Plug-ins for Enterprise Applications | User Guide

 7. At the Send at field, specify the time when you want to receive notifications. Note that you will receive a
notification on a status of the job status once a day.

8. You can choose to use global notification settings or specify custom notification settings.

o To receive a typical notification for the job, select Use global notification settings. In this case, Veeam
Backup & Replication will apply to the job global email notification settings specified for the backup
server. For more information, see Configuring Global Email Notification Settings.

o To configure a custom notification for a job, select Use custom notification settings specified below.
You can specify the following notification settings:

i. In the Subject field, specify a notification subject. You can use the following variables in the
subject: %Time% (completion time), %JobName%, %JobResult%, %VmCount% (number of
machines in the job) and %Issues% (number of machines in the job that have been processed
with the Warning or Failed status).

ii. Select the Notify on success, Notify on warning and Notify on error check boxes to receive email
notification if data processing within the backup copy interval completes successfully, fails or
completes with a warning.

231 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 6. Define Backup Copy Schedule
At the Schedule step of the wizard, define a time span in which the backup copy job must not transport data
between source and target backup repositories. For more information, see Backup Copy Window.

To define a backup window for the backup copy job:

1. Select the During the following time periods only option.

2. In the schedule box, select the desired time area.

3. Use the Enable and Disable options to mark the selected area as allowed or prohibited for the backup copy
job.

232 | Veeam Plug-ins for Enterprise Applications | User Guide

Step 7. Finish Working with the Wizard
At the Summary step of the wizard, complete the procedure of backup copy job configuration.

1. Review details of the backup copy job.

2. Select the Enable the job when I click Finish check box if you want to start the job right after you finish
working with the wizard.

3. Click Finish to close the wizard.

233 | Veeam Plug-ins for Enterprise Applications | User Guide

Converting Backup Copy to Backup
If you have imported backup copy files created by a backup copy job from another repository, you can convert
them into regular backup files. When you convert backup copy files to regular backup files, Veeam Plug-in
creates a backup job and adds attaches the converted backup files to it. You can use this backup job to continue
the backup chain and use converted backup files as a restore point.

If you have imported backups created by a backup copy job from another repository, you can convert them into
regular backup files. When you convert backup copy files to regular backup files, Veeam Plug-in creates a
backup job and adds attaches the converted backup files to it. You can use this backup job to continue the
backup chain and use converted backup files as a restore point.

You can convert imported Veeam Plug-in backups into regular Veeam Plug-in backup files in the following
cases:

• If you have deleted a backup copy job which created the backup copy.

• If you have excluded a backup job from a backup copy job that used multiple backup jobs as a source.

• If you have imported a Veeam Plug-in backup copy from another repository.

NOTE

If you want to restore from a backup copy, you don't need to convert the backup copy to backup. For
details, see Restore from Backup Copy.

Converting Backup Copy to Backup for SAP HANA

To convert a backup copy to a primary backup, use the --promote-backup-copy-to-primary parameter as shown
below:

SapOracleBackintConfigTool --promote-backup-copy-to-primary
Backup copies available for promotion to primary backup:
1. Backup Copy Job 1\saprhel01-localdomain SAP backint backup (Default Backup R
epository)
Select backup: 1
Promotion of backup copy to a primary backup will reconfigure the plug-in to us
e a different repository. Continue? (y/N): y

IMPORTANT

[For servers with the customServerName option] To avoid failure of conversion of backup copies, the
server name must be the same as the name used in the backup copy.

234 | Veeam Plug-ins for Enterprise Applications | User Guide

Logs and Support
If you have any questions or issues with Veeam Plug-in for SAP on Oracle or Veeam Backup & Replication, you
can search for a resolution on Veeam Community Forums or submit a support case in the Veeam Customer
Support Portal.

When you submit a support case, we recommend you attach necessary logs related to Veeam Plug-in
operations.

Veeam Plug-in Logs

To export Veeam Plug-in logs, do the following:

1. In the Veeam Backup & Replication server, go to %PROGRAMDATA%\Veeam\Backup\Plugin.

2. Copy logs of the required backup or restore process.

SAP Backint Logs

To export SAP Backint logs, in the SAP on Oracle server, go to /tmp/veeam_plugin_logs/<user_name>/
and copy the following files:

• SapOracleBackint.log

• SapBackintOracleManager.log

• Agent.Source.log

BRTools Logs
The Detail and Summary logs of BRTools, are stored in the /oracle/SID/sapbackup and
/oracle/SID/saparch directories.

For details, see the following sections of the SAP Database Guide: Oracle: BRBACKUP Logs, BRRESTORE Logs,
BRARCHIVE Logs, BRRECOVER Logs.

235 | Veeam Plug-ins for Enterprise Applications | User Guide