transport mode ignoring whats in the client config

You want to use hotadd? Have you checked all prerequisites?

Which VMware version is running?

NW 8.2 SP1 and later VMware Integration Guide, Rev 15

Page 136

--

l You must perform the following prerequisites on the NetWorker server/proxy machine

in order to run vSphere version 5.5 and 6.0:

1. Since the registry key for SSL verification is not set by default, add the following

keypath in the registry:

'HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/VMware, Inc./VMware

Virtual Disk Development Kit'

Add a DWORD VerifySSLCertificates and set it to zero ('VerifySSLCertificates=0').

This will disable SSL verification for all VDDK Hotadd operations.

2. Install .NET framework 3.5.1 or later on the proxy. In Windows 2008 R2, even

though the .NET framework is bundled with the operating system, ensure that you

enable the framework under Server Manager- > features.

3. Install VC++ runtime 9.0 (VC++2008 SP1) on the proxy. The following link provides

more details:

http://www.microsoft.com/en-us/download/details.aspx?id=2092

The section Limitations to vSphere 5.5 and 6.0 support on page 138 provides

information on limitations when using vSphere 5.5 or 6.0 with the VADP solution.

--

yes sir,

i have configured those pre-reqs. the thing that got me started in the first place was seeing that SOME vm's were taking 6+ hours to back up under 100gb. when i checked the log,those VM's were using NBD instead of Hotadd.

i cannot seem to find any rhyme or reason to why, which is why i started playing with the individual configs. some of the hotadd systems are on different hosts and luns as the proxy, so that doesnt apear to be the issue.

none of these vms' are over 250gb (many under 100gb). so i dont think its a block size issue.

any other suggestions?

Thanks for the pointer.

so, now i am getting the expected result. it simply sits there, not doing anything. in vcenter you can see that a snapshot is taken, but its not mounting it. the systems are on the SAME LUN and VM host...... nothing in the log at all at this time.

the backups run in the context of the vcenter administrator account... so permissions shouldent be a problem.

thoughts or suggestions?

ah, are you thinking it gets its config from the VADP proxy? i will try that out immediatly.

in the meantime here are teh settings from VUSVADP01

nsradmin> print type:"NSR client"; name:VUSVADP01

                        type: NSR client;

                        name: VUSVADP01;

                      server: susbck05.llsa.local;

                   client id: \

a59ad8ad-00000004-4fe8ab82-4fe8ab81-00011800-b73b72fe;

            scheduled backup: Enabled;

                     comment: ;

             Save operations: ;

            archive services: Enabled;

                    schedule: Default;

               browse policy: Month;

            retention policy: Month;

                  statistics: elapsed = 690, index size (KB) = 0,

                              amount used (KB) = 0, entries = 0;

                   directive: VCB directive;

                       group: Default, index;

                    save set: All;

  Backup renamed directories: Disabled;

          Checkpoint enabled: Disabled;

      Checkpoint granularity: Directory;

Parallel save streams per save set: Disabled;

                    priority: 500;

   File inactivity threshold: 0;

File inactivity alert threshold: 0;

               remote access: ;

                 remote user: ;

                    password: ;

         NAS management user: ;

     NAS management password: ;

        NAS file access user: ;

    NAS file access password: ;

              backup command: ;

                 Pre command: ;

                Post command: ;

     application information: VADP_MAX_BACKOFF_TIME=10,

                              VADP_TRANSPORT_MODE=hotadd|nbd,

                              VADP_HOST=susvc01.llsa.local,

                              "VADP_BACKUPROOT=c:\\mnt", VADP_MAX_RETRIES=0,

                              VADP_DISABLE_FLR=No;

     ndmp vendor information: ;

                        ndmp: No;

                  NAS device: No;

             NDMP array name: ;

  NAS device management name: ;

