Unfortunatly this is due to they way they have implemented VCB backups with
TSM. I requested for this to be changed when 5.5 was released, but I gues they
still have not looked into it.
They have hard coded the -a ipaddr: option, I asked for them to make the option
user selectable.
The only workaround was to create my own script which uses the vcbmounter util
and only call TSM once I have copied all the guests for a specific host. (ohh
dont get me started on the VM list parameter. not a very good idea when you
have over 2000 guests)
You may be able to overide the -m nbd option though the config.js file in the
VCB install folder.
Regards
Phil
________________________________________
From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] on behalf of David
Rigaudiere [...@rigaudiere.net]
Sent: 23 November 2009 11:32
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] VMWare VCB with BA Client v6.1.2.0 : How to force nbd
transport type with dsmc
Hi *SMers,
we are trying to implement VCB full vm backup with client v6.1.2.
We want call the VM by name, without DNS resolution.
The vcbmounter commands is ok.
vcbMounter -h xx.xx.xx.xx -u USER -p *** -a name:UDA14 -r s:\ -t
fullvm -m nbd
During the DSMC BA VM command, TSM send this command :
vcbMounter -h xx.xx.xx.xx -u USER -p **** -a ipaddr:UDA14 -r
"S:\fullvm\UDA14\BACKUP_CURRENT" -t fullvm
------------------------
> dsmc ba vm
IBM Tivoli Storage Manager
Command Line Backup-Archive Client Interface
Client Version 6, Release 1, Level 2.0
[...]
Backup VM command started. Total number of virtual machines to process: 1
Backup of Virtual Machine 'UDA14'
Mount virtual machine disk on backup proxy for VM 'UDA14'
Executing Operating System command or script:
vcbMounter -h xx.xx.xx.xx -u USER -p **** -a ipaddr:UDA14 -r
"S:\fullvm\UDA14\BACKUP_CURRENT" -t fullvm
[2009-11-23 12:05:14.235 'App' 188 info] Current working directory:
D:\TSM\baclient
[2009-11-23 12:05:14.235 'BaseLibs' 188 info] HOSTINFO: Seeing Intel
CPU, numCoresPerCPU 2 numThreadsPerCore 2.
[2009-11-23 12:05:14.235 'BaseLibs' 188 info] HOSTINFO: numPhysCPUs is
0, bumping to 1.
[2009-11-23 12:05:14.235 'BaseLibs' 188 info] HOSTINFO: numCores is 0,
bumping to 1.
[2009-11-23 12:05:14.235 'BaseLibs' 188 info] HOSTINFO: This machine
has 1 physical CPUS, 1 total cores, and 1 logical CPUs.
[2009-11-23 12:05:16.047 'BaseLibs' 188 info] Using system libcrypto,
version 90709F
[2009-11-23 12:05:16.141 'BaseLibs' 188 warning]
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs
10.210.144.151
[2009-11-23 12:05:16.141 'BaseLibs' 188 warning]
SSLVerifyCertAgainstSystemStore: The remote host certificate has these
problems:
* The host name used for the connection does not match the subject
name on the host certificate
* A certificate in the host's chain is not time valid
* A certificate in the host's chain is based on an untrusted root.
[2009-11-23 12:05:16.141 'BaseLibs' 188 warning] SSLVerifyIsEnabled:
failed to read registry value. Assuming verification is disabled.
LastError = 0
[2009-11-23 12:05:16.141 'BaseLibs' 188 warning]
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled,
so connection will proceed despite the error
[2009-11-23 12:05:18.891 'vcbMounter' 188 error] Error: Could not
resolve IP address for UDA14
Finished command. Return code is: 1
------------------------
Can we, with TSM, specify the -m nbd switch for backup by vmname,
without dns resolution ?
The "dsmc backup vm" command for a VM with DNS resolution is fine.
Is the DSN Resolution mandatory for VCB Full VM Backup with TSM ?
The -m nbd switch seems to be hardcoded in dsmc.exe, but I don't known
if we can activate it.
> findstr ipaddr dsmc.exe
....vcbMounter -h %ws -u %ws -p **** -a ipaddr:%ws -r "%ws" -t file
........vcbMounter -h %ws -u %ws -p %ws -a ipaddr:%ws -r "%ws" -t file
.vcbMounter -h %ws -u %ws -p **** -a ipaddr:%ws -r
"%ws\BACKUP_CURRENT" -t fullvm .......vcbMounter -h %ws -u %ws -p %ws
-a ipaddr:%ws -r "%ws\BACKUP_CURRENT" -t fullvm
........vmStartOffloadMount(): Creating dir %ws, psFileCreateDir rc = %d
> findstr nbd dsmc.exe
.vmStartOffloadMount: RETRY #1 - Network Base Disk Access (non-SAN) -m
nbd..-m nbd......R.e.t.r.y. .m.o.u.n.t. .c.o.m.m.a.n.d. .u.s.i.n.g.
.N.e.t.w.o.r.k. .B.a.s.e. .D.i.s.k. .A.c.c.e.s.s...
Best regards
David Rigaudiere
