Here is my situation.
We run a very mission critical application that uses DB2 7.2 for the data
repository. The database is hosed at a data center in Los Angeles, Ca.
Our main office is in Portland, Oregon.
For disaster recovery purposes, we have been conducting an offline backup of
the database each night, and then sending the backup file and the log files
to our Portland office over a T1 connection. We have a DR machine in
Portland that is identical to the production machine in LA. In the event of
a problem, our plan was to restore the back up and log files to the Portland
machine and then redirect all users to that database.
First Issue: Because of the increasing database size, we have reached the
point where the overnight time window is not enough to complete the backup
and file transfer process before the start of business the next day.
Second Issue: Since this is a mission critical application, we have been
instructed that in the event of a problem, the application can only be
unavailable for 1 hour. RTO = 1 hr. We also cannot stand to loose more than
1 hours worth of data. RPO = 1 hr. Therefore, our old plan, which could
cause a data loss of 24 hours, is no longer good enough.
I am toying with the notion of replicating the database in LA to the DR
machine in Portland over the T1 link. Is this possible? Can it be done?
Would it accomplish our objectives?
Given this situation, what is the best way to accomplish our DR goals? (RTO
= 1 hr. and RPO = 1 hr.)
Any help with this is greatly appreciated.
Thanks in advance,
John