How Veeam Plug-in for Oracle RMAN Works

Veeam Plug-in functions as an agent between Oracle RMAN and Veeam backup repository.

By default, RMAN sends backups to a native RMAN location on disk (DEFAULT DEVICE TYPE TO DISK). When you configure Veeam Plug-in, the default device type is changed to SBT_TAPE, which gives control over backup media management to Veeam Plug-in. Thus, 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 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.

Multiple Repositories Deployment

Page updated 7/8/2024

Page content applies to build 12.2.0.334