Maximum data protection, minimum data loss with Dbvisit Standby

[Mike Donovan]

Question:
This question is in relation to defining an approach to maximum data protection, with minimized data loss, during the event of a server failure. We understand that Dbvisit Standby offers a minimum of 60 seconds of data loss. We would like to understand what the configuration steps would be if 60 seconds is our policy of maximum protection.

Answer:
The way that Dbvisit Standby works is that the maximum protection period is determined by how often Dbvisit Standby is scheduled. On Linux and Unix, Dbvisit Standby can be scheduled with cron, and on Windows with Scheduled Tasks. So if Dbvisit Standby is scheduled every 5 minutes, then the maximum protection is 5 minutes. If Dbvisit Standby is scheduled every minute, then the maximum protection is 1 minute (60 seconds).

Please note that the more frequently Dbvisit Standby is scheduled, the more performance impact there will be on the primary system. This is not specific to Dbvisit Standby but to all disaster recovery implementations.