Building a Veeam Backup Job for Oracle with the RMAN Plug-in

Understanding the Oracle RMAN Plug-in Architecture

Unlike image-based backups that go through the hypervisor layer, the Veeam Plug-in for Oracle RMAN integrates directly with Oracle's Recovery Manager. RMAN treats the Veeam repository as a backup destination. The plug-in translates between RMAN's backup commands and Veeam's storage layer. This means the backup is driven by Oracle itself, not by a VM snapshot, and the resulting backup set is natively readable by RMAN for recovery.

In VBR managed mode, the VBR server handles plug-in installation, version management, and job scheduling. You configure everything from the VBR console. The plug-in runs as a service on the Oracle host and communicates back to VBR over the standard Veeam transport ports.

Prerequisites

Oracle RMAN in archive log mode. Run SELECT log_mode FROM v$database; and confirm it returns ARCHIVELOG. If it returns NOARCHIVELOG, RMAN cannot perform online backups and point-in-time recovery is not possible. Enable archivelog mode before proceeding.

SYSDBA credentials. The plug-in needs a user with SYSDBA privilege to connect to Oracle during backup. OS authentication (the oracle OS user on Linux) is simpler and does not require managing database passwords in Veeam.

Oracle listener running. Verify with lsnrctl status. The listener must be active and the Oracle instance registered.

SSH access for Linux Oracle hosts. VBR needs SSH access to deploy and manage the plug-in. The OS user needs sudo or root access.

TDE not in use. The Veeam Plug-in for Oracle RMAN does not support Transparent Data Encryption. If TDE is enabled, you cannot use this plug-in path for granular recovery.

Step 1: Create a Protection Group

1. In the VBR console, go to Inventory > Physical and Cloud Infrastructure.
2. Click Create Protection Group on the ribbon.
3. Select Individual computers as the protection group type and click Next.
4. Click Add and enter the hostname or IP of the Oracle host. In the credentials field, provide the OS-level credentials (the oracle OS user on Linux, or a local or domain administrator on Windows).
5. On the Options step, enable Install backup agent automatically and enable auto-update so VBR keeps the plug-in current after upgrades.
6. Leave Run discovery when I click Finish checked. This triggers VBR to connect to the Oracle host, verify access, and deploy the plug-in immediately.
7. Click Finish. Watch the discovery result in the bottom pane. You want to see the host appear as Online with the plug-in successfully deployed.

Step 2: Create the Oracle RMAN Backup Job

1. Go to Home and click Backup Job > Oracle RMAN. This option appears once you have at least one Oracle protection group.
2. Give the job a clear name and description. Click Next.
3. On the Computers step, click Add and select the Oracle host from the protection group.
4. On the Oracle step, configure how RMAN connects to the database. For OS authentication on Linux (recommended), select Oracle account and use the oracle OS user. Set the Number of RMAN channels. A common starting point for a single-disk Oracle host is 2 channels. Multi-disk or higher-performance environments can use 4 or more. Match this to your I/O capacity.
5. On the Storage step, select the target repository and set retention in days. RMAN backups expire based on time, not snapshot count.
6. On the Schedule step, configure the full backup frequency and the archive log backup interval. A daily full backup with archive log backup every 30 to 60 minutes is a reasonable starting point for most production environments.
7. Click Finish. If you want to run the first backup immediately, select Run the job when I click Finish.

Verifying the First Backup

Check the Job Session Log

After the first backup completes, open the session details in the VBR console. The log should show RMAN channel allocation, database backup, archive log backup, and channel release, all without errors. Any ORA- error in the session log indicates an RMAN-level problem that needs to be resolved before the backup is reliable.

Verify from the Oracle Host

rman target /

-- List all backups known to RMAN
LIST BACKUP SUMMARY;

-- Crosscheck that backup pieces are accessible
CROSSCHECK BACKUP;

-- List any expired backups (should be zero on first run)
LIST EXPIRED BACKUP;

Test Item-Level Recovery

Right-click the backup in Home > Backups > Applications, select Restore application items > Oracle databases, and confirm Veeam Explorer opens and shows the database. If it does, the backup is usable for recovery. If it fails to mount or shows an empty tree, the backup configuration has a problem to fix now rather than during an incident.