i am just stumbling over the same kind of question, also with HP Array Configuration Utility
dellock6 wrote:To be honest I don't know what's a full stripe in HP terms...
HP Help wrote:The stripe size is the amopunt of date that is stored on each physical drive in the array.The full stripe size is the ammount of data that the controller can read or write simultaneously on all drives in the array...
dellock6 wrote:For stripe size, you should align it to the expected deduplication level you are willing to use:
128k for "wan" (256k original, 128k with compression on)
256k for "lan" (512k original, 256k compressed)
512k for "local" (1024k original, 512k compressed).
Also, you should use the same size for both the storage and the file system, or you can incur in write amplification problems. So, use the same value also for NTFS. On Windows 2008 and later ntfs is automatically aligned to the underlying disk, otherwise you should also check and fix alignment problem, this is usually an uderestimated problem in storage configurations but it can lead to serious performance penalties.
What do you mean with "local"? The Backup Server will have local storage the repository is laying on but the vm to be backed up are running in another server room, connected via 1GBit lan with the backup server.
The Raid will be Raid5 and under that two logical drives:
So how should it be configured for each logical drive, specially the Repository?
- 120GB for Windows 2008R2
- 5,5TB for Veeam Repository