We have bought a new DAS (HP D3600) with 12 x 4TB SAS HDD. This DAS is connected through a HP SmartArray P421. We will use that storage as backup repository for Veeam. As we do incremental backups and no reversed incrementals, we will create a logical drive in RAID50. Are there any recommendations about other parameters of that volume, such as:.

Recommended Raid Block Size For Mac Download

Strip Size / Full Stripe Size Sectors/Track And in Windows, is it a good idea to format the disk with an allocation unit size of 64K (because it is to store only large files) Regards, Bert. To be honest I don't know what's a full stripe in HP terms. 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. Then, also evaluate the raid configuration, balancing space and performances.

Are you sure to go for raid50 with only 12 disks??? There are no 'SAS' 4TB disks, those are simple SATA disk using a SAS interface. At 7200rpm, raid50 and raid10 will give you really different results. 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:. 120GB for Windows 2008R2. 5,5TB for Veeam Repository So how should it be configured for each logical drive, specially the Repository?

I am reformatting my LaCie 1TB SSD Thunderbolt2 to Striped RAID. The question is what raid block size should I use. The options I have in disk utility is 32 up to 256. I only use this drive for my FCPX libraries including all my media.

In general the optimal configuration would be stripe size equal to the approx. Average I/O size for the main workload on that drive. You can very roughly approximate the I/O size of a given workload by using Activity Monitor, and dividing bytes per sec by IO per sec.

Best Raid Drives For Mac

Apps in this category often use fairly large average I/O sizes. Here is some testing I did on a Pegasus R4 in RAID5. This focused mostly on the impact of stripe size to RAID initialization, but I also did runtime performance tests. SSD has different behavioral characteristics than spinning disks; random I/O is especially faster. This can change the normal advice for stripe size. In general I wouldn't worry about it. What Ben said is good advice; unless you have clear evidence to the contrary, picking the default is a good idea.

I think your LaCie 1TB SSD is 2x 512GB SSDs, so you're talking about a two-drive RAID0 configuration. In theory that's faster but SSD is already so fast I'm not sure how much practical difference that makes, regardless of stripe size. But if in doubt, just take the defaults.