• EN
Solved

How to calculate Storage Area Network (SAN) Storage in a Physical Server + SAN as REPO setup

M
Userlevel 3
  • MM599
  • Comes here often
  • 6 comments

Hi All,

We are designing a new Veeam Backup Solution.

 

  • This will be a hardened solution with Linux OS on REPO Server for immutability
  • Snapshot integration will be setup for Veeam to backup from NetApp Snapshots
  • Solution will consist of virtual VMware proxy servers, 1 physical server as the repository server with RHEL installed, iSCSI connected Storage Area Network (SAN) Storage to provide the Repo storage to this RHEL physical server

We need to understand the Storage Area Network (SAN) Storage requirements such as how much RAM, CPU that SAN should have on the 2 controllers?

 

The Physical RHEL repo server will have 128GB memory, 2 x 18 core CPUs and can see the sizing detail for this in the vse sizer, however have not been able to see sizing around the SAN and the RAM/CPU they should have as we dont want to be in a position where the SAN Controllers are struggling.

 

Thanks, 

icon

Best answer by Link State 1 March 2024, 12:23

View original

6 comments

Link State
Userlevel 7
Badge +8

Hi @MM599 

You can use best practices guide and these web tools.

 

Repository Storage | Veeam Backup & Replication Best Practice Guide

 

VSE FrontEnd (veeam.com)

Veeam backup capacity calculator

 

greetings

 

 

Veeam: VMCA | VMCE | VMXP | Veeam Legend - Microsoft: MCITP | MCP | MCSA | 2008 R2 | 2012R2 | 2016 | MCSE Core Infrastructure | MCSE Cloud Platform - Azure: AZ900 | AZ104 - VMWare: VCP-DCV Vsphere 7.x - Cisco: CCNA (Expired)
M
Userlevel 3

Hi @Link State thanks for those links, familiar with those and looked at them already however dont see any detail about the SAN such as how much RAM and CPU that should have in the controllers for example so we can understand what spec of SAN to order.

The VSE Sizer details the below. The repository component will be the spec for the physical RHEL server in this case, so dont see any component detail for the iSCSI Attached SAN that will provide the storage to this RHEL Server?

  • Backup Server 4 Cores 8 GB RAM
  • Database 2 Cores 4 GB RAM
  • Proxy 11 Cores 20 GB RAM
  • Repository 5 Cores 30 GB RAM
coolsport00
Userlevel 7
Badge +17

Hi @MM599 -

Veeam doesn't give resource requirements for SANs because from a Veeam standpoint it's not that important with regards to transmitting of data. They do tend to have a firmware requirement for Storage Integration though.

Data movement is handled by the Backup Proxy. Data transfer speed from the "Source" is more about the throughout of the iSCSI storage network (i.e. 10Gb vs 40Gb, etc) and the path it takes to the Repository, and disk type (SSD vs SATA).

If I find something on resources though... I'll share it. 

Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
Link State
Userlevel 7
Badge +8

Hi @MM599 

SAN\ISCSI storage requirements are for compatibility and hardware snapshot integration support.

https://helpcenter.veeam.com/docs/backup/storage/storage_system_requirements.html?ver=120

https://www.veeam.com/alliance-partner-integrations-qualifications.html?type%5B%5D=snapshot-integrations

regards

Veeam: VMCA | VMCE | VMXP | Veeam Legend - Microsoft: MCITP | MCP | MCSA | 2008 R2 | 2012R2 | 2016 | MCSE Core Infrastructure | MCSE Cloud Platform - Azure: AZ900 | AZ104 - VMWare: VCP-DCV Vsphere 7.x - Cisco: CCNA (Expired)
M
Userlevel 3

The detail behind this is that the current SAN thats attached to the current backup solution is showing high CPU usage on the SAN Controllers, 88% at peak, so with the CPUs in those controllers at 88%, for the new SAN that will be the Veeam REPO, we are looking to calculate in some way the type of SAN, spec etc so the CPUs in those controllers are sufficient and wont be utilised up to 88% etc

MattM
Userlevel 5
Badge +2

You will need a physical proxy for direct storage access in order to backup from the NetApp storage snapshots. Virtual proxy technically works if your prod SAN is iSCSI based, but it’s not recommended. For FC based prod SAN, it’s unsupported.

Comment


Terms & Conditions