Spanned volume vs Scale-out Repositories

[jlhall1000]

We have recently just purchased Veeam and im looking at the best way to manage our backup storage.

My Veeam backup repository is a virtual Windows 2012 server.

I have a Compellent SAN with 7k disks to store the backups too and im just trying to work out the best way to present the storage to Veeam.

Do i;

• Present a large lun (e.g. 20tb) to the server and setup the backup repository on this.
  Present multiple 2tb luns and create a single spanned volume in Windows.
  Present multiple 2tb luns and use Scale-out backup repositories.

Has anyone seen performance issues with a large LUN with slow disks?

[PTide]

Hi,

That depends:

Present a large lun (e.g. 20tb) to the server and setup the backup repository on this.

How do you aggregate them?

Present multiple 2tb luns and use Scale-out backup repositories.

What license do you have on VBR?

Thanks

[jlhall1000]

Thank you for the response,

The SAN has 42 disks in a Raid 10 with raid tiering.

We have the enterprise plus license so i believe we have the scale out repository capability.

[PTide]

Then I'd go with the first option. Just make sure that you present it to the repository server directly via FC or iSCSI.

Thank you.

[mkretzer]

But you would only have one IO queue. We use striping / spanned volumes alot and it works good...

[Shestakov]

Markus, you may enable multiple write streams in this case.
Although your option looks good for me.

[mkretzer]

Where do you change that?
This still would not change the queues per device

[PTide]

AFAIK there is nothing wrong with a single queue if the OS that the storage is connected to applies an appropriate IO scheduling algorithm. There is a whitepaper that provides some performance tuning recommendations for Linux systems that use Compellent. I believe that there should be a similar tuning guide for Windows systems as well, or at least Dell engineers should be able to provide some recommendations on that matter.

Thanks