Thanks for the post.
The CS500 should be fine for the DDB. CV recommends having the DDB on a Raid0 because its the fast I/O available. But most companies are not comfortable with that so Raid 1+0 is fine. the DDB should have its own spindles with a single lun. This is to prevent splitting the I/O between other partitions and limiting ddb growth. The other important configuration is the MA its self.
Cv recommend having the O/S on a Raid 1 and more importantly the Page file need to have its own Raid 0 spindles. the memory should be 12gb min. for 8 and 24gb min. for 9.
If runing Windows 2008 R2 make sure to have the following MS hotfix
If the CX500 is going to be used for the disk library as well you will want to use seperate interfaces if possible.
the sim tool is part of the SIDB2 executable found in the base directory of the Media Agent.
This tool is a command line tool that will show how well the DDB will scale based on the drive configuration. When running this tool make sure to run it concurrently the same number of time there will be active DDB running during production. this is to simulate real world load. CV does not recommend running more than 4 ddbs per MA especially on the same DDB lun. typically we find that a properly configured MA can run the two Sim tool to completion.
how much data are you looking to dedup? how many storage policies are you configuring with dedup?
let me know if you have any questions.