Hello,
We have issues with our VCC-B.
I noticed when checking VCC GUI/History/System that Veeam One Agent which is installed on all VCC related servers, gather logs that regularly fill up OS disks on at least VCC and Repo servers.
It seems that the Veeam product cause issues with our critical VCC-B solution (we are an SP).
Could this really be the case ?
Is the path by default really the C-drive ?
How should we move forward in our troubleshooting ?
We have issues with our VCC-B.
I noticed when checking VCC GUI/History/System that Veeam One Agent which is installed on all VCC related servers, gather logs that regularly fill up OS disks on at least VCC and Repo servers.
It seems that the Veeam product cause issues with our critical VCC-B solution (we are an SP).
Could this really be the case ?
Is the path by default really the C-drive ?
How should we move forward in our troubleshooting ?
Statistics: Posted by JLundgren — Mar 26, 2024 7:52 pm