Move all backup files to the new backup repository first как исправить

Purpose

This article provides a method to change the repository where backup files are stored.
 

For documentation on changing the backup location of Veeam Agent jobs not directly controlled by Veeam Backup & Replication, but targeting a Veeam Backup & Replication server’s repository.  Please refer to vee.am/kb2321

Solution

Important! If you have attempted to manually import the backup files using the Import button in the ribbon prior to performing the steps below you must first «Remove from configuration» any backups that were manually imported. These will identifiable in the Backups > Disk (Imported) section, they will be listed with the suffix _imported and will have no repository listed in the Repository column.

There are two primary situations and respective methods that this KB article documents.
Below is a summary of both methods.

Method A:
You have physically moved the backup files to new storage and want to map the old jobs to the backup chain in the new location.

Method B:
You are seeding a job, or you want to map a job to a backup chain in a new location. This method does not require that the job doing the mapping be the same as the job which created the restore points initially.

Method A: Same Job, New Backup location

1. In [Backup Infrastructure] > [Backup Repositories], create a new repository for the new location where backup files will be located.
2. Manually move the backup files to the new repository path. You must include the metadata file (.vbm), full backup files (.vbk), and any needed incremental files (.vib or .vrb).

       Notes:

   • It is recommended to move all backup files, but you can omit incremental files if needed. If you decide to not move/copy all backup files to the new storage, you will need to use the “Forget Missing Restore Points” function to clear any references to backup files that were not moved/copied.
   • Also keep in mind that there will be folders created inside the directory/path for job names.
             If your repository path is set as E:Backups, Job A will go to E:BackupsJob A.
3.     
4. Rescan the new repository.     

   

       

5. If the backup files are not encrypted, skip this step.
       If the backup files are encrypted, the encrypted backup will appear under the Backups > Disk (encrypted) node in the inventory pane. In the working area, select the imported backup and click Specify Password on the ribbon or right-click the backup and select Specify password. More Information This is also relevant for encrypted Veeam Agent backups.
6. Edit the BackupBackup Copy Job. Go to the StorageTarget tab, and from the drop-down menu, select the new repository.     

   

       

7. Press Finish to finalize the setting. If you no error occurs, and the job now lists the new repository in its Repository column, the mapping has been completed.
       Note: If you encounter the following error: “Move all backup files to the new backup repository first”, some restore points the software was expecting to find were not found in the new repository. Cancel out of the job configuration and check both the old repository location and the new location to verify that all restore points have been moved. Then return to step 3 again.

If the steps above do not work, and you still get stopped at the «Move all backups files to the new backup repository first» error, please contact Veeam Support. You may also attempt Method B below.

Method B: New Job, New Backup location

To map the existing backup files to a new or different job, follow these steps:

1. Under Backups > Disk, right click the job you are changing repository for, and do either Remove From Backups (v8) or Remove from Configuration (v9).    

   

       

2. If you are mapping the backup set from one job to another, but the backup location will stay the same, skip this step.
       If you are moving the backup files to a new location create a new repository for the new location where backup files are located.
3. Rescan the repository where the backup files are located.     

   

       

4. If the backup files are not encrypted, skip this step.
       If the backup files are encrypted, the encrypted backup will appear under the Backups > Disk (encrypted) node in the inventory pane. In the working area, select the imported backup and click Specify Password on the ribbon or right-click the backup and select Specify password. More Information This is also relevant for encrypted Veeam Agent backups.
5. Edit the BackupBackup Copy Job. Go to the StorageTarget tab, and from the drop-down menu, select the repository where the backup files you wish to map are located.     

   

       

6. Click Map Backup and select the existing backup chain     

   

       

If you are attempting to seed failover cluster Veeam Agent for Microsoft Windows job’s restore points please follow the actions below (it has a bit different workflow due to the product design):

1. Clone the source cluster job
2. Remove the source job (it will also remove from configuration its points; not from the disk but from Veeam config only)
3. Move the source backup folder to a new backup folder;
4. Rescan the new repository to import the moved files 
5. Change the cloned backup job to the new repository and map the imported points there 

Migrating Repositories is not a day 2 day job. Sometimes it must be done when replacing Backup2Disk devices and sometimes when you’re running out of space. Migrations in general could be very challenging but not so with Veeam. There are two ways to migrate repositories and it depends on the Veeam license which one you can use. I tested both with my Synology NAS box. In theory it should be the same with any Enterprise Backup Storage System.

General

On my Synology I have two shared folders, VeeamBackup02 and VeeamBackup03. I also created a backup job that points to VeeamBackup02. Now I need to migrate repository VeeamBackup02 to VeeamBackup03. I also created under Backup Infrastructure – Backup Repositories 2 repositories pointing to the respective shared folders.

1. Migrate data on the Synology NAS

This method can be used with every paid Veeam Backup & Replication license. Before I started with the migration, I checked that no backup is currently running and that the backup job is disabled. The following steps describe the migration process.

• Copy all data from VeeamBackup02 to VeeamBackup03 on the Synology NAS.
• Open Backup and Replication console, select the new Backup Repository and do a “Rescan Repository”.
• When the rescan is completed you will find under Backup & Replication – Backups – Disk (imported) the moved backups.

• Edit the Backup Job and select the migrated Repository as new backup target.
• The backups will be moved from Disk (imported) to Disk.

2. Migrate data through a Scale-Out Repository

This method can only be done if you’re using an Enterprise or Enterprise Plus license because you need Scale-Out Repository functionality. The Enterprise license has also the limitation that the Scale-Out Repository can only consists of 3 extends.

• Create a Scale-Out Repository with the two repositories you want to migrate between.

• Add the two repositories as extents. In my case VeeamBackup02 and VeeamBackup03.

• You will get an message that all backup jobs which are using any of the extents will be pointing to the new Scale-Out Repository.

• Depending on which storage you are using select the policy that is the most appropriate.

• After the Scale-Out Repository was created you can place the old extent (VeeamBackup02) in “Maintenance mode” and “Evacuate backups” to the new extent (VeeamBackup03).

• When the migration is finished you select Properties on the Scale-Out Repository.

• You can now remove the new extent (VeeamBackup03) from the Scale-Out Repository. The extent should be in Maintenance Mode before the removal. When you try to remove it you will be asked if you want to evacuate backups. In this case we DON’T want this. If you try to remove the Scale-Out Repository first you will also remove all linked backups.

• After you removed the extent (VeeamBackup03) you need to rescan the removed repository (VeeamBackup03) to ensure Backup & Replication can see the data in it. If everything works fine you can change the backup job to the new repository (VeeamBackup03) and remove the Scale-Out Repository.