Tip

Worst practices for Windows backup and disaster recovery, Part 2

Part two of this two-part article examines more of the worst practices that will virtually doom any backup and disaster recovery plan. As explained in part one, any one of those practices is bad enough; using

    Requires Free Membership to View

more than one of them in a backup and recovery situation is an almost certain recipe for failure. Unfortunately, these practices exist at far too many companies. Here are five more worst practices that can render a company's backup and recovery plan useless.

  1. No plan for backup power. Failing to plan for backup power in the event of a blackout or any other situation where power fails is a critical lapse. Lacking such a plan -- whether that means having sufficient capacity in uninterruptible power supply (UPS) systems to handle the load short term, or having a backup generator or other solution for longer outages -- incurs the possibility of going without power for an extended period of time.
  2. No alternate facility. Not identifying an alternate site, and not making preparations for relocating to it in the event of a catastrophe, can mean not having a home for a while. Events like Hurricane Katrina demonstrate that it is important to not only have a backup facility in mind, but that you also make sure the backup facility is far enough away so as not to be affected by the same catastrophe.
  3. No plan for communications. Not planning to have multiple methods of communicating with critical personnel is a worst practice for disaster recovery. If your plan calls for sending e-mail to a distribution list and the e-mail server crashes, there must be a Plan B in place. Similarly, if you plan to reach personnel by phone and the phone lines are down, you will need another way to reach them. As the 9/11 terrorist attacks demonstrated, cell phones can be unreliable too.
  4. Not having the required computer and networking devices. Nothing will derail a backup and disaster recovery plan faster than not having the required computer and network equipment. Don't forget to identify standby equipment or another source that can provide or expedite the necessary servers, hard drives or other equipment if you need them.
  5. No dry run. One of the most heinous practices is failing to test the plan. It may all look good on paper, but without a practice drill or dry run to validate each step of the plan, critical issues and contingencies may not get identified until it is too late.


Tony Bradley is a consultant and writer who focuses on network security, antivirus and incident response. As the About.com Guide for Internet/Network Security, he provides security tips, advice, reviews and information. He also contributes frequently to other industry publications; a complete list of his freelance contributions can be found at Essential Computer Security.


More information from SearchWinSystems.com

This was first published in January 2006

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.