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.
-
@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)
-
@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.
-
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.
-
@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.
-
@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...
-
@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 tJust got the server. Downloading Hyper-V ISO now.
-
Veeam VM moved. Now creating a big VHDX for the data drive.
-
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.
-
@fuznutz04 You can't expect more if you have mechanical harddrives in RAID 1 or just 1 gigabit NIC.
-
@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.
-
@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.
-
@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!
