Skip to main content
  • EN

Hi all,

looking for real-world guidance on NIC sizing for a Linux Hardened Repository.

Context (VBR 12.x or 13.x ; Linux appliance vs Windows?):

  • Repository: Linux Hardened Repo (XFS, immutability).

  • Repo server NIC options: either 2×10/25GbE or 4×10/25GbE.

  • Backup server/proxies can also be 2×10/25GbE or 4×10/25GbE.

  • Primary storage for the VMware workloads will be either 32G FC (Direct SAN from proxies) or 10/25GbE iSCSI.

  • Single site, LAN backups (no WAN in the data path).

Goal: Max throughput and resilience without adding complexity that doesn’t pay off.

Has anyone measured a meaningful improvement going from 2×25GbE to 4×25GbE on a single Linux repo?

What actually worked (or didn’t) in your environments —  “wish-I-knew” lessons appreciated :-) 

Hi,

 

You’ll be able to leverage the extra networking bandwidth only if you need it.

 

Your repositories will benefit if you’ve got enough proxies keep in them fed with data, which also means enough servers being protected with enough data to justify this. Also, consider the IO performance of your repository. Will your storage be able to saturate 100Gbps/12.5GBps of data? Can your production datastores keep up with such a read rate during backup and a write rate during restore.

 

If you’ve got some form of flash in your hardened repo then it makes a lot more sense to do that.

 

For the record we held a competition years ago to see who could backup a small dataset the fastest and speeds of over 100GBps were achieved so you absolutely can achieve this level of performance with Veeam.

Hi ​@imadam A single repo is a SPOF (Single Pint Of Failure) itself. so you need to garantee additional copy/copies away from the primary repo.

You also need to move away any SOPF on your repository, you need to have redundant componets, such as Power Supply, RAID Controler, RAID level 6 is recommendad, Hot Spare disks.

have a look at my blog posts regarding DAS repository, I started publishing thos articles 2 weeks ago, they will give you an orientantion. 

 

For network, I think you need to understand the storage I/O before, you can benchmark your storage using those two tools. 
http://www.iometer.org/

https://fio.readthedocs.io/en/latest/fio_doc.html#i-o-size


 

Terms & ConditionsAccessibility statement