cancel
Showing results for 
Search instead for 
Did you mean: 

VMware Backup - EC14

NBU35
Level 6

Hi 

Master server Solaris 10, CLustered, 7.7.3

Media HP UX, 7.7.3

VMWare Backup host - WIndows 2008 R2, 7.7.3, Present in same cluster and DMZ where client is presnet.

Client - WIndows 2008R2 

Transport Mode - NBD

We are running vmware backup, backups starts and starts writing some data and then after some time it fails with EC14.

below are some messages from VXMS and bpbkar logs of the Backup host.

BPBKAR:

9:40:06.761 [3968.3972] <2> tar_base::V_vTarMsgW: INF - Transport Type = nbd
09:40:06.761 [3968.3972] <2> tar_base::V_vTarMsgW: INF - Files System Name to catalog VIRTUAL_FILE
09:40:30.215 [3968.3972] <2> tar_base::V_vTarMsgW: INF - Files System Name to catalog VIRTUAL_FILE
09:40:30.215 [3968.3972] <2> tar_base::V_vTarMsgW: INF - Files System Name to catalog VMFILE0_1502954789
10:01:18.127 [3968.3972] <16> tar_tfi::processException: An Exception of type [SocketWriteException] has occured at: Module: @(#) $Source$ $Revision$ , Function: TransporterRemote::write[2](), Line: 338 Module: @(#) $Source$ $Revision$ , Function: Packer::getBuffer(), Line: 662 Module: tar_tfi::getBuffer, Function: D:/NB/7.7.3/src/cl/clientpc/util/tar_tfi.cpp, Line: 311 Local Address: [::]:0 Remote Address: [::]:0 OS Error: 10053 (An established connection was aborted by the software in your host machine. ) Expected bytes: 16384
10:01:18.127 [3968.3972] <2> tar_base::V_vTarMsgW: FTL - socket write failed
10:01:18.127 [3968.3972] <16> tar_tfi::processException: An Exception of type [SocketWriteException] has occured at: Module: @(#) $Source$ $Revision$ , Function: TransporterRemote::write[2](), Line: 338 Module: @(#) $Source$ $Revision$ , Function: Packer::getBuffer(), Line: 662 Module: tar_tfi::getBuffer, Function: D:/NB/7.7.3/src/cl/clientpc/util/tar_tfi.cpp, Line: 311 Local Address: [::]:0 Remote Address: [::]:0 OS Error: 10053 (An established connection was aborted by the software in your host machine. ) Expected bytes: 16384
10:01:18.127 [3968.3972] <2> tar_base::V_vTarMsgW: FTL - socket write failed
10:01:18.127 [3968.3972] <2> tar_base::V_vTarMsgW: ERR - tar file write error (14)
10:01:37.080 [3968.3972] <8> ~NbuVddkInitializer: Unable to remove temporary file D:\Program Files\Veritas\NetBackup\var\tmp\vixDiskLib_3968_1502958573.ini, errno 0
10:01:37.095 [3968.3972] <4> tar_backup::backup_done_state: INF - number of file directives not found: 0
10:01:37.095 [3968.3972] <4> tar_backup::backup_done_state: INF - number of file directives found: 1
10:01:37.095 [3968.3972] <2> ov_log::V_GlobalLog: INF - Bypass the loading of BEDS
10:01:37.095 [3968.3972] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 14: file write failed
10:01:37.095 [3968.3972] <4> tar_backup::backup_done_state: INF - Not waiting for server status

 

VxMS:

09:11:05.0271 : getIndexFromPath:RvpNtfsFileSystem.cpp:2520 <ERROR> : Bytes transferred = 0
09:11:05.0271 : readRegistry:RvpNtfsFileSystem.cpp:1906 <ERROR> : Index for registry not found
09:11:05.0271 : resolveVolumesFromNtfs:RvpFileSystemMgr.cpp:2678 <ERROR> : Reading mounted devices from registry failed
09:11:05.0271 : RvpNtfsFileSystem:RvpNtfsFileSystem.cpp:103 <INFO> : Volume name: XYZZY:
09:11:05.0271 : vdRead:VixInterface.cpp:554 <TRACE> : Read(58707744, 206848,

 

09:11:08.0333 : getIndexFromPath:RvpNtfsFileSystem.cpp:2520 <ERROR> : Bytes transferred = 0
09:11:08.0333 : readFile:RvpNtfsFileSystem.cpp:1976 <DEBUG> : \Windows\Temp\mountPointList.txt not found
09:11:08.0333 : isPartitionEqual:RvpFileSystemMgr.cpp:2633 <DEBUG> : Partitions not equal
09:11:08.0333 : resolveGuidVolumes:RvpFileSystemMgr.cpp:2352 <DEBUG> : excluding volume guid: Volume{ab04e6d8-5d13-11e1-ab8f-806e6f6e6963}
09:11:08.0333 : resolveGuidVolumes:RvpFileSystemMgr.cpp:2352 <DEBUG> : excluding volume guid: Volume{ab04e6d9-5d13-11e1-ab8f-806e6f6e6963}
09:11:08.0333 : resolveGuidVolumes:RvpFileSystemMgr.cpp:2352 <DEBUG> : excluding volume guid: Volume{ecc72c75-d51c-11e2-b7e2-0050569100e1}

13724, 13782,1556 of backup host are not reachable from Master server, still other backups are running fine.

Please suggest

8 REPLIES 8

eduncan
Level 5
Employee

So it sounds like you are saying that the media server and the backup host are across a firewall?

Do other backups work without a problem?

When you said Client I assume you mean the VM?  If so the location of the VM is not important.  However the location of the Backup Host and the vCenter/ESX are important.  NBD will communicate with both the VC and the ESX host over the network.

It would be better if you can provide the fully VxMS_Provider log, I don't think you capture the actual error.

Based on what you provided it reads like a network issue.

Yes, firewall between media server and backup host, all other backups running fine.

Yes, by client I mean actual VM to be backed up.

unable to attach logs.. file size is 65 MB 

Thiago_Ribeiro
Moderator
Moderator
Partner    VIP    Accredited

Hi,

About vmware problem, TCP ports 443 and 902 are required to access the VMware infrastructure...these ports must be open.

https://www.veritas.com/support/en_US/article.000122717

13724
13782
1556

These port above of backup host are not reachable from Master server, and the backups jobs are working well?

Backup Host ==> Master doesnt work right?
Master Server ==> Backup Host?

 

Master Server ==>Other clients its working

Backup Host ==> Other clients its working? The backups jobs are running?

Regards,

 

Thiago

 

Vcenter and ESX are reachable from backuphost oon port 443 & 902.

Master is not able to connect backup host using any port, however reverse is working fine.

All other backups are running fine, 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please define "All other backups..."

All kinds of snapshot backups requires connectivity between the master and client/backup host.

Can i upload those log somehwere, where u ppl can see it ?

I am not able to upload them here due to certian size constraints.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

In all honesty, most forum members do not have the time to sift through massive log files.
You would be better off logging a Support call with Veritas as the support engineers have the time and the tools to search large logs.

Just my personal opinion......

 

EVen I believe that VMWAre backup host mus have bidirectional connectovity to master on port 13724/13782/1556.

But this is not here for any of VMWARE backup host(vm) in DMZ, still backups of remaining clients are running fine.

Also this VMWARE backup host lies in same DC/cluster where clients are