Anyway i think too , this setting should be easyly change in a XML inside VBO Settings as Feature Request
If you have Veeam Agent installed, then it's not possible to move the log directory and replace it with directory junction, because the log directory is also used by CBT driver and this behavior cannot be changed, until you uninstall it.
If you uninstall it, set the directory junction, reinstall the CBT driver and then try to back up the same server with Veeam Agent, it will fail the error "Error: The request is not supported. Error: in [VctSetCtStorePath] at step [5] Agent failed to process method {VeeamVolumeCt.SetUserStorePath}"
Happy sysdrive filling with the application log!
Why even doing this? I tried to free up some space as the upgrade to Veeam v13 requires... wait for it... 40GB of free space on sysdrive and it's always pain, to do this (temp dir also cannot be moved out of the sysdrive).
Could you please clarify which products are involved? I moved your comment from the Veeam Backup for Microsoft 365 forum, as it doesn’t appear to be related to that product.
To my understanding, you have a single machine with Veeam Backup & Replication and Veeam Agent deployed.
And now you are trying to use mklink to change the log folder to a different disk?
For Veeam Backup & Replication, please use the following KB to change Log Folder: https://www.veeam.com/kb1825
I'll have to double check for Veeam Agent for Windows.
thank you for your answer - my bad, that I did not notice the forum is for different product.
To my understanding, you have a single machine with Veeam Backup & Replication and Veeam Agent deployed.
And now you are trying to use mklink to change the log folder to a different disk?
Yes, that was exactly the case - Veeam Backup & Replication v12.3.2.4165. It is deployed on standalone physical machine which is backed up by Veeam Agent (as a part of the protection group) - the issue is with the CBT driver that uses the same directory as the log: if I use mklink to redirect the log out of system drive, the protection group backup fails with the described error.
