We have facing issue with exchange server backup with AAIP. Disabling AAIP , backup will work
Error :Failed to inventory guest system: Veeam Guest Agent is not started
Failed to prepare guest for hot backup. Error: Cannot connect to remote SCM database. Machine
Logs:
Error Veeam Guest Agent is not started (System.Exception) Error Failed to inventory guest system: Veeam Guest Agent is not started Error Failed to invoke guest call Error Cannot connect to remote SCM database. Machine. Requested rights: [0x8000000]. Error Win32 error: Access is denied. Code: 5 (System.UnauthorizedAccessException)
VBR v12
Proxy servers are Linux
GIP server is linux server and is not a backup proxy and credential test passed
VBR server and other proxy servers are not in domain
Please advise.
Best answer by coolsport00
Hi @Nikks -
The GIP server cannot be a Linux server. It has to be a phys or virt WINDOWS server as stated in the User Guide:
What change I need to make on this scenario, because if VBR server is automatically used, why access is denied is getting and cannot install non-persistent agents ?
I can’t say as I’m not aware fully of your environment. You can look in Veeam logs → C:\ProgramData\Veeam\Backup\<job-name>.log to see if anything shows there. Or, contact Veeam Support.
Thanks. Checked and observed VBR server cannot access Guest VM C$ and ADMIN$. Could it be the reason ? What i need to do with existing GIP proxy server in Linux , remove it or let it be there ?
Thanks. Checked and observed VBR server cannot access Guest VM C$ and ADMIN$. Could it be the reason ? What i need to do with existing GIP proxy server in Linux , remove it or let it be there ?
That would seem to be the reason imo...yes. I don’t know what your Linux server in Veeam is...but it’s not a GIP server, because again...a GIP server can only be a Windows server. If this Linux server you have in Veeam is not used for anything else, you can remove it if you want. Before removal, you must not have it be assigned any role in a Job or in Veeam.
Because you’re VBR is not on the domain, you should probably work with Support to help with the connectivity issue you’re having with VBR contacting your DB VM.
