SOBR Offload Job POSIX Error?

[jlhester]

Any ideas why the SOBR offload Job can't seem to access certain files on the Exagrid? Veeam reports POSIX Error. Permission Denied. Failed to read....File name and path. I have noticed that there is a NEW file in the same backup job directory(s) named "File name_meta.vbk" and all backup job files that have this additional file receive the same error. I tried a restore off of the same backup job vbk and it fails too with permissions denied issues. Contacted Exagrid support and they checked NFS permissions from SSH connection.....All good. Support case Veeam now opened.....Case # 04645151. Tier 1 engineer has logs and is reviewing. Excellent support. What is rlenameeally strange is that backup jobs are tiering off fine out of the same Exagrid and backup directories. The key seems to be the "File Name_meta.vbk" 17 MB file. No access permissions are applied to the SOBR......"Access to Everyone".

Thanks......Jim

[veremin]

Let's wait for the results of debug logs investigation - should shed some light on this rather strange behaviour.

[jlhester]

Unfortunately, due to Houston's ice storm we didn't get to work this issue from Monday-Friday this past week. No power, no internet, no worries. Re-contacted Veeam Support and the case has new uploaded logs and has been escalated to level two support. Waiting top hear back from them. Some backup files are uploading to Azure without issues, however the original or first offload backup files are still failing with same errors.

[jlhester]

UPDATE: After working with Veeam and Exagrid support, we are investigating a pointer (link) issue in Exagrid's deduplication process. Awaiting Exagrid engineering for next update. Good job of teaming between Veeam Level 2 and Exagrid. Jim