Skip to main content
Question

backup failure for single nas file share

  • April 8, 2026
  • 3 comments
  • 12 views

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]]]

3 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
  • 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! 

 


  • 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.