Recovering Oracle Databases with Veeam: A Step-by-Step Guide for vSphere Environments

Before We Start: How This Actually Works

It is worth spending a minute on the mechanics before jumping into the steps, because the Veeam Plug-in for Oracle RMAN workflow is distinct from the application-aware image backup path you might already be familiar with.

When you use the Veeam Plug-in for Oracle RMAN, Oracle's own Recovery Manager drives the backup directly to the Veeam repository. Veeam Explorer for Oracle then uses that same RMAN channel to restore. It is not mounting a VM snapshot and scraping files out -- it is a proper RMAN-mediated restore. That distinction matters because it means your RMAN catalog (or controlfile) is the source of truth for what can be recovered, and the Veeam plug-in on the Oracle host is doing the real work, not just the VBR console.

What Veeam Explorer actually does during a restore is this: it establishes a session from the VBR server to the Oracle host via the installed plug-in, then issues RMAN commands to restore the database files and archived redo logs to either the original location or a target you specify. For Linux hosts, it does all of this over SSH. For Windows hosts, it deploys a short-lived runtime service (Veeam Oracle Restore Service) on the target that handles the file operations and then removes itself when the restore is done.

Prerequisites

Run through this list before you start. Missing any of these is usually why recoveries fail before they even get to the RMAN phase.

This is your primary break-fix scenario. The database is on the same host it was backed up from, and you need it back -- whether that is after corruption, an accidental drop, or a failed patch rollback. The database will be taken offline during the restore and brought back open when RMAN finishes recovery.

1. In the VBR console, go to Home > Backups, find the backup job that covered the Oracle host, and right-click the restore point you want to work from. Select Restore application items > Oracle databases. This launches Veeam Explorer for Oracle.
2. Explorer will connect to the VBR server and enumerate the Oracle databases it finds in that restore point. Give it a moment -- on large backups this can take a minute or two to populate the tree.
3. In the left pane, expand the host node to see the available databases. Right-click the target database and select Restore database > To the original location.
4. The restore wizard opens. On the Restore point page, choose how far back you want to go: latest state, a specific point in time, or a specific SCN. For point-in-time, enter the date and time using the picker -- Veeam will use the archived redo logs to roll forward to that exact moment.
5. Provide the credentials for the Oracle host when prompted. On Linux this is the OS user that owns the Oracle home. On Windows, provide a user with access to the Oracle home directory.
6. Review the summary and click Restore. Watch the task log at the bottom of the Explorer window for RMAN output. You will see the familiar RMAN channel allocation, restore, and recover messages as it works through the operation.
7. When Explorer reports success, verify the database state before telling anyone it is back. See the verification section at the end of this article.

Veeam Explorer for Oracle -- restore point selection with point-in-time and SCN options for original location restore.

The Veeam Explorer for Oracle PowerShell module uses the VEOR prefix. For RMAN plug-in backups specifically, the session cmdlets are Start-VEORRMANRestoreSession and Restore-VEORRMANDatabase. These are different from the Start-VEORRestoreSession / Restore-VEORDatabase cmdlets, which are for VM image-based backups with application-aware processing. Make sure you are using the right set for your backup type.

# Load the Veeam Explorer for Oracle module from the VBR server
# Run this in a PowerShell session on the VBR server itself
Import-Module Veeam.Backup.PowerShell

# Get the RMAN plug-in backup by the Oracle host name
$backup = Get-VEORRMANBackup -Name "oracle-host.example.com"

# Start a restore session against that backup
$session = Start-VEORRMANRestoreSession -Backup $backup

# Enumerate the databases available in the session
$db = Get-VEORRMANDatabase -Session $session -Name "ORCL"

