Highlighted

How much mount space for VADP mountpoint when using NBD transport

Jump to solution

Hello,

We are having problems with VADP image level backup of a VM which has about 2.3TB of data in use.
Other client which are smaller are working fine.

Does anyone have an idea how big the mount space should be on the VADP Proxy Host ?

We are using Networker 7.6.2, Vsphere 4.1 and the client is running Windows 2008 R2 (fileserver).

kind regards,
Tom.

0 Kudos
1 Solution

Accepted Solutions

Re: How mount space for VADP mountpoint when using NBD transport

Jump to solution

1TB is also a limitation for NBD with VADP.
See my discussion on the vmware community:http://communities.vmware.com/message/1861067

see http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vddk_prog_guide.pdf

0 Kudos
6 Replies
ble1
5 Iridium

Re: How mount space for VADP mountpoint when using NBD transport

Jump to solution

Do you have any logs from VmWare side?  I know 3.5 and 4.x had some limits near 2TB due to LVM used on LUN size (they do not use GPT), but I guess this is not the case here.  If this fails during network copy, I would suggest to check vm log to see if there is anything related to NFC error (NFC is protocol used to copy data).

But then again, whole thing might be even simpler if following article is still correct:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101327...

In essence, it says, if data > 1TB - no go for nbd.

0 Kudos
pbina
2 Bronze

Re: How mount space for VADP mountpoint when using NBD transport

Jump to solution

Hi Tom,

Please have a look at page 29 of

EMC NetWorker

Release 7.6 Service Pack 2

Integration Guide

P/N 300-011-693

Space requirement changes on proxy for VADP vs. VCB

In previous NetWorker releases using VCB, extra space was required for the mount point on the VCB proxy for copy operations during backup and recovery. With NetWorker release 7.6 SP2, the VADP proxy requires significantly less space (typically, around 10% of the VM data size).

HTH,

0 Kudos

Re: How mount space for VADP mountpoint when using NBD transport

Jump to solution

I don't know about this... since we are using VADP in stead of VCB.

The NW VMW integration guide says that the mount dir needs about 10% of the VM Size, but then again...  I'm wondering how he deals with the initial backup.... the initial size of the VM which is about 2.3TB ?

With NBD he needs to copy that data over the Network to the proxy host.. so..... what about that ?

And the error is not very clear... below I will show you the Networker savegroup log file:

Initializing VADP Configuration.

Using pwvbu01 as the VADP proxy server host for client PWVFILE05.

Application information attribute VADP_HOST for client PWVFILE05 is set to "pwvvmvc02".

Application information attribute VADP_DISABLE_FLR for client PWVFILE05 is set to default value of "No".

Application information attribute VADP_BACKUPROOT for client PWVFILE05 is set to "V:\backupvmware".

Application information attribute VADP_TRANSPORT_MODE for client PWVFILE05 is set to "NBD".

Application information attribute VADP_MAX_RETRIES for client PWVFILE05 is set to "0".

Application information attribute VADP_MAX_BACKOFF_TIME for client PWVFILE05 is set to "20".

Trying to reset the client resource application information attributes.

Application information attribute VADP_HYPERVISOR for client PWVFILE05 is set to "pwvvmvc02".

VC\ESX Host Name        : 10.128.2.5

VC\ESX Port             : 443

VC\ESX Username         : pwvgrp\Sys_vdap

Mount point             : V:\backupvmware\PWVFILE05

Flavor                  : fullvm

Transport Mode          : nbd

Max retry               : 0

Max backoff time        : 20

VDDK Install Directory: C:\Program Files\Legato\nsr\plugins\VDDK.

VADP VM-TMP Directory Location: V:\backupvmware\PWVFILE05\PWVFILE05\PWVFILE05-tmp\letters\1.

Temporary Directory for VM created.

VADP TMP Directory Location: V:\backupvmware\PWVFILE05\PWVFILE05\tmp.

Temporary Directory for VADP created.

Temporary vmMntLoc Directory for VADP created.

Performing the backup via the Virtual Center.

Trying to connect to the VM using ipaddr/DNS name 'PWVFILE05'.

Performing a FULL Image level backup.

Creating snapshot for PWVFILE05.

Creating snapshot for 'vm-2153' ...

Task is -1% complete

Task is 95% complete

Task is 95% complete

Task is 95% complete

Task is 95% complete

74854:nsrvadp_save: The following VMware related error occured: Unable to create snapshot '_VADP-BACKUP_' for VM: vm-2153.  Details: 'An error occurred for task 'CreateSnapshot_Task'.  Details: Operation timed out.'.

80405:nsrvadp_save: Could not create Snapshot for VM 'PWVFILE05'.

Temporary directory 'V:\backupvmware\PWVFILE05' for VADP deleted.

0 Kudos

Re: How mount space for VADP mountpoint when using NBD transport

Jump to solution

Can anyone tell me how traffic is routed when using NBD transport.

So we have an ESX server, hosting the VM and a VCenter

The we have a backup server which acts as proxy host (physical).

During inital backup, the proxy host copies about 10% if the original VM size over the network to the mount space (snapshot metadata I think).

But what about the actual data ?

0 Kudos
ble1
5 Iridium

Re: How mount space for VADP mountpoint when using NBD transport

Jump to solution

NBD copies data from ESX host where VM is running to your proxy host.  This is highly likely VmW issue so I would suggest you also open a thread over at:

http://communities.vmware.com/community/vmtn/server/vsphere/datarecovery-vcb?view=discussions

The article stating 1TB limit for nbd applies to VDDK 1.0 as well (while VDDK 1.1 is available it hasn't been certified yet with nbd from what I could find on VMWare site).  This makes be believe VADP is affected as well.

Re: How mount space for VADP mountpoint when using NBD transport

Jump to solution

1TB is also a limitation for NBD with VADP.
See my discussion on the vmware community:http://communities.vmware.com/message/1861067

see http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vddk_prog_guide.pdf

0 Kudos