Why is SAN Replication is Causing Random Database Corruption?
in relation to your comment, I suspect a Ops related issue here instead of a SQL Server engine issue.  These SAN devices usually work on the block layer and some manage transaction log/data file sync better than others, as well as other areas.  

You can show the ops team that no, SQL Server doesn't randomly corrupt data like this.  You can restore backups to another server, setup mirroring, and all this happens with no corruption.  The minute we do san level replication it happens.  If SQL Server caused corruption like this it wouldn't be around.  SQL Server has almost millions of lines of code dealing with corruption, fixing corruption, and reducing the potential of corruption.  You don't get this issue in any other environment and it only comes up with SAN replication, correct?  

Firmware is often a major cause of these types of issues.  Get your Dell support rep on the line, they will have a lot more info and troubleshooting.  Don't settle for a lazy rep, your enterprise's data and time is on the line.  They have a lot of tools that check to see what is causing this in the background and other tools such as DPAC which might help.  This is not a SQL Server engine issue, we will need the full support of Ops.  

Edit: If your firmware is out of date or mismatched, get a policy from the Ops team that manages the SAN which states that they will keep the firmware across the stack of the machines they manage up to date.  If this SLA doesn't exist, you should make a note of it to your managers because you're exposed to a lot of other issues besides this one.

I'm assuming you're using SAN block level replication.

It could often also be mismatch in settings.  Maybe different block sizes, etc. but the san os should be able to detect those issues usually.