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.

Obsolesce

@fuznutz04 said in Backup server - Software layout:

Technical sounding board requested.....

So I have a server that will have 10 TB of usable space on it that can be used as a backup server. This will be a backup target for Veeam to backup a few VMs from a Hyper-V host. My initial 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 the backup server directly (no Hyper-V) and have it be simply a storage target.

Thoughts?

I ended up not going that route.

I installed Windows Server 2016 Standard with GUI on bare-metal becasue I was going to plug in a 32TB MD1000 and plug in a tape drive.

But I didn't. So it's just a little physical box now with some unused internal storage chugging away backups.

I plan on running Disk2VHD and doing what you mentioned. In my case, I'm not using storage or other media attached to physical Veeam backup server.

JaredBusch

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

Obsolesce

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

hobbit666

So i'm going to try Veeam to see how it works. I'll be trying with both ESXi and Hyper-V, but i guess the concept for the backup server will be the same.

My question is how to setup the backup server.

Guess install a hypervisor on the bare metal, like Hyper-V.

Then what?
Scenario 1 - Create a VM with 2 VMDKs.. One VMDK (C: Drive) for Windows 201X on and install Veeam backup and replication, then have a 2nd VMDK (backup drive) to store the backup files?
Scenario 2 - Create a VM with one VMDK for Windows + Veeam B&R. Then create a 2nd VM with either Linux or Windows that will have a single VMDK with a share that VM1 will see to store the backups?

Or just install Windows direct onto the bare metail and split the raid into drive and large backup drive?

jt1001001

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

AdamF

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

JaredBusch

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

hobbit666

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

pmoncho

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

AdamF

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

pmoncho

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

Obsolesce

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.