Availability for the Always-On Enterprise
Gostev
Veeam Software
Posts: 22808
Liked: 2801 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Failed to create NFC download stream

Post by Gostev » Dec 16, 2010 2:24 pm

Thank you for posting the resolution! So this ended up to be DNS issue...

Matt-WGSB
Novice
Posts: 4
Liked: never
Joined: Sep 27, 2011 6:40 pm
Full Name: Matthew Smith
Contact:

Re: Failed to create NFC download stream

Post by Matt-WGSB » Sep 28, 2011 7:49 pm

I just ran into the same issue on Veeam 5.0.2. The Veeam server was not added to the domain, though it was statically configured to look to the correct DNS server. I added it to the domain and a retry was successful. 2 cents in case it helps anyone else.

Andreas Neufert
Veeam Software
Posts: 2818
Liked: 478 times
Joined: May 04, 2011 8:36 am
Full Name: @AndyandtheVMs Veeam PM
Location: Germany
Contact:

Re: Failed to create NFC download stream

Post by Andreas Neufert » Aug 14, 2012 10:44 am 1 person likes this post

Had the same issue at a POC.

It was a DNS Error.
Backup Server and VCenter DNS worked, but on the Proxys the ESX Hosts where not resolved.

Andreas Neufert
Veeam Software
Posts: 2818
Liked: 478 times
Joined: May 04, 2011 8:36 am
Full Name: @AndyandtheVMs Veeam PM
Location: Germany
Contact:

Re: Failed to create NFC download stream

Post by Andreas Neufert » Jan 07, 2013 7:33 am 1 person likes this post

At another customer it was caused by a special character in datastore name.

dellock6
Veeam Software
Posts: 5437
Liked: 1480 times
Joined: Jul 26, 2009 3:39 pm
Full Name: Luca Dell'Oca
Location: Varese, Italy
Contact:

Re: Failed to create NFC download stream

Post by dellock6 » Jan 07, 2013 10:08 pm 1 person likes this post

Andreas, it happened right today at a customer too, some "genius" from another System Integrator following this customer before me configured one of the datastores with an exclamation mark in the name......

Luca.
Luca Dell'Oca
EMEA Cloud Architect @ Veeam Software

@dellock6
http://www.virtualtothecore.com/en/
vExpert 2011-2012-2013-2014-2015-2016-2017-2018
Veeam VMCE #1

Gostev
Veeam Software
Posts: 22808
Liked: 2801 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Failed to create NFC download stream

Post by Gostev » Jan 07, 2013 11:39 pm 1 person likes this post

Was it named like "DO NOT DELETE!!!" or something? :D

tsightler
Veeam Software
Posts: 5167
Liked: 2057 times
Joined: Jun 05, 2009 12:57 pm
Full Name: Tom Sightler
Contact:

Re: Failed to create NFC download stream

Post by tsightler » Jan 08, 2013 12:07 am 1 person likes this post

I had a client with a datastore named something along the lines of "Old & Slow - No New VMs!"

dellock6
Veeam Software
Posts: 5437
Liked: 1480 times
Joined: Jul 26, 2009 3:39 pm
Full Name: Luca Dell'Oca
Location: Varese, Italy
Contact:

Re: Failed to create NFC download stream

Post by dellock6 » Jan 08, 2013 12:09 am 2 people like this post

No kidding, it was:

!Backup only! Do not place VMs here!

Right as I wrote it here (well, was in italian to be honest, but that's the exact translation) :D
Luca Dell'Oca
EMEA Cloud Architect @ Veeam Software

@dellock6
http://www.virtualtothecore.com/en/
vExpert 2011-2012-2013-2014-2015-2016-2017-2018
Veeam VMCE #1

Ben Milligan
Expert
Posts: 173
Liked: 40 times
Joined: Jan 01, 2006 1:01 am
Contact:

Re: Failed to create NFC download stream

Post by Ben Milligan » Jan 08, 2013 1:29 pm 2 people like this post

A bit of a deeper dive on this for you folks in the field. Our source agent logs will many times point directly at the culprit if it is an issue of ports/permissions/DNS. These are the most common reasons we see this behavior.

IE: Agent.JOBNAME.Source.log:
Look for: "Creating NFC download stream"

You'll first see the host and port the agent is attempting to communicate with:
Host: [Test-vc01]
Port: [443]
Successfully logged in ( server: [Test-vc01], user: [test\bmilligan] )


This is the control connection above to the vCenter. Next you'll see the NFC connection to the host being made as determined by vCenter:
Native NFC file path: [[SAN-Test-LUN1] TestVM/TestVM.vmx].
Reconnecting to the NFC storage. Storage: [stg:datastore-25648,nfchost:host-458,conn:test-vc01]. Display name: [SAN-Test-LUN1].
Preferred NFC server: [host-458].
Connecting to NFC session. Target host: [ESX1.test.local]. Storage: [SAN-Test-LUN1]. VI SOAP connection ID: [test-vc01].
NFC service: [vpxa-nfc]. Port: [902].


If you see "failed" next to this line: Establishing connection with the host [ESX1.test.local]. Port: [902]., it's fairly clear you need to modify your firewall.

Next, you'll see the hostname DNS resolution attempt:
Resolving host name (ESX1.test.local) to IP address...


If you see failed next to the above line, you need to update your DNS records so that host is resolvable from the source proxy.

Lastly, you'll see the file begin to download:
Starting file download. File: [[SAN-Test-LUN1] TestVM/TestVM.vmx].

When it fails here, we're talking permissions to download the file at this point. As you can see, all three problems are fairly clear in logs context.

Hope this helps!

Ben Milligan
Expert
Posts: 173
Liked: 40 times
Joined: Jan 01, 2006 1:01 am
Contact:

Re: Failed to create NFC download stream

Post by Ben Milligan » Jan 08, 2013 2:07 pm

Oh! Forgot one thing. You'll see this in the target agent log when there is an upload failure during replication job from target proxy to target host/datastore, as opposed to source agent log.

cackerson
Novice
Posts: 6
Liked: 2 times
Joined: Feb 24, 2012 5:59 pm
Full Name: craig ackerson
Contact:

Re: Failed to create NFC download stream

Post by cackerson » Jan 14, 2013 3:22 pm

"Connecting to NFC session. Target host: [ESX1.test.local]. Storage: [SAN-Test-LUN1]. VI SOAP connection ID: [test-vc01].
NFC service: [vpxa-nfc]. Port: [902].[/i]

If you see "failed" next to this line: Establishing connection with the host [ESX1.test.local]. Port: [902]., it's fairly clear you need to modify your firewall."

Ben - have the same issue and support told me to modify my firewall. But they could not tell me what firewall. Do you mean a Windows firewall? On the Machine being replicated or the proxxy? Or do you mean a firewall across a WAN link?

Ben Milligan
Expert
Posts: 173
Liked: 40 times
Joined: Jan 01, 2006 1:01 am
Contact:

Re: Failed to create NFC download stream

Post by Ben Milligan » Jan 14, 2013 3:27 pm 2 people like this post

Sorry for any lack of clarify here.

Port 902 needs to be open between the Source Proxy and the source ESX(i) host where the VM you are backing up/replicating resides. It would also need to be open between the target proxy and target ESX(i) host on destination side for replication. Most times this is a Windows firewall or router in between the source proxy and source host that is disallowing the traffic. You can open vSphere client and use datastore browser to test file copies to/from the datastore to your Windows server running as the Veeam Backup source proxy for manual testing as it uses the same port. Once this is working then the job should not throw this error any more.

cackerson
Novice
Posts: 6
Liked: 2 times
Joined: Feb 24, 2012 5:59 pm
Full Name: craig ackerson
Contact:

Re: Failed to create NFC download stream

Post by cackerson » Jan 14, 2013 9:16 pm

After getting the Port: [902] error message mail failback did not work. I now have a "Veeam Replication Failback Snapshot" in my Snapshot Manager in Vsphere Client.

Is it ok to delete this snapshot?

Ben Milligan
Expert
Posts: 173
Liked: 40 times
Joined: Jan 01, 2006 1:01 am
Contact:

Re: Failed to create NFC download stream

Post by Ben Milligan » Jan 14, 2013 9:57 pm

Craig - that snapshot is likely not filled with good data. It resides on the original source machine, and contains the failback data (changes) from the replica. You could revert to that snapshot, to ensure it is good/bad, then delete if its not needed. If it failed during the data transfer, which is likely considering a block on port 902, the snapshot likely contains no information. In that case, its OK to delete the snap, and retry the failback after port 902 is confirmed open between target proxy and target host.

Hope this helps!

Dwayneair
Lurker
Posts: 2
Liked: never
Joined: Dec 10, 2012 7:02 pm
Full Name: Dwayne Lovely
Location: Albany NY
Contact:

Re: Failed to create NFC download stream

Post by Dwayneair » Feb 04, 2013 4:25 pm

I posted on an older Post with very similar issues, and the Administrator pointed me here.
After placing a service request for the same error message, we were able to find out that one of the Hosts was backing up with no issues but any of the others would result in this same error. 1) Checked DNS on all components and Proxies and yes we had a typo in the Host files for Host ESX1 and ESX2 (the 2 problem children). Fixed it.
But now only a couple of the backups work and nothing was working from Host ESX3 ???? so we then 2) disconnected a mapped drive (N:) to the repository (my NAS), I guess there are issues when you do this on the Veeam Backup server. and 3) Recreated the backups but selected the Virtual servers from the Standalone Host objects instead of the VCenter object. Now everything seems to be working fine. Although I have yet to test vmotioning one of the servers over to a different Host and seeing if the backup will follow or error out.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 23 guests