Help with backup configuration using SOBR

[jadonr]

I am a little confused by how I should configure my backup locations. My server contains a RAID (partioned as drive D) for all the shared/stored files and a drive for the OS. My Scale-Out Backup Repository is comprised of the path "D:\Backups\Veeam" and Backblaze B2 bucket.

I have 3 machines that currently need to be backed up:

Workstation 1 --> SOBR
Workstation 2 --> SOBR
Server --> SOBR

At my server, I would typically backup the entire D drive path. However, since that path includes the path "D:\Backups\Veeam" of my SOBR, would it be best to set this path as an exclusion so I'm not backing this up to Backblaze twice?

Also if I create a new partition on my RAID and format as REFT, will I get that much more compression or performance? I really didn't want to sacrifice a block of space on my drive if possible.

[HannesK]

Hello,
the "normal" design would be to have a dedicated backup server (that can also be a Windows 10). If you really only have three servers and you want to back up externally, then a Veeam Cloud Connect provider might be the better way https://www.veeam.com/service-providers.html

I assume that REFT is a typo that means REFS. Yes, that would help https://www.veeam.com/blog/advanced-ref ... suite.html

You can also exclude a folder by using file based backup and chose the volume and exclude the folder: Example 1 https://www.veeam.com/kb3236. Actually that should happen automatically



Best regards,
Hannes

[jadonr]

Can you explain why a Cloud Connect would be more suitable? If Backblaze B2 is included in my SOBR, wouldn't my backups (including the from the host) be included there and wouldn't I be able to restore from there? I currently have VBR installed on my Hyper-V Host and just read (https://helpcenter.veeam.com/docs/backu ... ml?ver=100) that this is not recommended. I don't really have a better place for it to be installed. Additionally, I only have a single VM on this host and it likely won't be included in the backup. That link explains the reason as being "the on-host backup may result in high CPU usage and network overhead". Can't I simply throttle the CPU usage and network overhead?

[HannesK]

Can you explain why a Cloud Connect would be more suitable?

because you don't need Veeam Backup & Replication (VBR) for that. VBR is built for larger environments. Using that software for 3 machines is overkill for me.

The agents cannot write to S3 directly. So Cloud connect is the alternative. That's why.

I don't really have a better place for it to be installed

see my recommendation above

Can't I simply throttle the CPU usage and network overhead?

you can try everything. It's unsupported by Microsoft anyway. And as you already installed it... well, you can just go for it and probably it will work "good enough"

Personally I would use software in a way the vendor designed it for. For your size, standalone agents seem suitable for me.

[jadonr]

Thanks for the recommendations!