Skip to main content
Question

Need guidance on NAS repository IP change

  • July 28, 2026
  • 1 comment
  • 13 views
N
Forum|alt.badge.img+1

 

We changed the IP address of a NAS used as a CIFS/SMB backup repository. The repository was originally configured using a UNC path with a hardcoded IP address and is now showing as Unavailable because the old IP is no longer reachable.

Veaam ver 12.3.2

Current situation:

  • Repository type: CIFS/SMB
  • Old repository path: \\192.168.0.8\NAS
  • New repository path: \\192.168.0.81\NAS\Backups
  • Repository is not listed under Get-VBRServer; it is only visible via Get-VBRBackupRepository, so KB1905 (managed server rename) does not apply.
  • A new repository was added using the updated NAS path.
  • When attempting to map existing backups to the new repository, Veeam requests moving the backup files from the old repository.
  • This operation cannot proceed because the old repository path is no longer accessible.
  • Creating a new backup chain is currently not an option due to storage constraints.

Looking for the supported and safest approach to transition the existing backup chains and jobs to the new NAS repository when:

  1. The old repository IP is no longer reachable.
  2. Existing backup files remain on the NAS.
  3. There is insufficient free space to create new full backups.

Has anyone handled a similar CIFS repository IP change scenario, and what would be the recommended supported path forward?

      1 comment

      D
      Forum|alt.badge.img+3
      • ddomask
      • Veeam Product Management
      • July 28, 2026

       

       

      • When attempting to map existing backups to the new repository, Veeam requests moving the backup files from the old repository.

      Should not happen, if the backups are properly identified and imported, then map backup will avoid the need for any Move-Backup operation. To me sounds like for whatever reason, the backups on the “new” repository were not properly detected.

      There is no safe way to update the IP of an SMB repository added by IP (don’t even try with DB or PowerShell, it’s a mess and it’s not as simple as AI may tell you, please trust me on this existing “solutions” online will leave a mess in the DB and likely introduce silent issues that only pop up later)

      Please work with Veeam Support on this; the proper way to do it would be:

      1. Take a Configuration Backup as a safety precaution to do a fall-back
      2. Detach all existing backups targeting the old repository from their respective jobs
      3. Remove all the backups from configuration (ctrl+right-click)
      4. Remove the old repository
      5. Add the new repository
      6. Rescan the repository to import all the backups
        1. This step must succeed -- if it does not, then you won’t be able to map to the existing backups
      7. Edit each job, point it at the new repository and map backup

      Similarly, strongly advise add a DNS name for the NAS IP if possible (even with /etc/hosts hacks)

      0x0D 0x0A
        Terms & ConditionsAccessibility statement