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 backups of scale-out clusters and servers with the customServerName option] To avoid mapping failure, the cluster name must be the same as the name used before importing backups.

[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.

Importing Veeam Plug-in Backup Files

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

Copy the backup file folder to a backup repository or add a new backup repository with this folder as a subfolder.

Important

Make sure that you import backup files and all related metadata files. Each backup folder includes a Veeam Plug-in backup file (.VAB) with its own storage metadata file (.VASM), and a single backup job metadata file (.VACM).

The import process cannot be completed successfully without the backup job metadata .VACM file.

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 IBM Db2 server, set the new repository as a target in the Veeam Plug-in settings:

DB2ConfigTool --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 following parameter:

Note

After you import the backup, map the imported backup to continue to back up to this repository. Using the Veeam Plug-in configuration tools, select the new repository as the target.

DB2ConfigTool --map-backup

Repairing Backup

Before you start the repair operation, you must disable the backup job that created the backup. Otherwise, Veeam Backup & Replication will display a message notifying that the job must be disabled. For details, see Disabling Backup Job.

To repair a backup:

In the Veeam Backup & Replication console, open the Home view.
In the inventory pane, select Backups.
In the working area, select the necessary backup.
Press and hold the [Ctrl] key, right-click the backup and select Repair.

Note

If your backups reside on a scale-out backup repository expanded with capacity tier, rescan the backup repository after the repair operation. To learn more about rescan, see the Rescanning Backup Repositories section in the Veeam Backup & Replication User Guide.