Skip to main content
Question

backup failure for single nas file share

  • April 8, 2026
  • 4 comments
  • 29 views
B

Backup failure for single nas file share , rest of the file shares ( CIFS ) are completing successfully.

 

4/8/2026 3:47:51 AM Failed : Calculating file share size

4/8/2026 3:47:51 AM Failed : Backing up 0 files and 0 folders (0 B) transferred at 0 KB/s

4/8/2026 3:47:51 AM Failed : Container doesn't exist in backup.

Folder: [Id: [2cfxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx582f], Object key: [56dxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxeac1], Relative path: [Path [|.copy_offload], Nodes: [[.copy_offload]], Nodes count: 1, RootId [0000000000000000]]]

      4 comments

      Jason Orchard-ingram micro
      Forum|alt.badge.img+2

      Rescan repository + recreate job metadata

      If exclusion alone doesn’t work:

      1. Disable the NAS backup job
      2. Rescan the backup repository
      3. Remove the failing share from the job
      4. Re-add it
      5. Re-enable the job

      This rebuilds the NAS container mappings.

        Andanet
        Forum|alt.badge.img+12
        • Andanet
        • Veeam Legend
        • April 8, 2026

        hi ​@Benn 

        The issue could be related attempting to read the .copy_offload folder.

        Please could you try excluding the folder from the job and verify?

        Other check: 

        • Try a rescan of your NAS
        • Verify right permission for the  .copy_offload folder
        • Check hidden snapshots on the NAS

        Let me know! 

         

        Antonio D'Andrea | VMCE 2021 | VMCA 2022 | VMTSP2024 | Veeam Legend | VUG Italy Leader | Object First Ace | VCP6-DCV | I want it written on my tombstone "Please start a restore to the last valid backup"
          B
          • Benn
          • Author
          • New Here
          • April 8, 2026

          Rescan repository + recreate job metadata

          If exclusion alone doesn’t work:

          1. Disable the NAS backup job
          2. Rescan the backup repository
          3. Remove the failing share from the job
          4. Re-add it
          5. Re-enable the job

          This rebuilds the NAS container mappings.

           

          I have followed this step, the repairing of metadata completed successfully, however the backup again failed with the same error.

            coolsport00
            Forum|alt.badge.img+22
            • coolsport00
            • Veeam Legend
            • April 8, 2026

            Hi ​@Benn - Welcome to the Community!

            Keep in mind...the Community Hub is a forum of like-minded Veeam users. We are not official Veeam Support. We can offer suggestions to any issues community members post about, but reaching out to Veeam Support is the recommended avenue for troubleshooting, log perusing, and resolving most Veeam-related issues encountered.

            As it appears what ​@Jason Orchard-ingram micro suggested you to try has not worked, it is recommended you open a Support case with Veeam to look at your logs and see what is going on.

            Keep us posted on things go if you can.

            Best.

            Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
              Terms & ConditionsAccessibility statement