> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
> On Behalf Of Fazil Saiyed
> Sent: Wednesday, October 08, 2008 10:59 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] VCB & Networker
> 
> Hello,
> The opinions are wide ranging, however, if there is high IO ( Which it
> will be) requirement to backup VMIMAGES, VCB needs to be robust
physical
> server, this server should ideally be Storage node for Networker  so
that
> data flowing to the tapes from SN ( VCB Proxy  server) is lan free.
> Among other justifications, consider, why you would use storage node
vs
> going over lan for huge datastores, same is true for VMDK
>  ( VMIMAGE) backups.
> In my mind, vertulized server for VCB is  going in wrong direction.
> HTH
> 
> 
> 

I fully agree on wide-ranging opinions - I also agree the VCB should be
a physical server, setup as a storage node in nw.  But, thinking out
loud - there really is no way to make your VCB backups *completely*
lan-free without making the NW server the VCB node, or the vcb node
visible on the san to ESX luns, correct? (My thinking is that since our
NW server cannot see the datastores in the fabric, it must be going from
the storage node  to nw across the lan, yes?)  Hmm...  not really ideal
indeed now that I think about that... :(  

Lastly, to use a vm as a VCB server, would you have to enable NPIV in
ESX, as I don't see how the VM could see the ESX datastores/luns
otherwise?

Thanks - This is a great thread - So many nice (and not so nice) ways to
skin the same cat!... ahhhh!... ;) 

jamie

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER