Get your MSMQ also on local disk. I believe SAN is not supported/too slow
DA/CA not supported on VM. Will work, but Symantec recommends these running on physical machines.
You sql is more than capable of handling ev.
1 - you will have to change sql-server that ev approaches. You could (but test!!!) see if you can use an alias. We use this in our environment, as we do not have the default port used by SQL. You can use on the DR-EV-server :
start, run, cliconfg
tab alias.
give OLD sql server as aliasname, and point to the new server as where it should go. Might work!!! again, test!
2 - 300GB for index is more than sufficient.
I assume (as you use WORM) you will not expire from journal. I'd personally go for smaller cifs luns, and use ev-partitions to keep the data manageable. example. 2tb a year is approx 170 GB a month. make partitions of 200GB, and configure partition roll-over using diskspace as value.
This means if you need to backup worms, once a partition has rolled over, it won't change anymore (assuming you do not expire!), and youneed not make a frequent backup of that partition (no worms expert though)
3 - use cliconfg as easiest workaround. There is a document (http://seer.entsupport.symantec.com/docs/340611.htm) that describes moving databases to other sql server.
4 - DA/CA (no experience in CA) DA searches can produce massive results. Probably best having a 500GB disk for results.
5 - SQL-mirroring not sure.
good luck.
Regards. Gertjan