Not quite sure what you're asking here? A VLAN basically makes the group of
ports assigned to it a virtual switch of it's own -- the only way for
packets
to get from one network to another is through a router. If you're using
VLANs
on your switch, though, I don't think your servers are on a "non-VLANed"
portion
of the switch, but rather on a default VLAN - and your other servers are on
one 
that your created and assigned (at least as far as the switch is concerned).

So -- what do you expect to gain by having a VLAN that has not route to
other 
subnets under your control - especially if you're hosting your netbackup
servers
on it?

-Charlie
-----Original Message-----
From: Scott Jacobson [mailto:SJACOBSO AT novell DOT com]
Sent: Monday, June 30, 2003 5:57 PM
To: Veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] VLAN Backups Same as Fire Wall Configuration - think
not


Just trying to confirm (has anyone successfully done this?):

If a master/media server is sitting a non VLANed portion of a switch and a
client (on the same switch) is VLANed, backups will not work.

We obviously can configure/create access lists to allow NetBackup to work
across firewalls, however, (and though this may be very network hardware
specific), VLANS and their access configuration setting are very limited and
backup attempts of this type will fail.

I'm thinking only with a layer 4 Foundry Networks type device might this
flexibility be possible.

Thanks,

Scott Jacobson
NetBackup Systems Administration
Data Retention and Storage Management
I. S. & T. Provo Operations
sjacobso AT novell DOT com
Desk Direct:   801-861-7668
Toll Free:        800-453-1267 Ext. 1-7668
Cell:                801-560-6891
Novell, Inc., the leading provider of Net business solutions
www.novell.com