Updating Source File Share Path for Backup Jobs with Secondary Target

Veeam Backup & Replication does not support auto mapping of the source file share path for the file backup copy when updating the source file share path for the main file backup job.

For example, you have a File Backup job protecting the file share located at \\shared_server\documents. It has an associated backup copy job - File Backup (Copy) 1. The file backups are stored in the main_storage repository, the file backup copies are stored in the copy_storage repository. Then, you decide to update the protected file share name to \\share_server_new\documents.

To correctly update the file backup job protecting this file share, do the following:

Add a new file share \\share_server_new\documents in the inventory, as described in section Adding File Share. Do not remove the old file share from the inventory yet as it is associated with the old file backup job.
Update the path to the source file share for the file backup:

For Veeam Backup & Replication 12.1 (build 12.1.0.2131) and later:

$unstructuredbackup = Get-VBRUnstructuredBackup -Name "File Backup"

$sourceserver = Get-VBRUnstructuredServer -Backup $unstructuredbackup

$targetserver = Get-VBRUnstructuredServer -Name "\\share_server_new\documents"

Update-VBRUnstructuredBackupPath -Backup $unstructuredbackup -SourceUnstructuredServer $sourceserver -TargetUnstructuredServer $targetserver

For Veeam Backup & Replication 12:

$nasbackup = Get-VBRNASBackup -Name "File Backup"

$sourceserver = Get-VBRNASServer -Backup $nasbackup

$targetserver = Get-VBRNASServer -Name "\\share_server_new\documents"

Update-VBRNasBackupPath -Backup $nasbackup -SourceNASServer $sourceserver -TargetNASServer $targetserver

As a result, the backup will be moved from the Backups - Disk to Backups - Disk (Orphaned).

Update the path to the source file share for the file backup copy:

For Veeam Backup & Replication 12.1 (build 12.1.0.2131) and later:

$unstructuredbackup = Get-VBRUnstructuredBackup -Name "File Backup (Copy) 1"

$sourceserver = Get-VBRUnstructuredServer -Backup $unstructuredbackup

$targetserver = Get-VBRUnstructuredServer -Name "\\share_server_new\documents"

Update-VBRUnstructuredBackupPath -Backup $unstructuredbackup -SourceUnstructuredServer $sourceserver -TargetUnstructuredServer $targetserver

For Veeam Backup & Replication 12:

$nasbackup = Get-VBRNASBackup -Name "File Backup (Copy) 1"

$sourceserver = Get-VBRNASServer -Backup $nasbackup

$targetserver = Get-VBRNASServer -Name "\\share_server_new\documents"

Update-VBRNasBackupPath -Backup $nasbackup -SourceNASServer $sourceserver -TargetNASServer $targetserver

As a result, the backup copy will be moved from Backups - Disk (Copy) to Backups - Disk (Orphaned).

Edit settings of the File Backup job defining file backup properties:

Remove the old protected file share at \\shared_server\documents and add the new file share at \\share_server_new\documents, as described in sections Select Files and Folders to Back Up of Creating File Backup Jobs.
Map the file backup job to the File Backup backup converted at step 2, as described in step 4 of the Creating File Backup Jobs procedure.
Remove the secondary target repository added at step 7 of Creating File Backup Jobs procedure.
Ensure that the Run the job when I click Finish check box is not selected when you close the wizard, as described in step 9 of the Creating File Backup Jobs procedure.

Edit settings of the File Backup job defining file backup copy properties:

Enable creation of the file backup copy by selecting the Configure secondary destinations for this job check box, as described in step 4 of the Creating File Backup Jobs procedure.
Add the copy_storage repository for storing backup copies, as described in step 7 of the Creating File Backup Jobs procedure.

Veeam Backup & Replication will automatically map the existing file backup copy, which was previously located in Backups - Disk (Orphaned), to the file backup job.

Ensure that the Run the job when I click Finish check box is selected when you close the wizard, as described in step 9 of the Creating File Backup Jobs procedure.

As a result, if the job and its backups are updated correctly, the first session of the updated job will create not a full backup, but an incremental one.