We are shipping t-logs through a DS3, using some compression routines/software. What's happening is we keep getting a random t-log file restore that causes the standby database to go into Suspect mode. Is there any way for us to reapply the log before and reapply the bad log (or a good copy of the bad t-log)?