Hey all, hoping to get a little insight here.
Our company has been dealing with a super slow Buffalo branded all in one NAS product for backing up our VM's to for a while now. We've finally got a new server in, and I'm tasked with creating a NAS to use for our backups. EPYC 9224, 64GB RAM, BOSS setup, dual 10gig, etc.
We're a relatively small shop compared to big enterprise - we have under 30 VM's total and are currently using about 20TB of storage for our backups. We are 98% a Windows shop.
My original plan was to use the Veeam Linux Hardened Repository ISO released not long ago, and have our repo set up using that. However, our MSP, who we purchased the server from, recommended not to use it, and to use a normal Windows 2022 server w/ ReFS instead.
From all the research I've done, it seems like XFS is the way to go here, but now I'm doubting myself. ReFS does seem like a good enough option, but I want to make sure I'm making the best decision for the company that will allow for quick backup and restore performance. Right now, restores take a very long time. Most of my research leaned towards Linux/XFS.
What are your thoughts?
-
- Lurker
- Posts: 2
- Liked: 1 time
- Joined: Feb 07, 2025 6:12 pm
- Full Name: Tyler Weslow
- Contact:
-
- Influencer
- Posts: 10
- Liked: 12 times
- Joined: Dec 19, 2023 7:02 pm
- Full Name: Phil Brutsche
- Contact:
Re: Building new on-prem repo - Windows Server running ReFS vs. Linux Hardened Repo (XFS)
IMO the Veeam hardened repository is the way to go.
Here are the benefits:
* It's not domain joined. This is a common mistake with most Veeam installs
* It has the relevant DISA STIGs applied as a security baseline
* Immutable backups
A Windows-based repository loses immutable backups, and you need to do your own OS hardening (the Microsoft Security Toolkit baselines are a good starting point, from the small amount of digging I've done there's a lot of overlap with the DISA STIGs)
In the event you do decide to go with the Windows-based repository... for the love of whatever deities you worship, DON'T JOIN IT TO THE DOMAIN. Your IMO Veeam environment shouldn't be domain joined either.
Here are the benefits:
* It's not domain joined. This is a common mistake with most Veeam installs
* It has the relevant DISA STIGs applied as a security baseline
* Immutable backups
A Windows-based repository loses immutable backups, and you need to do your own OS hardening (the Microsoft Security Toolkit baselines are a good starting point, from the small amount of digging I've done there's a lot of overlap with the DISA STIGs)
In the event you do decide to go with the Windows-based repository... for the love of whatever deities you worship, DON'T JOIN IT TO THE DOMAIN. Your IMO Veeam environment shouldn't be domain joined either.
-
- Lurker
- Posts: 2
- Liked: 1 time
- Joined: Feb 07, 2025 6:12 pm
- Full Name: Tyler Weslow
- Contact:
Re: Building new on-prem repo - Windows Server running ReFS vs. Linux Hardened Repo (XFS)
Thanks for the reply mdwophil.
We just deployed the VHR using Veeam's ISO. What an excellent product. Very easy to set up.
Our processing rates are unbelievable now that we got rid of that Buffalo NAS. We are using a PowerEdge R7615 for our NAS.
We just deployed the VHR using Veeam's ISO. What an excellent product. Very easy to set up.
Our processing rates are unbelievable now that we got rid of that Buffalo NAS. We are using a PowerEdge R7615 for our NAS.
-
- Veteran
- Posts: 1255
- Liked: 444 times
- Joined: Dec 17, 2015 7:17 am
- Contact:
Re: Building new on-prem repo - Windows Server running ReFS vs. Linux Hardened Repo (XFS)
And the synthetics will be faster as well. And up until now no strange bugs.
At the moment we are also on the way to be 100 % ReFS free
At the moment we are also on the way to be 100 % ReFS free

Who is online
Users browsing this forum: Baidu [Spider], Google [Bot] and 60 guests