The proxy/backup server/datamover/whateverIBMiscallingitnow is not a VM, so hotadd is not an option. Agree that NBD isn't ideal, but the customer has NAS VM storage, so it's either NBD or hotadd.
STEPHEN STACKWICK | Senior Consultant | 301.518.6352 (m) | Stephen.Stackwick < at > icfi.com | icfi.com
ICF INTERNATIONAL | 410 E. Pratt Street Suite 2214, Baltimore, MD 21202 | 410.539.1135 (o)
From: ADSM: Dist Stor Manager [ADSM-L < at > VM.MARIST.EDU] on behalf of Stefan Folkerts [stefan.folkerts < at > GMAIL.COM]
Sent: Friday, June 01, 2012 12:11
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM4VE NBD data path
I haven't but why not multihome the datamover vm and try to let it connect
to the storage & vCenter server that way?
I might be missing something but why would you want to use NBD over hotadd?
On Fri, Jun 1, 2012 at 5:20 PM, Stackwick, Stephen <
Stephen.Stackwick < at > icfi.com> wrote:
I have a customer with a VMware environment using NFS storage. He has a
dedicated private network connecting his ESX hosts to his network storage.
He wondered if it was possible to attach the backup/proxy server to this
private LAN, in order to isolation the backup traffic. Has anyone tried
this? The problem I see is that the proxy wants to talk to vCenter, and
vCenter isn't reachable on the storage interface. It seems if you ditched
the vCenter plugin approach, and manually configured the datamover dsm.opt
files to point to ESX server IP addresses, it might work, right?
STEPHEN STACKWICK | Senior Consultant | 301.518.6352 (m) |
Stephen.Stackwick < at > icfi.com<mailto:sstackwick < at > icfi.com> | icfi.com<
ICF INTERNATIONAL | 410 E. Pratt Street Suite 2214, Baltimore, MD 21202 |