VADP Recovery using NBD transport mode instead of SAN

We are tryng recover VM and given transport mode as SAN. But it took NBD transport mode automatically and giving below errors

Requesting 1 recover session(s) from server.

07/10/16 08:22:40.000327

Total estimated disk space needed for recover is 2071 GB.

Recover start time: 10/07/2016 08:20:32

07/10/16 08:22:40.000327

openVddkHandle() successful for disk number 1

Using 'nbd' as the transport mode for VirtualDisk_1.

83330:nsrvadp_recover: Error writing data at offset 39483392, size 8192. Error: The following internal error occurred: An error was returned from nsrvddk.exe: Error writing to disk: VDDK Error: NBD_ERR_NETWORK_CONNECT.

97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VM

DK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written instead of 261632 bytes for file : 1:\virtualdisk_1.vmdk.97261:nsrvadp_recover: Error writing to VMDK: 0 bytes written inst

ead

.....................................................................................................................................................Error writing buffer to VMDK.

vadp_chunk_write() vmdk write Queue error: Write aborted

vadp_chunk_write() vmdk write Queue error: Write aborted

vadp_chunk_write() vmdk write Queue error: Write aborted

vadp_chunk_write() vmdk write Queue error: Write aborted

vadp_chunk_write() vmdk write Queue error: Write aborted

vadp_chunk_write() vmdk write Queue error: Write aborted

vadp_chunk_write() vmdk write Queue error: Write aborted

vadp_chunk_write() vmdk write Queue error: Write aborted

vadp_chunk_write() vmdk write Queue error: Write aborted

vadp_chunk_write() vmdk write Queue error: Write aborted

vadp_chunk_write() vmdk write Queue error: Write aborted

vadp_chunk_write() vmdk write Queue error: Write aborted

vadp_chunk_write() vmdk write Queue error: Write aborted

vadp_chunk_write() vmdk write Queue error: Write aborted

Please help me

0 Kudos
7 Replies
ledugarte
2 Iron

Re: VADP Recovery using NBD transport mode instead of SAN

Hello.

For SAN transport mode, you need a physical proxy machine with SAN connection to storage where residing VM's. Please take a review to VMware Integration Guide for details. If SAN transport mode fails, recover job tries to use NBD trasport mode.

You are getting some network errors when restore job use NBD. Have you checked network speed and duplex mode in proxy host?.

Another tip: A few months ago, I had similar error and root cause was special characters in "Annotations Notes" in virtual machine I was trying to recover. I erase all special characters in annotations and recover ends fine.

Hope it helps.

0 Kudos

Re: VADP Recovery using NBD transport mode instead of SAN

Hello Ledugarte,

Physical proxy server has SAN connection with storage and those datastores also presented to Proxy host aswel.

But it is autoconverted to NBD.

I heard somewhere that VADP recovery from tapes backup is not supported by networker. is it true?

0 Kudos
ledugarte
2 Iron

Re: VADP Recovery using NBD transport mode instead of SAN

Hello.

A few questions:

1. What version of operative system has the machine where you are launching networker user?

2. Does the proxy has read/write access to LUN?

3. Have you checked all permissions for vcenter user?

4. Is NBD transport mode working?

For your last question: tape backups are supported with VADP for backup and recover.

0 Kudos

Re: VADP Recovery using NBD transport mode instead of SAN

Hello

1. What version of operative system has the machine where you are launching networker user?

ANS: Windows Server 2008 and NW version is 8.2.1

2. Does the proxy has read/write access to LUN?

ANS: Yes it has. Confirmed by Storage team.

BTW can u tell me how to check this? so that I will check my own for double sure. Here Storage is EMC VNX

3. Have you checked all permissions for vcenter user?

Ans: Yes. It has all privileges with administrator access

4. Is NBD transport mode working?

Ans: Data writing speed is dead slow. 300kbps

Let me know please, if you require any more details

0 Kudos
ledugarte
2 Iron

Re: VADP Recovery using NBD transport mode instead of SAN

You can check if Proxy is in the same zone than ESXi. If so, proxy has r/w access to LUNs.

Did you run diskpart in your proxy? I suppose you are running Networker User from proxy host, and then, that is the 2008 server you mentioned. You need to run diskpart and enable SAN POLICY.

Please take a look to Vcenter and ESXi versions. If you have version 5, you need take some steps before use SAN transport.

0 Kudos

Re: VADP Recovery using NBD transport mode instead of SAN

Hello Ledugarte,

SAN Policy is already enabled. And V center version is 5.5

Regards,

0 Kudos
ledugarte
2 Iron

Re: VADP Recovery using NBD transport mode instead of SAN

0 Kudos