Look to your hardware vendor for a solution. To move the data from the primary site to the secondary site, you're talking about replication. Your options are:
Synchronous
Semi-Synchronous
Asynchronous
When we talk about fault tolerant DR options, there are two main areas to consider. The first is RPO, or recovery point objective. This simply state how much data you are willing to lose in the event of a failure. The second is RTO or recovery time option. This represents the time it takes to restore funtionality.
With Synchronous replication, the RPO is zero. With semi-synchronous or asynchronous replication, the RPO is some value larger than zero usually expressed as a time. For example, if you use asynchronous replication sheduled at three hour intervals, the RPO in the event of failure is up to 3 hours depending on exactly when the failure occurred and when the data was last replicated.
To answer your question, asynchronous replication will provide some protection againt database corruption at the cost of an RPO greater than zero. Sychronous replication also provides some degree of protection, depending on the nature of the corruption, with an RPO of zero.
Another approach is to combine snapshots in the mix. In this approach you would snap tha databases every couple of hours, and the log files at a much more frequent interval. Then, replicate the snapshots. This gives you the greater protection from corruption that you get with Asynchronous replication, while reducing the RPO by replicating logs more frequently. On startup of the recovery server, the logs are replayed, so the cost of this approach is a potentially longer RTO.
