Challenge
Mapping an existing Veeam Availability for Nutanix AHV backup chain to a different Veeam Backup and Replication Repository.Solution
Make sure the respective backup job is not running (and won't be running during the entire process). Do not change Veeam Backup server credentials specified in the web interface of Veeam Availability for Nutanix AHV during the entire process.Perform the following:
1. Locate the backup chain: in Veeam Backup & Replication console navigate to ‘Backups -> Disk’, open job properties (right-click) and note the path to the backup files.
In this example, the backup chain parent directory is F:\Backups\TERMINAL95T1N_Administrator
2. Locate root folder of Veeam Backup & Replication repository you want to move backups to: in Veeam Backup & Replication console navigate to ‘Backup infrastructure -> Backup repositories’, open properties of a repository (right-click), note root folder path specified in ‘Repository’ tab.
In this example, the root folder is E:\Backups
3. Move the backup chain:
3.1 Re-create the directory structure in the new repository:
Backup chain parent directory path (F:\Backups\TERMINAL95T1N_Administrator) consists of the following parts:
F:\Backups – source backup repository root folder
TERMINAL95T1N_Administrator – backup chain parent directory
For instance, under E:\Backups (root folder of Veeam Backup & Replication repository you want to move the backups to) create a directory named after the account that is used to access the Veeam Backup server. In this example, the account is TERMINAL95T1N\Administrator, so the folder name would be TERMINAL95T1N_Administrator and the whole path E:\Backups\TERMINAL95T1N_Administrator
F:\Backups – source backup repository root folder
TERMINAL95T1N_Administrator – backup chain parent directory
For instance, under E:\Backups (root folder of Veeam Backup & Replication repository you want to move the backups to) create a directory named after the account that is used to access the Veeam Backup server. In this example, the account is TERMINAL95T1N\Administrator, so the folder name would be TERMINAL95T1N_Administrator and the whole path E:\Backups\TERMINAL95T1N_Administrator
3.2 Select backup chain to move:
For Nutanix AHV VMs, Veeam Backup & Replication generates per-VM backup chains: one backup chain contains data for one VM only. Even if you add multiple VMs to a backup job, Veeam Backup & Replication will create multiple backup chains in the backup repository, one per every VM processed by the job.
You may find a list of all per-VM backup chains as shown in step 1.
Per-VM backup directories naming pattern is as follows:
vm_name Backup (policy_name),
where:
vm_name – virtual machine name
policy_name – backup policy name
For example:
ahvbkp Backup (BackupJob - all vms)
This is the name of the per-VM backup directory for the virtual machine ahvbkp being backed up by the BackupJob – all vms backup policy.
3.3 Move the selected per-VM backup folders to the new repository
You may find a list of all per-VM backup chains as shown in step 1.
Per-VM backup directories naming pattern is as follows:
vm_name Backup (policy_name),
where:
vm_name – virtual machine name
policy_name – backup policy name
For example:
ahvbkp Backup (BackupJob - all vms)
This is the name of the per-VM backup directory for the virtual machine ahvbkp being backed up by the BackupJob – all vms backup policy.
3.3 Move the selected per-VM backup folders to the new repository
4. Rescan both source and target Veeam Backup & Replication repositories: in Veeam Backup & Replication console navigate to ‘Backup infrastructure -> Backup repositories’, open properties of the repository (right-click), select ‘Rescan’. Once the rescan is done, moved backup chain appears under the Backup -> Disk (imported) section.
5. Log in to Veeam Availability for Nutanix AHV web interface and edit your backup policy according to this guide.
6. Upon the next backup session of the respective backup policy, the moved backup chains will disappear from Backup -> Disk (imported) section and will be moved to Backup -> Disk. The backup policy will start to use new location as a target repository.