Importing Backup Files

If the Veeam Backup & Replication server has failed and you have restored it in a new location, you can copy the backup files to a new repository and re-map the Veeam Plug-in backup files.

Limitations and Prerequisites

Consider the following limitations:

If backup files are not imported according to instructions given in this section, Veeam Plug-in backup and restore operations may fail.
The repository from which you plan to import backups must be added to the Veeam Backup & Replication infrastructure. Otherwise you will not be able to access backup files.

[For imports to the scale-out backup repository] Before importing your backup, consider that the names of all backup files (.VAB, .VASM, .VACM) and paths to these files contain only the following allowed characters:

a-zA-Z0-9
_-.+=@^

If your backup was initially created on a standalone backup server, the default name of the backup metadata file (.VACM) contains forbidden characters. Before importing, you must delete forbidden characters from the file name or replace them with the allowed characters.

How to Import Veeam Plug-in Backup Files

To import Veeam Plug-in backup files, do the following:

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

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.

In the Veeam Backup & Replication console, open the Backup Infrastructure view.
In the inventory pane of the Backup Infrastructure view, select the Backup Repositories node.
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.

During the rescan operation, Veeam Backup & Replication gathers information about backups that are currently available in the backup repository and updates the list of backups in the configuration database. After the rescan operation, backups that were not in this configuration database will be shown on the Home view in the Backups > Disk (Imported) node.

On the Oracle server, use the terminal to set the new repository as a target in the Veeam Plug-in settings:

For Windows:

"%PROGRAMFILES%\Veeam\VeeamPluginforOracleRMAN\OracleRMANConfigTool" --set-repositories

Available backup repositories:
1. serv55.tech.local
2. serv07_repo
Enter repository number: 1

For Linux and Unix:

OracleRMANConfigTool --set-repositories

Available backup repositories:
1. serv55.tech.local
2. serv07_repo
Enter repository number: 1

Start the Veeam Plug-in configuration wizard with the --map-backup parameter to re-map the plug-in backups:

Note

Before you re-map your backup to the repository, make sure that there is not an existing backup job on your machine with Veeam Plug-in that is targeted at the same repository. If there is such a job, delete this job from the Veeam Backup & Replication console.

For Windows:

"%PROGRAMFILES%\Veeam\VeeamPluginforOracleRMAN\OracleRMANConfigTool" --map-backup

For Linux and Unix:

OracleRMANConfigTool --map-backup