12.1 - NAS backup fails due to inaccessible subfolder

[DanielJ]

VBR 12.1. A NAS backup job that backs up a DFS root and everything under it fails after one of the folders below it no longer can be accessed since the path it points to is unavailable. After filtering that folder from the job, it succeeds. I had expected the job to warn about the inaccessible folder, or simply report it at the end of the session. It seems like an unexpected and unwanted behaviour to fail the whole job just because a subfolder is inaccessible. It might be coincidence but it seems like this started happening right after upgrade from 12.0 to 12.1. The session logs before the upgrade does not mention the folder at all, and I don't know exactly when the folder became inaccessible.

2024-01-08 20:44:57 :: The network name cannot be found. Failed to initialize win search iterator. Path: [Prefix [\\?\UNC\], Path [redacted path to the inaccessible folder]]

Ticket with job logs: 07081211

[Dima P.]

Hello Daniel,

Can you check if the severity is set to warn you about skipped objects or not in the NAS backup job settings?

[DanielJ]

Nothing is checked under Notifications. I should also clarify that the job scope is the single DFS root path, and the inaccessible folder is simply a subfolder to that path (not explicitly added to the job, but now excluded from the job).

[Dima P.]

You can check the option to 'make file or folder processing issue result a job warning' this would mark the job results yellow whenever you have at least on file or folder that cannot be reached due to network issues or due to locks. That should add the notification you've been looking for. Thank you!