VMware {code} Community
Zand
Contributor
Contributor

vSphere and Veritas NetBackup 7.0 integration

Hello Experts,

We're trying to backup VM using NetBackup and "hotadd" transport.

VMs based on ESX4.0 EnterprisePlus Update 1.0.

It seems that snapshot created fine but VM backup host unable to map and mount snapshot volume.

I'm suspecting licensing stuff but not sure... Any ideas on how to fix this????

Any help would be greatly appreciated!!!

VXMS logs from VM backup host below:

03/02/2010 14:45:49.0576 : VixInterface::vdConnect:.\VixInterface.cpp:406 <VFM_ESINFO> : Calling VixDiskLib_ConnectEx()

03/02/2010 14:45:50.0029 : g_vdInterfaceLogger:.\libvix.cpp:1689 <VFM_ESINFO> : VixDiskLib: Advanced transport modes not available for opening moref=vm-158.

03/02/2010 14:45:50.0029 : VixGuest::connectToHost:.\VixGuest.cpp:926 <VFM_ESINFO> : Setting up VMM interface

03/02/2010 14:45:50.0029 : VixGuest::connectToHost:.\VixGuest.cpp:945 <VFM_ESINFO> : ChangeTracking is disabled/unsupported

03/02/2010 14:45:50.0029 : VixGuest::openLeafSnapshotDisks:.\VixGuest.cpp:397 <VFM_ESINFO> : connectToHost() success

03/02/2010 14:45:50.0029 : VixGuest::openLeafSnapshotDisks:.\VixGuest.cpp:413 <VFM_ESINFO> : Calling vdOpen(Disk = test/test.vmdk, Flags = 0x4)

03/02/2010 14:45:50.0029 : VixInterface::vdOpen:.\VixInterface.cpp:141 <VFM_ESINFO> : Calling VixDiskLib_Open()

03/02/2010 14:45:50.0029 : g_vdInterfaceLogger:.\libvix.cpp:1689 <VFM_ESINFO> : TicketResolveHostName: Resolving IP address for hostname sapvcenter.

03/02/2010 14:45:50.0029 : g_vdInterfaceLogger:.\libvix.cpp:1689 <VFM_ESINFO> : TicketResolveHostName: Resolved to 10.154.196.116.

03/02/2010 14:45:50.0045 : g_vdInterfaceLogger:.\libvix.cpp:1689 <VFM_ESINFO> : VixDiskLibVim: TicketLogin

03/02/2010 14:45:51.0435 : g_vdInterfaceLogger:.\libvix.cpp:1693 <VFM_ESWARN> : VixDiskLibVim: Not licensed to use this function.

03/02/2010 14:45:51.0467 : g_vdInterfaceLogger:.\libvix.cpp:1689 <VFM_ESINFO> : VixDiskLibVim: TicketLogout

03/02/2010 14:45:51.0670 : VixInterface::vdOpen:.\VixInterface.cpp:150 <VFM_ESERROR> : VixDiskLib_Open() error. Exited

03/02/2010 14:45:51.0670 : VixGuest::openLeafSnapshotDisks:.\VixGuest.cpp:424 <VFM_ESERROR> : vdOpen() error = 16064. Calling closeLeafSnapshotDisks()

03/02/2010 14:45:51.0670 : VixGuest::openLeafSnapshotDisks:.\VixGuest.cpp:527 <VFM_ESERROR> : Exited with failure

03/02/2010 14:45:51.0670 : VixCoordinator::vixMapObjCtl:.\VixCoordinator.cpp:903 <VFM_ESERROR> : Exited with 23

03/02/2010 14:45:51.0670 : vix_map_objctl:.\libvix.cpp:1145 <VFM_ESERROR> : Error 23

Reply
0 Kudos
16 Replies
admin
Immortal
Immortal

"

03/02/2010 14:45:51.0435 TID 0x00000adc: g_vdInterfaceLogger:.\libvix.cpp:1693 : VixDiskLibVim: Not

licensed to use this function.

"

Seems to be license issue. You are not using the ESXi free version, are you? I may ask you for more information otherwise.

Thanks

-Sudarsan

Reply
0 Kudos
Zand
Contributor
Contributor

Hi Sudarsan,

