ANS4174E Full VM backup of VMware Virtual Machine 'CentOS-test' failed with RC=-1

[xyzegg]

Hi,

We are facing a problem to backup virtual machines. Error message code below.

ANS4174E Full VM backup of VMware Virtual Machine 'CentOS-test' failed with RC=-1 mode=Periodic Full - Full, target node name='VMW_VCENTER6_DC01', data mover node name='VMW_VCENTER6_DM01'


Environment description:

• TSM Server: Storage Management Server for Linux/x86_64 - Version 7, Release 1, Level 3.0
• TSM datamover details (VIRTUAL vStorage Backup server):

OS Name: Microsoft Windows Server 2008 R2 Enterprise
OS Version: 6.1.7600 N/A Build 7600
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Server
OS Build Type: Multiprocessor Free
Registered Owner: Windows User
System Manufacturer: VMware, Inc.
System Model: VMware Virtual Platform
System Type: x64-based PC
** AND VERY IMPORTANT **

• TSM Client Version 7, Release 1, Level 0.0
• Virtual vStorage Backup Server VM previously added to vCenter6
• Not using enablement file to upgrade the Backup-Archive client by adding incremental backups capability. Just need to do a "Periodic Full - Full". It's a POC.
• Virtual vStorage Backup Server resides on an ESXi host system that has access to the datastore that contains the virtual disks of the Virtual Machine that is backed up. (not for sure)
• Virtual vStorage Backup Server in a datastore with a block size larger than or
  equal to the datastores that contains the virtual machine’s to back up
• Setup accordingly to "Tivoli Storage Manager for Virtual Environments Deployment Guide" (redp4991.pdf)

• VMware details:

1 (one) Vcenter;
Version: 6.0.0
Build: 2559268
Ports: HTTP: 80 // HTTPS: 443
VMware vCenter Server 6 Standard (Instances)
SSL settings: vCenter Server requires verified SSL certificates
Thumbprint list in the vCenter Server Settings empty (0 hosts)
​

• dsm.opt (on datamover):

NODENAME VMW_VCENTER6_DM01
TCPSERVERADDRESS 10.95.240.156

VMCHOST vcenter6.xxx.yy.z
VMCUSER xxx\xpto
VMFULLTYPE vstor
VMBACKUPTYPE fullvm
VMMC "MC_VM_M90"

PASSWORDACCESS GENERATE

DOMAIN.VMFULL "VM=CentOS-test;"
VMVSTORTRANSPORT "HOTADD"
TRACEFILE "C:\tsmvmbackup\traceVM.tsm"
TRACEFLAGS VM​

• Some relevant information from traceVM.tsm:

...
vmvddksdk.cpp (1224): VixDiskLib: VixDiskLib_ConnectEx: Establish connection using hotadd.
vmvddksdk.cpp (1224): VixDiskLib: VixDiskLib_Connect: Establish connection.
vmvddksdk.cpp (1224): 2016-03-14T18:40:02.984-03:00 [02208 error 'HttpConnectionPool-000000'] [ConnectComplete] Connect failed to <cs p:0000000005facd00, TCP:vcenter6.xxx.yy.z:443>; cnx: (null), error: class Vmacore::Ssl::SSLException(SSL Exception: error:140000DB:SSL routines:SSL routines:short read)

vmvddksdk.cpp (1224): 2016-03-14T18:40:02.984-03:00 [02208 error 'HttpConnectionPool-000000'] [ConnectComplete] Connect failed to <cs p:0000000005facea0, TCP:vcenter6.xxx.yy.z:443>; cnx: (null), error: class Vmacore::Ssl::SSLException(SSL Exception: error:140000DB:SSL routines:SSL routines:short read)

vmvddksdk.cpp (1224): 2016-03-14T18:40:02.984-03:00 [03740 error 'Default'] Cannot use advanced transport modes for vcenter6.xxx.yy.z/moRef=vm-8403/snapshot-8809: Other error encountered: SSL Exception: error:140000DB:SSL routines:SSL routines:short read.

vmvddksdk.cpp (1224): VixDiskLib: Advanced transport modes not available for opening moRef=vm-8403.
...
vmvddksdk.cpp (1750): vddksdkOpen: Error: not expected transport mode was chosen, rc=-1.
...​

It seems we have a SSL authentication issue, but do we need to establish SSL connection to vCenter to backup VMs using "HotAdd" as VMVSTORTRANSPORT?

Can you suggest VMware documentation to setup SSL certificates?

Peace and thank you in advance,


xyzegg

 

[BaR]

As far as I know the vBS has to reside on the same host as the VM you are attempting to backup. If you are not sure if that's the case, try using: VMVSTORTRANSPORT HOTADD:NBD so in case an HOTADD connection could not be established, and NBD connection will be attempted.

 

[xyzegg]

Sorry, my original post did not mention that: It works with NBD as the Data Transport. And as far as I know BA client does not default to NBD due to a bug.

BACKUP VM error ANS4174E RC=-1
http://www-01.ibm.com/support/docview.wss?uid=swg21675163
"if the VMVSTORTRANSPORT option for data mover is set to only the following advanced transport modes: SAN, HOTADD or NBDSSL, it will fail with the following errors if actual selected transport is NBD."


My client version is affected (7.1.x), but we need to try HotAdd before.

 

[xyzegg]

I'll try to update the client with a fix pack. Version 7.1.4 was shipped with "Virtual Disk Development Kit (VDDK) 6.0.1 released with vSphere 6.0 U1 is a bug-fix update"" according to this page:

Tivoli Storage Manager for Virtual Environments: Data Protection for VMware data mover compatibility guide with VMware's Virtual Disk Development Kit
http://www-01.ibm.com/support/docview.wss?uid=swg21672351&myns=swgtiv&mynp=OCSS8TDQ&mync=R

 

[BaR]

Keep in mind that you have to update your TDP VMware too to the same version as the client installed on the vBS.