ML
    • Register
    • Login
    • Search
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups

    Backup server - Software layout

    IT Discussion
    veeam backup hyper-v best practice
    12
    42
    1936
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JaredBusch
      JaredBusch @AdamF last edited by

      @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.

      AdamF 1 Reply Last reply Reply Quote 1
      • AdamF
        AdamF @JaredBusch last edited by

        @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?

        JaredBusch 2 Replies Last reply Reply Quote 0
        • JaredBusch
          JaredBusch @AdamF last edited by

          @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.

          AdamF 1 Reply Last reply Reply Quote 1
          • JaredBusch
            JaredBusch @AdamF last edited by

            @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.

            1 Reply Last reply Reply Quote 2
            • AdamF
              AdamF @JaredBusch last edited by

              @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

              JaredBusch 1 Reply Last reply Reply Quote 0
              • JaredBusch
                JaredBusch @AdamF last edited by

                @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

                AdamF 1 Reply Last reply Reply Quote 0
                • JaredBusch
                  JaredBusch last edited by

                  Screenshot form cockpit on my local KVM test system
                  0_1534295031592_92fc6ea5-b06b-429d-aac2-bfe2dff6a759-image.png

                  1 Reply Last reply Reply Quote 0
                  • AdamF
                    AdamF @JaredBusch last edited by

                    @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!

                    1 Reply Last reply Reply Quote 0
                    • JaredBusch
                      JaredBusch last edited by

                      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.

                      AdamF 1 Reply Last reply Reply Quote 2
                      • AdamF
                        AdamF @JaredBusch last edited by

                        @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.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post