Calculate IOPS for Backup Repository

[BackupDude]

Greetings,

I have begun to research our next great backup repository. We currently are using a Data Domain and its slowly reaching capacity both in terms of storage but the amount of data it can ingest. We have multiple Veeam servers sending data to this single target and trying to wrap my head around a way to calculate the amount of IOPS the new system will require.

Can someone point me in the direction I should be investigating?

[dellock6]

Fabio, I'm about to publish a whitepaper on this exact topic in few days, just wait... I will update this post once it's out.

Luca.

[BackupDude]

My eyeballs are ready!

[dellock6]

As promised, paper is out:
http://www.veeam.com/wp-veeam-backup-re ... mance.html

Really interested in having honest feedback.

[NightBird]

15 Threads (repository with 15 concurrent tasks ?) to max out a FAS2020 with 12 SATA drives in raid DP ? I'm bluffed

I will increase repository concurrent tasks for many customers.
I have a lot of customers with 11 NL-SAS Drives in raid 5 + 1HS or 24x NL-SAS Raid5. (raid controller with 2 or 4GB cache)

Thank you for this WP

[dellock6]

That's why we need tests and NUMBERS to prove our point
Honestly I've never used the default 4 threads in any storage array, and even an OnTap v7 can manage multiple streams pretty well. This is another proof of what me and Tom Sightler are always saying: to improve performances run multiple jobs against the same storage, it can handle them if it's a modern (or modern-ish) one.

PS: remember there is also the windows file level cache in between, another reason I always suggest to use windows/linux datamover and not the smb share.

Luca.

[JayL]

Hello,

I'm looking for a new storage and I would like to know how to calculare the amount of IOPS I need for my backups.
Do you have any formula to calculate that ?

Thanks

[Dima P.]

Hello JayL.

Take a look at the white paper mentioned in this thread as it can help you to better plan your setup. Thanks!