Originally Posted by n_i
I guess it depends on what you mean by "continuous availability". There are many ways to skin this cat, including:
- storage replication with OS active-passive clustering;
- DB2 HADR;
- DB2 Q Replication;
- InfoSphere Change Data Capture;
- log shipping.
In the attachment I have outlined the existing set-up.
Machine's 1 and 2 exist. 3 and 4 are what we want.
Is it possible to do 'sync' from machine 1 to 2,3,4 without 'any' data loss whatsoever in the event of machine 1 failure using HADR on DB2 9.7 ?
This is what i mean by continuous availibility:
Continuous availability (CA) is defined as high availability extended to 365 days a year, 24 hours a day. CA combines the characteristics of continuous operations and high availability, to mask or eliminate all planned (scheduled) and unplanned (unscheduled) outages from the end user.