Disaster Recovery Recommendations

By Henry Baltazar  |  Posted 2005-04-25 Print this article Print

Disaster recovery recommendations

Site-level planning

  • Maintain multiple live sites, and split production traffic as evenly as possible

  • Utilize remote sites if possible, especially remote sites where employees already work (sales offices, R&D facilities, etc.), to initiate recovery

  • Keep recovery site updated; manuals, diagrams, software and everything else you use in your production site should also be available at the recovery site

  • Recovery tests should be run a few times a year and must be revised to compensate for new apps and other major changes

    Data center optimization

  • A homogeneous data center is easiest to manage and recover. Eliminate extraneous operating system platforms, servers and storage hardware

  • Run performance tests to find bottlenecks and develop SLAs for business managers

  • Consolidate servers and storage as much as possible

  • Make sure dependent apps (apps that feed data to one another) have a synchronized recovery point. For transaction-intensive environments, mismatched recovery points could lead to data corruption

  • Streamline the backup infrastructure. It is good to have multiple copies of data, but you dont want to have too many redundant copies taking up valuable tape and disk resources

  • Document the configurations and settings for all the apps and hardware in the data center, keeping close tabs on changes made

    Senior Analyst Henry Baltazar can be reached at henry_baltazar@ziffdavis.com.

    Check out eWEEK.coms for the latest news, views and analysis on servers, switches and networking protocols for the enterprise and small businesses.


    Submit a Comment

    Loading Comments...
    Manage your Newsletters: Login   Register My Newsletters

    Rocket Fuel