How Veeam Plug-in for Oracle RMAN Works

In this article

    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.

    How Veeam Plug-in for Oracle RMAN Works 

    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.

    How Veeam Plug-in for Oracle RMAN Works 

    Backup Files

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

    • VAB: compressed and deduplicated Oracle database backup files. Veeam Plug-in creates VAB files for all types of backups.
    • VASM: metadata files 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.
    • VACM: a backup job metadata file used to check synchronization with the database.
    I want to report a typo

    There is a misspelling right here:


    I want to let the Veeam Documentation Team know about that.