Veeam Restore Failed To Install Guest Agent Control As to your issue with backing up a DC VM with user name or bad password. Strange thing is that it does work on the old the ticket submitting process is quick. With the release of Update 3 of Veeam Backup & Replication we introduced the ability to manage agent from within the console. This was for both our Windows and Linux agents and aimed to add increased levels of manageability and control when deploying agents in larger enterprise type environments. Download Veeam Agent for Windows Beta (build: 2.0.0.594): here. This article provides a step by step guide to install Veeam Agent for Windows. New Veeam Agents for Windows and Linux will be supported and licensed per agent. Veeam Agent for Windows will be available soon and Veeam Agent for Linux is already released.
Note: We are using Veeam Backup & Restore 9.5 Update 2, with the server on a virtualized Windows 2012 Server Datacenter Edition, files located on the same LAN on a Linux server (fetched via the SSH option where it runs the perl scripts to transfer the data), a centralized vCenter 6.5 install on the same network; all on 10.100.0.0/16; and the target network for restore being a remote network, 10.163.0.0/16, on ESXi 6.5 server 'esxi01.remote', trying to restore 'vmserver07', through a proxy server veeamproxy02[.remote] located on the remote network and ESXi server. We have no problems backing up data or restoring when it's done over 'nbd' with no remote proxy setup.
SHORT OF IT: Everything, remote and local, is running VMware 6.5, and our Veeam install is all Veeam Backup & Restore 9.5 Update 2.
HELP!
We have setup a Veeam proxy server, 'veeamproxy02' or 10.163.100.10 on Windows 2012 on one of our remote networks from which we backup VMs to our local Veeam server. We did this so that we could get faster restores than the less-than-or-equal-to-1MB/sec 'nbd' speeds. We also installed a WAN accelerator on the server.
However we are having a problem restoring a virtual server, 'vmserver07', when specified explicitly through the backup proxy, known as 'veeam02[.remote]', at the remote site, and the error says something related to NFC (Network File Copy) (see below for the full error).
We choose Full VM Restore and, instead of 'automatically select proxy', we specifically choose the veeam02 proxy at the remote site. Things get running - 'start restore job', 'locking required backup files', 'queued for processing at <timestamp>', 'processing vmserver07', 'Required backup infrastructure resources have been assigned', and '6 files to restore (16.0 GB)' messages are all checked with green checkmarks meaning everything went okay; however 'Restoring [vmserver07] vmserver07/vmserver07.vmx' fails after 3 minutes and 19 seconds, and the restore process pukes and bails out with the following error message:
4/17/2018 4:18:56 PM Error Restore job failed Error: NFC storage connection is unavailable. Storage: [stg:datastore-6934,nfchost:host-6933,conn:10.100.10.1]. Storage display name: [vmserver07]. Failed to create NFC upload stream. NFC path: [nfc://conn:10.100.10.1,nfchost:host-6933,stg:datastore-6934@vmserver07/vmserver07.vmx].
Here, 10.100.10.1 is our central vCenter server (and 10.100.0.0/16 is our local network where Veeam is housed; 10.163.0.0/16 is the remote site where the remote ESXi server, VM guest veeamproxy02 [the Veeam proxy and WAN accelerator], and veeam07 VM guest is housed.
We have enabled NFC on the ESXi servers that contain vCenter (vmhost02.local), the desired instance to restore, vmserver07 (vmhost01.remote), the Windows 2012 instance running Veeam Backup & Restore 9.5 veeam01 (vmhost01.local). This is a total of three ESXi 6.5 w/ latest update patch servers and, as stated, NFC is enabled; in fact, all options on the management interface are enabled such as Provisioning, vMotion, etc - everything except 'Fault Tolerance Logging'. There are no firewalls enabled on the Windows virtual servers running Veeam master and Veeam proxy/WAN accelerator (veeam01.local and veeamproxy02.remote, respectively) as to ensure it's not a port blocking issue. The ESXi firewall is setup to allow all IPs to access the NFC service.
Veeam Restore Failed To Install Guest Agent Control
We restarted the ESXi host/hypervisor servers after enabling NFC to no avail. We found some information about the errors seen in /var/log/nfcd.log (see below) and the fix was to enable IPv6 on the main TCP/IP stack; this was done, the servers rebooted, but again the errors in nfcd.log persist and nfcd does not run even though its listed as enabled in 'chkconfig'.
As said above, of note is that 'nfcd' does not start successfully on the ESXi host/hypervisor servers (esxi01 and 02.local, esxi01.remote) even with NFC enabled on the management interface's TCP/IP stack. Is 'nfcd' supposed to be running for NFC to be enabled, or is it otherwise provided thru vpxa in VMware 6.5? Logs from /var/log/nfcd.log reveal the following when nfcd attempts to start/run:
2018-04-17T04:04:36Z nfcd[67503]: DictionaryLoad: Cannot open file '/usr/lib/vmware/config': No such file or directory. 2018-04-17T04:04:36Z nfcd[67503]: InitLog: Failed to establish log file 2018-04-17T04:04:36Z nfcd[67503]: Failed to switch netstack to the vSphereProvisioning stack. Using default management network stack. 2018-04-17T04:04:36Z nfcd[67503]: Failed to setup the IPV4 socket: No such file or directory.
There is a TCP/IP stack aside from the 'Default' one called 'Provisioning' on all the ESXi 6.5 servers in question, but each show zero (0) VMKernel adapters assigned. Do we need to do something with this interface? In the options, there is nothing aside from Name, DNS, Route (which doesn't let me edit anything), and the congestion control protocol/max # of connections under Advanced.
Any input is greatly appreciated.
Thank you!
Note: We are using Veeam Backup & Restore 9.5 Update 2, with the server on a virtualized Windows 2012 Server Datacenter Edition, files located on the same LAN on a Linux server (fetched via the SSH option where it runs the perl scripts to transfer the data), a centralized vCenter 6.5 install on the same network; all on 10.100.0.0/16; and the target network for restore being a remote network, 10.163.0.0/16, on ESXi 6.5 server 'esxi01.remote', trying to restore 'vmserver07', through a proxy server veeamproxy02[.remote] located on the remote network and ESXi server. We have no problems backing up data or restoring when it's done over 'nbd' with no remote proxy setup.
SHORT OF IT: Everything, remote and local, is running VMware 6.5, and our Veeam install is all Veeam Backup & Restore 9.5 Update 2.
HELP!
We have setup a Veeam proxy server, 'veeamproxy02' or 10.163.100.10 on Windows 2012 on one of our remote networks from which we backup VMs to our local Veeam server. We did this so that we could get faster restores than the less-than-or-equal-to-1MB/sec 'nbd' speeds. We also installed a WAN accelerator on the server.
However we are having a problem restoring a virtual server, 'vmserver07', when specified explicitly through the backup proxy, known as 'veeam02[.remote]', at the remote site, and the error says something related to NFC (Network File Copy) (see below for the full error).
We choose Full VM Restore and, instead of 'automatically select proxy', we specifically choose the veeam02 proxy at the remote site. Things get running - 'start restore job', 'locking required backup files', 'queued for processing at <timestamp>', 'processing vmserver07', 'Required backup infrastructure resources have been assigned', and '6 files to restore (16.0 GB)' messages are all checked with green checkmarks meaning everything went okay; however 'Restoring [vmserver07] vmserver07/vmserver07.vmx' fails after 3 minutes and 19 seconds, and the restore process pukes and bails out with the following error message:
4/17/2018 4:18:56 PM Error Restore job failed Error: NFC storage connection is unavailable. Storage: [stg:datastore-6934,nfchost:host-6933,conn:10.100.10.1]. Storage display name: [vmserver07]. Failed to create NFC upload stream. NFC path: [nfc://conn:10.100.10.1,nfchost:host-6933,stg:datastore-6934@vmserver07/vmserver07.vmx].
Here, 10.100.10.1 is our central vCenter server (and 10.100.0.0/16 is our local network where Veeam is housed; 10.163.0.0/16 is the remote site where the remote ESXi server, VM guest veeamproxy02 [the Veeam proxy and WAN accelerator], and veeam07 VM guest is housed.
We have enabled NFC on the ESXi servers that contain vCenter (vmhost02.local), the desired instance to restore, vmserver07 (vmhost01.remote), the Windows 2012 instance running Veeam Backup & Restore 9.5 veeam01 (vmhost01.local). This is a total of three ESXi 6.5 w/ latest update patch servers and, as stated, NFC is enabled; in fact, all options on the management interface are enabled such as Provisioning, vMotion, etc - everything except 'Fault Tolerance Logging'. There are no firewalls enabled on the Windows virtual servers running Veeam master and Veeam proxy/WAN accelerator (veeam01.local and veeamproxy02.remote, respectively) as to ensure it's not a port blocking issue. The ESXi firewall is setup to allow all IPs to access the NFC service.
We restarted the ESXi host/hypervisor servers after enabling NFC to no avail. We found some information about the errors seen in /var/log/nfcd.log (see below) and the fix was to enable IPv6 on the main TCP/IP stack; this was done, the servers rebooted, but again the errors in nfcd.log persist and nfcd does not run even though its listed as enabled in 'chkconfig'.
As said above, of note is that 'nfcd' does not start successfully on the ESXi host/hypervisor servers (esxi01 and 02.local, esxi01.remote) even with NFC enabled on the management interface's TCP/IP stack. Is 'nfcd' supposed to be running for NFC to be enabled, or is it otherwise provided thru vpxa in VMware 6.5? Logs from /var/log/nfcd.log reveal the following when nfcd attempts to start/run:
2018-04-17T04:04:36Z nfcd[67503]: DictionaryLoad: Cannot open file '/usr/lib/vmware/config': No such file or directory. 2018-04-17T04:04:36Z nfcd[67503]: InitLog: Failed to establish log file 2018-04-17T04:04:36Z nfcd[67503]: Failed to switch netstack to the vSphereProvisioning stack. Using default management network stack. 2018-04-17T04:04:36Z nfcd[67503]: Failed to setup the IPV4 socket: No such file or directory.
There is a TCP/IP stack aside from the 'Default' one called 'Provisioning' on all the ESXi 6.5 servers in question, but each show zero (0) VMKernel adapters assigned. Do we need to do something with this interface? In the options, there is nothing aside from Name, DNS, Route (which doesn't let me edit anything), and the congestion control protocol/max # of connections under Advanced.
Any input is greatly appreciated.
Thank you!