storage replication policy name: ;

       De-duplication backup: No;

         De-duplication node: ;

                        Pool: ;

          Data Domain backup: Yes;

       Data Domain interface: IP;

               Client direct: Enabled;

         Probe resource name: ;

              virtual client: No;

          Block based backup: No;

               physical host: ;

           Proxy backup type: ;

           Proxy backup host: ;

             executable path: ;

    server network interface: ;

                     aliases: VUSVADP01, vusvadp01.llsa.local,

                              VUSVADP01.llsa.local, vusvadp01;

                  index path: ;

          owner notification: ;

                 parallelism: 12;

physical client parallelism: Disabled;

     autoselect storage node: Disabled;

               storage nodes: VUSVADP01, nsrserverhost;

       recover storage nodes: VUSVADP01, SUSBCK05;

   save session distribution: max sessions;

                  hard links: Disabled;

             short filenames: Disabled;

                 backup type: ;

              client OS type: ;

                        CPUs: ;

           NetWorker version: ;

              enabler in use: No;

       licensed applications: ;

               licensed PSPs: ;

nsradmin>

Yes, please give it a try

You can't mix the transport modes, so it makes sense to define it only on the proxy.

disregard. as of now it finally kicked off (45 min after teh jobs started).

thank you for your assistance today!

well this is maddening. after reviewing the backup logs, i get this..... at no point is NBD even entered as an OPTION.

Initializing VADP Configuration.

Using VUSVADP01 as the VADP proxy server host for client VUSWEB20.

Application information attribute VADP_HOST for client VUSWEB20 is set to "susvc01.llsa.local".

Application information attribute VADP_DISABLE_FLR for client VUSWEB20 is set to 'No'.

Application information attribute VADP_DISABLE_CBT for client VUSWEB20 is set to 'Yes'.

Application information attribute 'VADP_QUIESCE_SNAPSHOT' for client 'VUSWEB20' is set to default value of "Yes".

Application information attribute VADP_BACKUPROOT for client VUSWEB20 is set to "c:\mnt".

Application information attribute VADP_TRANSPORT_MODE for client VUSWEB20 is set to "hotadd".

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

Application information attribute VADP_MAX_BACKOFF_TIME for client VUSWEB20 is set to "10".

Trying to reset the client resource application information attributes.

Application information attribute VADP_HYPERVISOR for client VUSWEB20 is set to "susvc01.llsa.local".

Application information attribute VADP_DISABLE_CBT for client VUSWEB20 is set to 'Yes'.

90245:nsrvadp_save: An unknown application information attribute is found for client 'VUSWEB20'.

VC\ESX Host Name        : 10.0.20.44

VC\ESX Port             : 443

VC\ESX Username         : Administrator

Mount point             : c:\mnt\VUSWEB20

Flavor                  : fullvm

Transport Mode          : hotadd

Max retry               : 0

Max backoff time        : 10

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

VADP VM-TMP Directory Location: c:\mnt\VUSWEB20\VUSWEB20\VUSWEB20-tmp\letters\1.

Temporary Directory for VM created.

VADP TMP Directory Location: c:\mnt\VUSWEB20\VUSWEB20\tmp.

Temporary Directory for VADP created.

Temporary vmMntLoc Directory for VADP created.

Performing the backup via the Virtual Center.

Application information attribute VADP_VM_NAME for client VUSWEB20 is set to "VUSWEB20".

Trying to connect to the VM using VM name 'VUSWEB20'.

Performing a File level incremental over image level backup.

Creating a quiesced snapshot for 'VUSWEB20'.

10/04/16 09:33:54.970131 Creating snapshot for 'vm-87' ...

10/04/16 09:33:55.016930  Task is 0% complete

10/04/16 09:33:55.032529  Task is 0% complete

10/04/16 09:33:55.048129  Task is 10% complete

10/04/16 09:33:56.046503  Task is 20% complete

10/04/16 09:33:57.044878  Task is 30% complete

10/04/16 09:33:58.043252  Task is 40% complete

