Uh, why isnt it lock to the folder it creates though or at least pointed to? That doesnt seem right to me... that seems like a weird design from Veeam if that is true... I also assume this is what is being talk about:
I assume this is what the OP is saying? IF I am not correct, please correct me.
Root folder to me would be like:
point to > D:\NasDrive -> Veeam makes: D:\NasDrive\VeeamBackup
Veeam Makes Folder for job/computer -> D:\NasDrive\VeeamBackup\Job ComputerName
That client should only read D:\NasDrive\VeeamBackup\Job ComputerName now unless other wise pointed to a different direction for another job.
If Veeam is reading everything in D:\NasDrive\VeeamBackup per client, that seems really silly programming there? IF so, no wonder there are issues going on with this design. What reason would the need to scan outside of its folder be if you dont mind me asking?
I assume this is what the OP is saying? IF I am not correct, please correct me.
Root folder to me would be like:
point to > D:\NasDrive -> Veeam makes: D:\NasDrive\VeeamBackup
Veeam Makes Folder for job/computer -> D:\NasDrive\VeeamBackup\Job ComputerName
That client should only read D:\NasDrive\VeeamBackup\Job ComputerName now unless other wise pointed to a different direction for another job.
If Veeam is reading everything in D:\NasDrive\VeeamBackup per client, that seems really silly programming there? IF so, no wonder there are issues going on with this design. What reason would the need to scan outside of its folder be if you dont mind me asking?
Statistics: Posted by mradr — May 25, 2024 7:02 am
