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

    Backup server - Software layout

    IT Discussion
    veeam backup hyper-v best practice
    12
    42
    3.4k
    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.
    • AdamFA
      AdamF @hobbit666
      last edited by

      @hobbit666 said in Backup server - Software layout:

      VMDKs.. One VMDK (C: Drive) for Windows 201X on and install Veeam backup and replication, then have a 2nd VMD

      I would go for either scenario 1, or scenario 1 using just 1 large VMDK for the entire thing. However, I too am looking for opinions as well.

      I would not install Windows direct in my case, since I want to install a Hypervisor on the bare metal.

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

        @hobbit666 Scenario 1. It keeps your data in an easily portable vmdk/vhdx that you can reattach anywhere in case of VM guest failure.

        hobbit666H 1 Reply Last reply Reply Quote 5
        • hobbit666H
          hobbit666 @JaredBusch
          last edited by

          @jaredbusch
          That's what i was leaning towards 🙂

          Just need so time now to start the trail, might but it off for a few weeks while i re-configure some sites.

          1 Reply Last reply Reply Quote 0
          • pmonchoP
            pmoncho @jt1001001
            last edited by

            @jt1001001 said in Backup server - Software layout:

            Watching this thread as I just acquired a Dell R510 loaded with 2TB spinning rust drives, perfect for a backup target

            I would watch out if you are planning on using Hyper-V 2016 on older Dell's. My R310 will not run VM's in Hyper-V 2016.

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

              @pmoncho said in Backup server - Software layout:

              @jt1001001 said in Backup server - Software layout:

              Watching this thread as I just acquired a Dell R510 loaded with 2TB spinning rust drives, perfect for a backup target

              I would watch out if you are planning on using Hyper-V 2016 on older Dell's. My R310 will not run VM's in Hyper-V 2016.

              Good point. It all depends on what processor you have. The proc MUST support SLAT (or extended page tables. If it does, then you should be good to go. (at least that's what I found)

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

                @fuznutz04 said in Backup server - Software layout:

                @pmoncho said in Backup server - Software layout:

                @jt1001001 said in Backup server - Software layout:

                Watching this thread as I just acquired a Dell R510 loaded with 2TB spinning rust drives, perfect for a backup target

                I would watch out if you are planning on using Hyper-V 2016 on older Dell's. My R310 will not run VM's in Hyper-V 2016.

                Good point. It all depends on what processor you have. The proc MUST support SLAT (or extended page tables. If it does, then you should be good to go. (at least that's what I found)

                I found the same info.

                1 Reply Last reply Reply Quote 0
                • ObsolesceO
                  Obsolesce
                  last edited by

                  Just an FYI...

                  I kept the 64 TB(raw) DAS physically attached to the server with all the data (rougly 20tb). Veeam is smart enough to have it go there directly via the SAS cable, rather than over the network, which woudl be a daily/weekly nightmare... same with the tape drive, directly attached to the physical server that has the backup it's coming from .

                  I did that to avoid all the data going over the network, which would slow backups and tape.

                  Veeam server is still a separate physical box, Windows server 2016 standard installed on the bare metal, no Hyper-V. As i said earlier, that was due to originally wanting to attach the DAS and tape drive to the backup server, but did not end up doing that.

                  So I would do Scenario 1, as that makes the most sense.

                  1 Reply Last reply Reply Quote 1
                  • J
                    Jimmy9008 @Obsolesce
                    last edited by

                    @obsolesce said in Backup server - Software layout:

                    @jaredbusch said in Backup server - Software layout:

                    @obsolesce said in Backup server - Software layout:

                    @jaredbusch said in Backup server - Software layout:

                    @aaronstuder said in Backup server - Software layout:

                    Also, you could use Hyper-V Replica, or Veeam for Replication.

                    Could, but Hyper-V Replication requires SA.

                    Thought we got to the bottom of that before in a large discussion... replication does NOT require SA; replication requires nothing, only a license to cover the VM and hardware on which you turn on the replica.

                    We did.
                    Hyper-V Replication requires SA. Replication from some other tool does not.

                    No we went over this. Everything SA-related was in regards to the disaster recovery benefit, nothing at all to do with Hyper-V Replication.

                    Correct. You can use Hyper-V Replica without SA.

                    matteo nunziatiM 1 Reply Last reply Reply Quote 0
                    • matteo nunziatiM
                      matteo nunziati @Jimmy9008
                      last edited by

                      @jimmy9008 said in Backup server - Software layout:

                      @obsolesce said in Backup server - Software layout:

                      @jaredbusch said in Backup server - Software layout:

                      @obsolesce said in Backup server - Software layout:

                      @jaredbusch said in Backup server - Software layout:

                      @aaronstuder said in Backup server - Software layout:

                      Also, you could use Hyper-V Replica, or Veeam for Replication.

                      Could, but Hyper-V Replication requires SA.

                      Thought we got to the bottom of that before in a large discussion... replication does NOT require SA; replication requires nothing, only a license to cover the VM and hardware on which you turn on the replica.

                      We did.
                      Hyper-V Replication requires SA. Replication from some other tool does not.

                      No we went over this. Everything SA-related was in regards to the disaster recovery benefit, nothing at all to do with Hyper-V Replication.

                      Correct. You can use Hyper-V Replica without SA.

                      I think they are debating the windows vm replica scenario. You can replicate linux freebsd as you want. I still miss the official docs on replica and SA. I dont know which one is right here...

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

                        @fuznutz04 said in Backup server - Software layout:

                        l plan was to install Hyper-V server on the backup server, and then create a large VM for Veeam. That way, I can utilize the backup server as a backup target, but it could also act as a secondary Hyper-V host in case something goes wrong with the main host.
                        The other option could be to just install something like Fedora, on t

                        Just got the server. Downloading Hyper-V ISO now.

                        1 Reply Last reply Reply Quote 1
                        • AdamFA
                          AdamF
                          last edited by

                          Veeam VM moved. Now creating a big VHDX for the data drive.

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

                            Hmm... Getting a transfer speed of 127 MB/s and a transfer speed of 108 MB/s. This is transferring over the network from HV host 1 to this new backup VM on HV host 2.

                            Anyone with a similar setup? Curious as to what speed others are getting on their backups.

                            1 scottalanmillerS 2 Replies Last reply Reply Quote 0
                            • 1
                              1337 @AdamF
                              last edited by

                              @fuznutz04 You can't expect more if you have mechanical harddrives in RAID 1 or just 1 gigabit NIC.

                              AdamFA 1 Reply Last reply Reply Quote 0
                              • scottalanmillerS
                                scottalanmiller @AdamF
                                last edited by

                                @fuznutz04 said in Backup server - Software layout:

                                Hmm... Getting a transfer speed of 127 MB/s and a transfer speed of 108 MB/s. This is transferring over the network from HV host 1 to this new backup VM on HV host 2.

                                Anyone with a similar setup? Curious as to what speed others are getting on their backups.

                                That sounds like your device limits, as Pete pointed out.

                                1 Reply Last reply Reply Quote 1
                                • AdamFA
                                  AdamF @1337
                                  last edited by

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

                                  JaredBuschJ 1 Reply Last reply Reply Quote 0
                                  • JaredBuschJ
                                    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.

                                    AdamFA 1 Reply Last reply Reply Quote 1
                                    • AdamFA
                                      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?

                                      JaredBuschJ 2 Replies Last reply Reply Quote 0
                                      • JaredBuschJ
                                        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.

                                        AdamFA 1 Reply Last reply Reply Quote 1
                                        • JaredBuschJ
                                          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
                                          • AdamFA
                                            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

                                            JaredBuschJ 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 2 / 3
                                            • First post
                                              Last post