Hi Neelakantan,
Glad to hear that it worked, thank you for confirming and glad I could assist.
I can understand your assumption here, but when you use pre/post job scripts (and pre-freeze/post-thaw), Veeam does not do _anything_ to the script or the execution environment; Veeam simply executes the script using the native host methodology (e.g., for Powershell it's just the call operator, for bash scripts we just pass the script to the shell, etc), meaning that if you don't tell the shell what it needs, it won't find it. But Veeam does not touch or alter the script or the execution environment, it just sends the command to execute the script "as-is".
Glad to hear that it worked, thank you for confirming and glad I could assist.
I can understand your assumption here, but when you use pre/post job scripts (and pre-freeze/post-thaw), Veeam does not do _anything_ to the script or the execution environment; Veeam simply executes the script using the native host methodology (e.g., for Powershell it's just the call operator, for bash scripts we just pass the script to the shell, etc), meaning that if you don't tell the shell what it needs, it won't find it. But Veeam does not touch or alter the script or the execution environment, it just sends the command to execute the script "as-is".
Statistics: Posted by david.domask — May 29, 2024 9:42 am
