On checking the binary log it was observed that backups were taking much longer to complete because all the VM’s were backing up in NBD mode instead of SAN mode as seen below:
Job Message 2016/03/13 19:01:13 700 Data Plugin NVBABCK01 TaskID 1u VM disk '[test1] vm1.net1.int/vm1.net1.int-000002.vmdk' opened in 'nbd' mode
Job Message 2016/03/13 19:01:30 696 Data Plugin NVBABCK01 TaskID 1u VM disk '[test2] VM2.net2.ad.sys/VM2.net2.ad.sys-000002.vmdk' opened in 'nbd' mode
Job Message 2016/03/13 19:38:37 700 Data Plugin NVBABCK01 TaskID 1u VM disk '[test1] vm1.net1.int/vm1.net1.int_1-000002.vmdk' opened in 'nbd' mode
Enabled VDDK trace in verbose mode by applying KB below:
https://support.quest.com/netvault-backup/kb/81509
Checked the VDDK trace file vixDiskLib-xxxx.log found the following. Looking at this output we see “Cannot use advanced transport modes” , “SSL Exception: error:140000DB:SSL routines:SSL routines:short read” , Open a disk with standard transport mode.
016-03-15T16:21:28.463+01:00 [11468 error 'Default'] Cannot use advanced transport modes for 10.10.00.70/moref=vm-2374/snapshot-4031: Other error encountered: SSL Exception: error:140000DB:SSL routines:SSL routines:short read.
2016-03-15T16:21:28.463+01:00 [11468 info 'Default'] Successfully released all resources.
2016-03-15T16:21:28.463+01:00 [14768 trivia 'ThreadPool'] ThreadPool[idle:4, busy_io:0, busy_long:0] HandleWork(type: 0, fun: class boost::_bi::bind_t<void,class boost::_mfi::mf3<void,class Vmacore::System::ThreadPoolAsio,class boost::shared_ptr<class Vmacore::Exception> const & __ptr64,int,class Vmacore::Functor<void,class Vmacore::Exception * __ptr64,int,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil> const & __ptr64>,class boost::_bi::list4<class boost::_bi::value<class Vmacore::Ref<class Vmacore::System::ThreadPoolAsio> >,class boost::_bi::value<class boost::shared_ptr<class Vmacore::Exception> >,class boost::_bi::value<int>,class boost::_bi::value<class Vmacore::Functor<void,class Vmacore::Exception * __ptr64,int,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil> > > >)
VixDiskLib: Advanced transport modes not available for opening moref=vm-2374.
2016-03-15T16:21:28.463+01:00 [14768 trivia 'ThreadPool'] HandleWork() leaving
VixDiskLib: VixDiskLib_OpenEx: Open a disk.
VixDiskLib: Open a disk with standard transport mode.
We try to use SSL on the Vcenter server and have an error because SSL had been removed from config file.
Check that SSL is enabledas follows:
open vCenter client, select view, select administration, server settings, advanced server settings, scroll down to SSL.Version and make the value all option is available. If SLL option not available for selection it will need to be configured as follows.
To enable SSLv3:
1. Open the vpxd.cfg file:
Windows default location: C:\ProgramData\VMware\VMware VirtualCenter\vpxd.cfg
vCenter Server Appliance default location: /etc/vmware-vpx/vpxd.cfg
2. Create a backup copy of the file.
3. Edit the file to add or remove "<ssloptions>16924672</ssloptions>" to enable or disable SSLv3 respectively:
<vmacore>
<cacheProperties>true</cacheProperties>
<ssl>
<useCompression>true</useCompression>
<sslOptions>16924672</sslOptions>
</ssl>
<threadPool>
<TaskMax>90</TaskMax>
<threadNamePrefix>vpxd</threadNamePrefix>
</threadPool>
</vmacore>
4. Save the file.
5. Restart the vpxd Service.
6. To disable SSLv3, make sure the "sslOptions" is not set in the vpxd.cfg file.
7. check that we now see SSL available in vCenter server Advanced settings.
Note: for making changes to vCenter server settings you should contact VMware.
