09-01-2016 11:42 PM
Hello,
Currently we are having a flat IP network configured for our master/media servers but moving forward we need to change this to a multiple VLAN IP networks configuration on a trunk link configuration. May I know whether anyone has implemented this type of configuration before, if yes, how it is done. Our master server is solaris 10 with netbackup 7.7.2, our media server consists of suse 11 SP 4 and Windows 2008 R2 servers. Have anyone implemented multiple VLAN configuration on single trunk NICs in their environment.
Thanks
Chan
09-02-2016 01:45 AM - edited 09-02-2016 01:49 AM
I have used VLAN trunking many times, works perfecty. The technique for this is called 802.1Q VLAN tagging
Found a blog about this:
http://troysunix.blogspot.dk/2010/10/vlan-tagged-interfaces-solaris.html
Hop
09-02-2016 03:13 AM - edited 09-02-2016 05:26 AM
09-02-2016 06:35 AM
09-02-2016 08:10 AM
ok thanks. I will discuss with my network and OS colleagues
09-02-2016 08:13 AM
Hello, Does trunking to the Master/Media servers increase network performance? I'm not sure but if I remember reading some netbackup performance document, it alloctes bandwidth based on the different subnets/VLANs equally. If this is true does that mean having your environment in multiple different VLANs help boost network based backups? Regards, Adnan
09-05-2016 04:34 AM - edited 09-05-2016 04:35 AM
Trunking (configuring multiple IP per NIC) as such does not improve performance, maximum performance is dictated by the underlying NIC.
Bonding however increases network performance because you join multiple NIC to one logical NIC. The loadbalane algorithm is important, from my experience LACP (802.3ad) mode 4 is best.
Never heard of allocating bandwidth per VLAN.
See "Linux bonding driver".
https://en.wikipedia.org/wiki/Link_aggregation
09-13-2016 07:24 AM
Thank you Nicolai,
Absolutely trunking is just allowing different VLANs to allow access to the trunk. It should not really matter however if there's just an access VLAN on the server.
Regarding the b/w distribution, just got the below from "NB planning & Performance Tuning Guide" page no. 109
"When a backup starts, NetBackup reads the bandwidth limit configuration and then determines the appropriate bandwidth value and passes it to the client. As the number of active backups increases or decreases on a subnet, NetBackup dynamically adjusts the bandwidth limiting on that subnet. If additional backups are started, the NetBackup server instructs the other NetBackup clients that run on that subnet to decrease their bandwidth setting. Similarly, bandwidth per client is increased if the number of clients decreases. Changes to the bandwidth value occur on a periodic basis rather than as backups stop and start. This characteristic can reduce the number of bandwidth value changes"
Its not VLANs but subnets (as a VLAN could have more than one subnet, not good practice though). It does state the servers within same subnet would decrease the b/w if more clients within same subnet start backup.
I didnt get any details on how to stop this, as in typical SMB data centers all the servers could be limited to 1 or 2 subnets. And having b/w limiations as such could be not so efficient.
09-26-2016 01:40 AM
I think that only apply when bandwidth throttling has been set in Netbackup. You can trottle by IP segment, so even if you have more than one subnet on one VLAN, you should be home safe anyway.
See :
http://www.symantec.com/docs/TECH30467 (Symantec link, humm)
http://www.veritas.com/docs/000074045
http://www.veritas.com/docs/000084566