DA performance issues - recommendation
Running EV/CA/DA 9.0.2
Have a single EV SQL server, and a single CA/DA SQL server.
SQL servers are 2008 R2 VMs, 4 CPU with 32GB of RAM. Planning on upping CPUs to 8GB.
We've had some performance issues recently in the environmnent around CA and DA, mainly due to a recent 10-fold increase in DA usage, with massive searches, acceptances, legal holds, etc. We went from 7 million messages searched for in Feb to 100 million messages searched for in Mar, and some of these massive searches were accepted, put on legal hold etc.
DA database size went from 200GB in early Mar, to 500GB in late Mar, now around 385GB. CA database is fairly constant around 68GB.
Question 1 - what reduces DA database size? Deleting cases? Taking legal holds off?
Other than not increasing DA usage 10-fold and being mindful of massive legal holds, etc., I am wondering what to do to improve performance, outside of the standard tech docs such as http://www.symantec.com/business/support/index?page=content&id=TECH63230
With a DA database of 500GB, maintenance is very time consuming with the time needed for SQL dumps, index reorgs, etc.
DA10 SQL best practise guide states:
You may need to roll over customer databases to remain within the available storage capacity. The database storage requirements are high. To reduce storage costs, you may want to roll over the database periodically to a new customer database (that is, create all new cases in a new database), and then archive the old database when it is no longer active. Alternatively, you can move the old customer database to slower storage and disable the associated Discovery Accelerator customer tasks. This would allow the customer database to be brought online quickly.
Question 2 - at what point should database be rolled over? My understanding is that there isn't a real way to "close" or "archive" a DA customer database. The best approach is to stop any activity in it (e.g. scheduled searches) and advise users to use a new database. What does disabling the DA customer task do? Does that make the database inaccessible to end users?
The "Co-locating multiple customer databases" section says it may pay to split DBs between different SQL servers, but doesn't give much guidelines around at what point this should be done.
Question 3 - "Additional customer databases may create an impact at the Discovery Accelerator server and the underlying Enterprise Vault infrastructure, which needs to be considered before implementation" - what sort of impact? Is this if multiple customer databases are created on a single SQL server instead of multiple servers?
Any advice appreciated. Thanks.