Best Veeam Implementation?

[Matt123]

Hello hello!

I have a 3 host Vmware Enviroment with an nearly full 3TB SAN and plan to use Veeam to backup local and remotely.
I have the following suggestion on how I will go about doing this and would like input to 'better' ways that it can be implemented.

To have a new physical server with Veeam installed on it, some budget HP Server with local disks raid protected.
Then I would have a QNAP with raid protected storage sat in a data centre. I could then use the local veeam server to backup over to a WAN share (of some sort?) on our QNAP in the datacenter.

Would i require veeam (at the other end?)

I am looking for the best implementation of our backup/restore process.
I want to keep as much data as possible for the best price.

I also want the data in a local data center so i can go drive pick it up for a fast restoration process.

I look forward to your comments and recommendations if CPU/Memory/Disk will help the backup fast.

[foggy]

Matt, have you heard about the new Backup Copy job type available in the soon-to-be-released Veeam B&R v7? Seems to perfectly address your requirements.

[Matt123]

Would this backup to local repo and then to remote location after, this way saves pulling from the source twice?

Do you have a link to info on this feature?

This was I wouldn't require 'server like' features at my remote location just pure disk space?

[foggy]

Would this backup to local repo and then to remote location after, this way saves pulling from the source twice?

You would have an ordinary backup job to perform backup to the local repository first, then the Backup Copy job will offload the required restore points offsite. Production VMs will be touched only once, during the first local backup.

Do you have a link to info on this feature?

I've provided two of them in my previous post actually.

This was I wouldn't require 'server like' features at my remote location just pure disk space?

Not sure I understand what do you mean here. You will need to have the backup repository server at your remote location.

[yizhar]

To have a new physical server with Veeam installed on it, some budget HP Server with local disks raid protected.

Good.
Make sure you have enough capacity - I recommend at least 5tb, and a fast controller.
For example make sure you have RAID5 controller with BBWC, instead of low end on-board sata.
Disks can be for example 6*2tb SATA.

Then I would have a QNAP with raid protected storage sat in a data centre. I could then use the local veeam server to backup over to a WAN share (of some sort?) on our QNAP in the datacenter.

Not good.
You will need an additional server to act as remote proxy/repository.
A better approach is to have another windows server at remote location.

Would i require veeam (at the other end?)

No, but you will need a Windows server to act as remote proxy and repository.

[f.dapra@ifinet.it]

If you can afford buy a Server as the backup server/repository the two important factor as other have said is having a hardware controller and a sufficient number of disks to handle the throuput.
The majority of the low budget NAS (I mean under 4k €) are not powerful enought to get the max performances, those would struggle with reverse incremental.

We got very good results with IBM x3630 M4 with 3 or 4 TB SATA disks and you can get up to 56 TB in a 2U machine.
Dell and HP have similar solutions.
jmtc