Setting up a replication configuration is a fairly standard way to enable disaster recovery (DR) for business-critical databases. In such a configuration, changes from a production or primary system are propagated to a standby or secondary system. One of the important technology decisions that organizations make upfront is the choice of the replication architecture.
Posted May 15, 2009
In recent years, disaster recovery has garnered attention from the company boardroom to the Office of the CIO. Despite this fact, many companies have yet to implement an effective DR solution to safeguard their applications and data. This inertia is attributed to two factors - perception of the term "Disaster" ("when the disaster happens, we'll deal with it then") and shortcomings of existing solutions ("we don't have budget for machines to sit by idly").Due to the rarity of catastrophic disasters such as earthquakes, floods and fires, organizations rarely implement comprehensive disaster protection measures. However, there is another set of "technical disasters" that are caused by much more mundane events which regularly lead to significant system outages. These span faulty system components (server, network, storage, and software), data corruptions, backup/recovery of bad data, wrong batch jobs, bad installations/upgrades/patches, operator errors, and power outages, among others.
Posted March 15, 2008