While implementing Veeam Replication recently (see my posts Part 1, Part 2 and Part 3) , I was searching for information about the following error
Error: Client error: NFC storage connection is unavailable
and I stumbled across this post
I thought I would share another possible workaround for the above error. I was getting the following error when trying to backup a new environment
27/06/2012 12:42:35 :: Error: Client error: NFC storage connection is unavailable. Storage: [stg:datastore-188,nfchost:host-221,conn:prd-vc1]. Storage display name: [ZONE-OS].
Failed to create NFC download stream. NFC path: [nfc://conn:prd-vc1,nfchost:host-221,stg:[email protected]/gry-sc2.vmx].
so a quick search of the KB articles came up with http://www.veeam.com/KB1198 , I tried everything in the article but still the error message persisted.
Was almost at wits end , so took a final look in the log files and notice the job was trying to use a 169.x.x.x address as the proxy. A colleague then pipped up something about checking the Network binding (in Windows 208 R2). The perculiar thing this is a hidden menu , so steps take were
1. Open Network and Sharing Center
2. Click on ‘Change Adapter Settings’
3. Press ‘ALT’ key to bring up menu
4. Click on ‘Advanced’
5. Select ‘Advanced Settings’
You will now be able to change the order of connections. In my case I had to put the connection in the management VLAN at the top of the list.
After reading and thinking “What an informative post!” , I suddenly realised I had posted it nearly a year earlier!!
So posting a quick blog post for information purposes.