tsm client 6.1 and vcb

[tsmfreak]

config :

Virtual center virtualized
vcb proxy not virtualized

With the TSM Client 6.1 (and VCB) on the proxy you can make a full consistent backup of a VM , it takes a snaspshot via the VC and saves the VM files that constitutes the full image directly in the TSM Server and this only wtih one TSM client command (great):

backup vm mbsbc220 -vmbackuptype=FULLVM -vmbackdir=d:\HOLDINGTANK


My problem is that the proxy access the VM files via the network and not directly via the SAN. It switches (retry) automatically to option -m ndb

Mount command failed. Retry #1...
Retry mount command using Network Base Disk Access.
Mount virtual machine disk on backup proxy for VM 'mbsbc220'
Executing Operating System command or script:
vcbMounter -h mbsvm049 -u bslm -p **** -a ipaddr:mbsbc220 -r "d:\HOLDINGTANK\fullvm\mbsbc220\BACKUP_CURRENT" -t fullvm -m nbd


any idea ?

 

[tsmfreak]

found the solution : the VMFS LUN was not mapped to the VCB proxy in the SAN Volume Controller (=virtualization layer)

 

[Runamuck]

Can the TSM server and VCB be the same server? Thinking of using VCB. TSM 6.1

 

[tsmfreak]

when the TSM Server is installed on a Windows plattform (and the machine has enough power) I have not seen any restriction ( because VCB is a Windows software).

My environment :

TSM Server 5.5.1 on Linux (native)
VCB on Windows Server (native) with TSM Client 6.1
Virtual Center (virtualized on an ESX Host)

 

[Runamuck]

Doesn't say it can not be done but I wonder what kind of issues I would have.