On Apr 9, 5:42 am, ran...@sanovi.com wrote:

>
> As to why anyone would need this, it simply is a more accurate
> indication of how much the DR database is behind the production
> database.
>

Why not just set up a scheduled cron process that takes a transaction
dump from the production database every N minutes, then immediately
loads it to the backup database?

What's wrong with just doing this every N minutes, regardless of
whether or not it might actually be "necessary" or "much behind"?

This method guarantees that your backup database will always be up-to-
date within N minutes. Select "N" based on whatever you or your
customer is comfortable with.

I tried to be "clever" once by having the transaction dump occur every
15 minutes during working hours. Then the customer fooled me by coming
in weekends for the month-end closing. The system locked up from the
logs filling up. So my "cleverness" cost me some weekend support, that
I don't get paid extra for. Particularly harrowing was that this
customer is in Singapore and I'm not, so somebody has to wake me at
2AM.

Long story short, I now have it dumping and loading every 15 minutes
for 22 hours of every day of the week, excepting an hour on either
side of midnite when it does a full dump. Maybe wears the disks a
little more, but that's their problem.

:-)