Thank you for your reply. I've just checked with Customer.. They are using ESXi Enteprise Plus Update 1 using

temporary license key (it should be differrent from Free-version). Attaching screenshot of their licenses inventory.

Any inconsistinsies with backup type we are triying to setup???

Thanks, Zand

Reply
0 Kudos
admin
Immortal
Immortal

Thanks for the message - Can you please post what you see on this page?

https:// with your ESX ip address / dns name.

Thanks

Sudarsan

Zand
Contributor
Contributor

Hi,

I appreciate your help!

This page looks as follows:

Reply
0 Kudos
admin
Immortal
Immortal

Thank you. Can you please also get me the output when you click on licenses link in the page you show? Sorry I did not ask you this earlier,

-Sudarsan

Reply
0 Kudos
Zand
Contributor
Contributor

Hi Sudarsan,

Thank you for your interest. Attaching html page you asking for.

Zand

Reply
0 Kudos
Zand
Contributor
Contributor

Hi,

We have made some progress since my last post:

- allowed communications on port 902 from VM backup host to ESX;

- added permissions (to full admin capabilities) to the NetBackup user which used to connect to vCenter;

- tried new VM (Solaris) backup, - both NBD and HOTADD methods works fine;

- tried VM (Windows) backup, - only NBD works fine, HOTADD failed back to NBD;

- recreated Win-VM from new template, - both NBD and HOTADD methods works fine, but for Solaris-Vm only NBD works fine, HOTADD failed back to NBD

with "advanced trasport unavailable" and "Error 23" in VxMS logs as it was with Win-VM before.

So it's looks like almost working but unstable environment... Still researching..

WBR, Zand

Reply
0 Kudos
oehrli
Contributor
Contributor

I have also had limited success getting the NBU 7.0 integration with the vStorage API to work with hotadd mode. To date, I have only been able to get it to work by connecting directly to the ESX host, and not through vCenter. In addition, it only works if the backup host/VM (since it's hotadd mode) is located on the same ESX host. In a multi-ESX hosts environment (aka vSphere w/ vCenter), I haven't had any success getting hotadd mode to work with NBU 7.0.

Reply
0 Kudos
kgupta
Contributor
Contributor

Hi oehrli ,

HotAdd had a couple of constraint, can you check if your environment has any of these:-

  1. HotAdd transport mode
    can not mount vmdk files greater that 1 TB.

  2. HotAdd also requires
    that the VM being backed up as well as the backup proxy should not have any IDE
    disk in it.

  3. In the backup VM no two
    disks should have the same name (this can occur if those disks reside on
    different data stores).

  4. The host running the
    proxy VM requires access to the datastore of the backed-up
    VMs

  5. HotAdd backups might
    fail if you do not have sufficient space available on the datastore on which
    proxy VM resides.

Thanks,

Reply
0 Kudos
oehrli
Contributor
Contributor

My current environment meets all of these criteria. I can configure NBU to communicate with the ESX host directly or with the vCenter server. As I previously stated, I can backup VM's if I configure NBU to communicate directly with the ESX host. If I try to go through vCenter, the exact same backup will fail.

--Mike O

Reply
0 Kudos
kgupta
Contributor
Contributor

Are you using vCenter 4.0 ? Becuase if you are using earlier versions, then you need to configure VCB-HELPER to get hotadd working.

Thanks,

Reply
0 Kudos
oehrli
Contributor
Contributor

Yes, I am using vCenter 4.0.

Reply
0 Kudos
dgorokhov
Contributor
Contributor

Hello!

Did somebody find the workaround or solution, how to resolve this issue?

We have the same problems.

ESX and vSphere are 4.1, NBU is 7.0.1

Backup host is VM on Windows 2008 R2.

We've opened the case in symantec techsupport, but no success yet. Also I've found another peoples that have this problem

http://www.symantec.com/connect/forums/netbackup-7-and-vmware-backup-windows-2008-x64-guests

Reply
0 Kudos
asshutossh
Contributor
Contributor

@

what's the symantec case id?

Regards,

Ashutosh

Regards, Ashutosh
Reply
0 Kudos
dgorokhov
Contributor
Contributor

Symantec case id is 413-208-526

Reply
0 Kudos
Totopolis
Contributor
Contributor

Have anyone found a solution?

Reply
0 Kudos