Disaster Recovery is the process, policies and procedures of restoring operations critical to the resumption of business, including regaining access to data (records, hardware, software, etc.), communications (incoming, outgoing, toll-free, fax, etc.), workspace, and other business processes after a natural or human-induced disaster. To increase the opportunity for a successful recovery of valuable records, a well-established and thoroughly tested disaster recovery plan must be developed. This task requires the cooperation of a well-organized committee led by an experienced chairperson. [1] A disaster recovery plan (DRP) should also include plans for coping with the unexpected or sudden loss of communications and/or key personnel, although these are not covered in this article, the focus of which is data protection. Disaster recovery planning is part of a larger process known as business continuity planning (BCP). In layman's terms Disaster recovery is a plan in case of a disaster affecting your network/data/infrastructure. An example would be to have a mirrored server in a data center somewhere else in the world. Failover routers and routes that will reroute traffic to that data center instead of the point of failure. The mirror needs to be real time or it will be useless. The stakeholders are the major players in the plan. Such as the IT director should be planning and designing the business rules that run the operation. The network manager and network administrator should work with the database administrator and any other IT roles to devise a plan that will give your network the 5 9's of up time. Stakeholders can also refer to the CEO, President or Board of Directors. Business requirements can obviously change from organization to organization but they usually all include a real time backup/recovery plan. How often to replicate the database as to not lose customer orders. Say your orders are updated on the hour out of a different database. You can safely only replicate after that once an hour. But for companies updating on every record that database needs to be consistently synced up. As for trends BGP and other routing protocols as well as software like replistore and Microsoft data center packages seem to find their way into all DR sites. SQL or Oracle replication and DFS for syncing up file shares. If you need more data - give me some more questions!

Disaster Recovery is the process, policies and procedures of restoring operations critical to the resumption of business, including regaining access to data (records, hardware, software, etc.), communications (incoming, outgoing, toll-free, fax, etc.), workspace, and other business processes after a natural or human-induced disaster. To increase the opportunity for a successful recovery of valuable records, a well-established and thoroughly tested disaster recovery plan must be developed. This task requires the cooperation of a well-organized committee led by an experienced chairperson. [1] A disaster recovery plan (DRP) should also include plans for coping with the unexpected or sudden loss of communications and/or key personnel, although these are not covered in this article, the focus of which is data protection. Disaster recovery planning is part of a larger process known as business continuity planning (BCP). In layman's terms Disaster recovery is a plan in case of a disaster affecting your network/data/infrastructure. An example would be to have a mirrored server in a data center somewhere else in the world. Failover routers and routes that will reroute traffic to that data center instead of the point of failure. The mirror needs to be real time or it will be useless. The stakeholders are the major players in the plan. Such as the IT director should be planning and designing the business rules that run the operation. The network manager and network administrator should work with the database administrator and any other IT roles to devise a plan that will give your network the 5 9's of up time. Stakeholders can also refer to the CEO, President or Board of Directors. Business requirements can obviously change from organization to organization but they usually all include a real time backup/recovery plan. How often to replicate the database as to not lose customer orders. Say your orders are updated on the hour out of a different database. You can safely only replicate after that once an hour. But for companies updating on every record that database needs to be consistently synced up. As for trends BGP and other routing protocols as well as software like replistore and Microsoft data center packages seem to find their way into all DR sites. SQL or Oracle replication and DFS for syncing up file shares. If you need more data - give me some more questions!