10/04/16 09:33:59.057226  Task is 50% complete

10/04/16 09:34:00.055601  Task is 60% complete

10/04/16 09:34:01.053975  Task is 70% complete

10/04/16 09:34:02.052349  Task is 80% complete

10/04/16 09:34:03.066323  Task is 90% complete

10/04/16 09:34:04.064698  Task is 95% complete

10/04/16 09:36:04.072421  Task is 95% complete

10/04/16 09:36:08.611904  Task is 95% complete

10/04/16 09:36:08.845898  Task is -1% complete

The snapshot was created successfully for VM 'VUSWEB20'.

Downloading VM configuration for VUSWEB20.

Configuration downloaded successfully for VM 'VUSWEB20'.

Following are the details of the client VUSWEB20:

VirtualCenter : 10.0.20.44

ESX Server : susvm02.llsa.local

DataCenter Name : LLSA

ConfigDatastore Name : LUN60_VNX

Resourcepool Name : /

Following is the disk information of the client VUSWEB20:

Disk 1 Label : Hard disk 1

Disk 1 Size : 40.0 GB

Disk 1 Datastore name : LUN60_VNX

Disk 2 Label : Hard disk 2

Disk 2 Size : 13.0 GB

Disk 2 Datastore name : LUN60_VNX

Total Number of Disks : 2

Obtained the virtual disks for the VM.

Change block tracking is enabled for VM: VUSWEB20

Successfully mounted the VM as a file system.

Using 'nbd' as the transport mode for Hard disk 1.

Using 'nbd' as the transport mode for Hard disk 2.

Starting NetWorker save operation.

C:\Program Files\Legato\nsr\\bin\save.exe -s susbck05.llsa.local -c VUSWEB20 -w 1478266428 -y 1478266428 -g EVADP10 -LL -a "device interface=data domain" -a "Data Domain interface=IP" -a "DIRECT_ACCESS=No" -b "standard" -m VUSWEB20 -t 1475587371 -o vss:*=off;REQUESTED_LEVEL:level=incr; -l incr -q -W 78 -N VM:VUSWEB20.llsa.local:*IMAGE* -x c:\mnt\VUSWEB20\VUSWEB20\VUSWEB20\__VADP_MOUNT__\500d2f59-b447-5b9d-1522-319ca87346f5\VUSWEB20\letters\

90034:save: The VCB directive is enabled for client 'VUSWEB20' via the VCB proxy server 'VUSVADP01'.

107204:save: 'Backup renamed directories' disabled, renamed directories will not be backed up

VUSWEB20: FULLVM                  level=incr,    159 MB 00:09:45    263 files

completed savetime=1475588287

94694:save: The backup of save set 'FULLVM' succeeded.

Cleaningup VADP mount operation.

10/04/16 09:47:55.398581 Deleting snapshot for 'snapshot-54997' ...

10/04/16 09:47:55.460979  Task is 0% complete

10/04/16 09:48:09.563018  Task is 20% complete

10/04/16 09:48:11.512968  Task is 33% complete

10/04/16 09:48:12.776535  Task is 50% complete

10/04/16 09:48:14.196099  Task is 75% complete

10/04/16 09:48:14.632888  Task is 80% complete

10/04/16 09:48:15.116475  Task is 100% complete

10/04/16 09:48:15.568864  Task is 100% complete

10/04/16 09:48:15.584463  Task is -1% complete

Snapshot for VM VUSWEB20 is deleted.

Temporary directory 'c:\mnt\VUSWEB20' for VADP deleted.

i appreciate the additional pointers. now that i know the actual transport mode IS functioning, i can troubleshoot for throughput problems (items you suggested).

Thank you again!

bingo.

id give another "correct" answer, but its already done .

Test the following on the VADP proxy:

• stop nsrexecd
• delete any folder in ...\nsr\plugins\VDDK\tmp\
• rename ...\nsr\tmp
• start nsrexecd
• run the job again