We have a newer VM that is in a DMZ network, not part of the domain or anything, so its IP address is filtered via the firewall. Is it OK to have these backup jobs fail every day with this type of error message:
Failed to prepare guest for hot backup. Error: Failed to connect to guest agent. Errors: 'Cannot connect to the host's administrative share. Host: [SERVERNAME]. Account: [SERVERNAME\Administrator]. Win32 error:The network name cannot be found. Code: 67 Cannot connect to the host's administrative share. Host: [192.168.1.80]. Account: [SERVERNAME\Administrator]. Win32 error:The network name cannot be found. Code: 67 '
Error: Failed to connect to guest agent. Errors: 'Cannot connect to the host's administrative share. Host: [SERVERNAME]. Account: [SERVERNAME\Administrator]. Win32 error:The network name cannot be found. Code: 67 Cannot connect to the host's administrative share. Host: [192.168.1.80]. Account: [SERVERNAME\Administrator]. Win32 error:The network name cannot be found. Code: 67 '
Is it ok to turn off application aware processing? Its not hosting any type of transnational database or anything. The VM is and will still be backed up and restorable correct?
How about other machines where Testing admin share accessibility via VIX results in Error code 0x80004005?
Nevermind the last bit about the vix error 0x80004005. That was resolved by the EnableLUA to a 0 in the registry (and reboot).
But if I have a VM in a different, isolated network, of course the test will fail on these steps:
Connecting to guest OS via RPC
Testing admin share accessibility via RPC.
The Veeam and Veeam Proxy server do not have ability to reach that network in that way as its isolated and segmented off (different security levels).
If those VMs aren't running any VSS-aware applications, you can simply disable that functionality; that won't affect backup recoverability anyhow. Thanks.