new1234.jpg

Archive

Posts Tagged ‘Hostfile’

Veeam: Client error: NFC storage connection is unavailable

December 10th, 2014 1 comment

Last week I added a new vSphere host in my homelab, after I configured and started my backup job in the Backup & Replication 7.0 patch 4 environment I received this error messages:

Processing ‘DC01’ Error: Client error: NFC storage connection is unavailable. Storage: [stg:datastore-12,nfchost:host-10,conn:vce01.vmpros.local]. Storage display name: [ESX01_VMFS02].
Failed to create NFC download stream. NFC path: [nfc://conn:vce01.vmpros.local,nfchost:host-10,stg:datastore-12@DC01/DC01.vmx].

image

 

Solution

When you look at the Backup Job log file you can see the details, logfile location: C:\ProgramData\Veeam\Backup\VMpros_-_Backup_01

In my case Veeam Backup could resolve my VMware vCenter 5.5 server but when he try to contact the vSphere host with some local datastores the backup failed. I tried to ping the hosts and couldn’t resolve the hostname of my vSphere host.

Make sure you have:

– Added the vSphere host in DNS, create a A record in your DNS server

Optionally: Add the vSphere hostsname(s) and IP-address(es) in the hostfile at your Veeam Backup server

 

End result

 

image

 

More information: Veeam

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Data Recovery – Failed to create snapshot for <server>, (vcb api exeption)

June 21st, 2010 2 comments

Last week we upgraded VMware Data Recovery from version 1.1 to 1.2. After rerun the backup schedule I received this error:

Failed to create snapshot for <server>. error –3948 ( vcb api exeption)

 

My backup starts > Create a new snapshot > Few seconds later… the snapshot is removed and get this warning..

image

  Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: VM Console error: Unable to connect to the MKS: Failed to connect to the server (1010828)

August 29th, 2009 29 comments

“Unable to connect to the MKS: Failed to connect to the server 172.16.254.202:902” or “Unable to connect to the MKS: Failed to connect to the server no such host is known”

image

Solution:

To avoid losing access to the ESX host, perform the following steps:

1. Add the ESX server in your DNS

2. Edit your hostfile on the workstation (C:\Windows\System32\Drivers\etc\hosts\) and add your ESX server

 

After adding the ESX by DNS in my hostfile and restarted the VI Client I was able to open Console screen.

[ad#ad-banner]

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

Categories: VMware Tags: , , , ,