# Restore to original location -- latest available state
# Add -RestoreToPointInTime or -RestoreToSCN to target a specific point
Restore-VEORRMANDatabase `
    -Session $session `
    -Database $db `
    -RestoreToOriginalLocation

# Close the session when done
Stop-VEORRMANRestoreSession -Session $session

Use this path when you want to land the database somewhere other than where it came from -- a different host, a different Oracle home directory, or under a new database name. This is the path for dev/test refreshes, pre-production validation, or restoring to a standby host while the primary is still being diagnosed.

1. Launch Veeam Explorer for Oracle as in Path 1, steps 1 and 2.
2. Right-click the target database in the left pane and select Restore database > To a different location.
3. On the Target server page, specify the destination Oracle host. It must have the Veeam Plug-in for Oracle RMAN installed and be reachable from the VBR server. For Linux targets, SSH must be available.
4. In the Oracle home field, specify the Oracle home path on the destination host. Click Browse to navigate the remote filesystem, or type the path directly.
5. Set the Global database name in the format DB_NAME.DB_DOMAIN (for example, orcl_restore.example.com). Veeam will truncate the DB_NAME portion to 8 characters if it exceeds that length. Set the Oracle SID as well -- it defaults to match the DB_NAME but you can override it. Maximum SID length is 12 alphanumeric characters.
6. Set the restore point scope (latest, point-in-time, or SCN) and provide host credentials.
7. Review the summary and click Restore. Monitor the task log.

Custom location restore -- setting the destination host, Oracle home path, global database name, and SID.

Import-Module Veeam.Backup.PowerShell

$backup  = Get-VEORRMANBackup -Name "oracle-host.example.com"
$session = Start-VEORRMANRestoreSession -Backup $backup
$db      = Get-VEORRMANDatabase -Session $session -Name "ORCL"

# Restore to a different host under a new name
# -ServerName       : FQDN or hostname of the destination Oracle host
# -OracleHomePath   : full path to Oracle home on the destination
# -DatabaseName     : new DB_NAME (max 8 chars)
# -DatabaseDomain   : domain portion of the global database name
Restore-VEORRMANDatabase `
    -Session $session `
    -Database $db `
    -ServerName "oracle-dest.example.com" `
    -OracleHomePath "/u01/app/oracle/product/19.0.0/dbhome_1" `
    -DatabaseName "ORCL_RST" `
    -DatabaseDomain "example.com" `
    -RestoreToPointInTime (Get-Date "2024-06-15 14:30:00")

Stop-VEORRMANRestoreSession -Session $session

Sometimes you do not want to restore to a live Oracle instance at all -- you just want the files. Maybe you are handing a copy off to a DBA team working in an isolated environment, or you want to archive a specific point-in-time state outside of your normal backup chain, or you need to import using RMAN on a host where Veeam is not installed. The export path handles all of that.

One important prerequisite for this path: if your Oracle host is Linux-based, you need a staging Oracle server configured in VBR under General Options > Oracle. Without it, export operations on Linux will not start. Windows-based Oracle hosts do not have this requirement.

1. Launch Veeam Explorer for Oracle as in Path 1, steps 1 and 2.
2. Right-click the target database (you can also expand it to target a specific tablespace) and select Export database.
3. Specify the destination folder. This can be a local path on the machine running the VBR console, or a UNC path to a network share. Make sure there is enough space -- you need at least the combined size of all datafiles plus the archive logs needed to reach your selected restore point.
4. Set the restore point scope: latest, point-in-time, or SCN.
5. Click Export and monitor the task log. When complete, the destination folder will contain RMAN backup set files that can be imported into any compatible Oracle instance.

Import-Module Veeam.Backup.PowerShell

$backup  = Get-VEORRMANBackup -Name "oracle-host.example.com"
$session = Start-VEORRMANRestoreSession -Backup $backup
$db      = Get-VEORRMANDatabase -Session $session -Name "ORCL"

# Export the database as RMAN backup sets to a local folder
# The folder will be created if it does not already exist
Export-VEORDatabase `
    -Session $session `
    -Database $db `
    -Path "D:\OracleExports\ORCL_20240615" `
    -RestoreToPointInTime (Get-Date "2024-06-15 14:30:00")

# Omit -RestoreToPointInTime to export to the latest available state

Stop-VEORRMANRestoreSession -Session $session

Post-Recovery Verification

Do not skip this. A restore that finishes without errors does not automatically mean a database that is clean and healthy. Run through these checks before you hand it back.

Confirm the Database is Open

sqlplus / as sysdba

SELECT instance_name, status FROM v$instance;
SELECT name, open_mode FROM v$database;

-- You want: STATUS = OPEN, OPEN_MODE = READ WRITE
-- If OPEN_MODE shows READ ONLY, the database did not complete recovery cleanly

Confirm Archive Log Mode

SELECT log_mode FROM v$database;
-- Should return ARCHIVELOG
-- If it returns NOARCHIVELOG after a restore, your pfile/spfile may not have been
-- restored correctly -- check the alert log before putting the database into service

Check the Alert Log

# Find the alert log location
find $ORACLE_BASE/diag -name "alert_*.log" -type f 2>/dev/null

# Scan for ORA- errors in the last 200 lines
tail -200 /u01/app/oracle/diag/rdbms/orcl/ORCL/trace/alert_ORCL.log | grep -i "ORA-"

# A clean restore ends with something like:
# Completed: ALTER DATABASE OPEN
# No ORA- errors after that line is what you want to see

Validate with RMAN

rman target /

-- Validate the physical and logical integrity of the restored database
VALIDATE DATABASE;

-- Crosscheck the repository so it reflects what is actually on disk now
CROSSCHECK BACKUP;
LIST EXPIRED BACKUP;