Backup server - Software layout
-
@fuznutz04 said in Backup server - Software layout:
@pete-s said in Backup server - Software layout:
@fuznutz04 You can't expect more if you have mechanical harddrives in RAID 1 or just 1 gigabit NIC.
That's exactly what I have. I suppose I could bond some NICs together, but I'm sure the drives are the limiting factor. At this point, for my backup volume and large backup window, it's fine. But maybe if I get a chance, I'll do some testing with bonding NICs just to see.
I set up Switch Independent teams on all hypervisors always.
You can only get single link max on any given connection, but backup software usually uses multiple threads. SO you can max out multiple links like that.
-
@jaredbusch said in Backup server - Software layout:
I set up Switch Independent teams on all hypervisors always.
Might be the beer talking, but when you say "Switch independent", do you mean team the nics together with the NIC driver/software before presenting it to Hyper-V, or am I way off?
-
@fuznutz04 said in Backup server - Software layout:
@jaredbusch said in Backup server - Software layout:
I set up Switch Independent teams on all hypervisors always.
Might be the beer talking, but when you say "Switch independent", do you mean team the nics together with the NIC driver/software before presenting it to Hyper-V, or am I way off?
Way off.
The terms vary, Microsoft calls it Switch Independent mode.
Linux (Fedora) calls it load balancing.Basically, it is not LACP bonding.
-
@fuznutz04 said in Backup server - Software layout:
@jaredbusch said in Backup server - Software layout:
I set up Switch Independent teams on all hypervisors always.
Might be the beer talking, but when you say "Switch independent", do you mean team the nics together with the NIC driver/software before presenting it to Hyper-V, or am I way off?
I also never use the NIC software.
I only ever use the OS to make teams.
-
@jaredbusch said in Backup server - Software layout:
@fuznutz04 said in Backup server - Software layout:
@jaredbusch said in Backup server - Software layout:
I set up Switch Independent teams on all hypervisors always.
Might be the beer talking, but when you say "Switch independent", do you mean team the nics together with the NIC driver/software before presenting it to Hyper-V, or am I way off?
Way off.
The terms vary, Microsoft calls it Switch Independent mode.
Linux (Fedora) calls it load balancing.Basically, it is not LACP bonding.
Well then, looks like I'll start googling
-
@fuznutz04 said in Backup server - Software layout:
@jaredbusch said in Backup server - Software layout:
@fuznutz04 said in Backup server - Software layout:
@jaredbusch said in Backup server - Software layout:
I set up Switch Independent teams on all hypervisors always.
Might be the beer talking, but when you say "Switch independent", do you mean team the nics together with the NIC driver/software before presenting it to Hyper-V, or am I way off?
Way off.
The terms vary, Microsoft calls it Switch Independent mode.
Linux (Fedora) calls it load balancing.Basically, it is not LACP bonding.
Well then, looks like I'll start googling
Hyper-V example: https://mangolassi.it/topic/10855/dell-r710-nic-teaming-issues/4
-
Screenshot form cockpit on my local KVM test system
-
@jaredbusch said in Backup server - Software layout:
https://mangolassi.it/topic/10855/dell-r710-nic-teaming-issues/4
Well then, looks like I know what I'll be doing tomorrow. Thanks!
-
I use teams, even if there is only one NIC in the team most of the time, because I can add and remove NICs without impacting the higher layers.
-
@jaredbusch said in Backup server - Software layout:
I use teams, even if there is only one NIC in the team most of the time, because I can add and remove NICs without impacting the higher layers.
Good idea. This server I just got has the onboard GB NICs, but also 2 dual port Intel GB NICs as well. I could create a BIG team if I wanted.
