is4profit small business free small business information and advice
Small Business Ad
Home Business Advice IT & Telecoms IT Disaster Prevention
Wednesday, 07 January 2009
IT Disaster Prevention -
Contents
IT Disaster Prevention
Assessing Risks
Sensible Purchasing
Setting Up Your System
Maintenance
Procedures
Backing Up
Planning for the Worst

IT Disaster Prevention

2. Sensible Purchasing

Small Business Ad

2.1 Look for reliability and simplicity when buying computer hardware and software.

  • Unless you have complex IT needs, use off-the-shelf products with a proven track record. Getting support will be easier than with a bespoke package.
  • Get recommendations from contacts with similar needs.
  • Tell your supplier how you intend to use software, and state what other software packages your system is running. Different packages may not work well together.

2.2 Purchase the support you need. Depending on your in-house resources, this may include:

  • Installation, configuration and any customisation needed (see 3).
  • Maintenance (see 4). If you have a network, you will probably need on-site support for your servers and network equipment.
  • Training (see 5.1).

2.3 Check what guarantees you have.

  • Find out how quickly equipment will be repaired or replaced if it goes wrong (see 7.4).

Safe System Upgrades

When you make changes to your system, there is a higher risk of disaster. Following a safe procedure is essential.

Check the upgrade is really necessary.

  • The benefits offered by new versions of software packages do not always justify the inconvenience of upgrading.

Back up the system before you start.

Take steps to minimise problems.

  • Make sure the upgrade is compatible with existing software and hardware.
  • Wait a few months after new software is released before buying it. Problems are more likely to have been ironed out.
  • Upgrade systems during an inactive period to reduce disruption, for example overnight or at a weekend. But bear in mind support may not be available at these times if things go wrong.

Be particularly careful with complex changes or highly sensitive systems.

  • Maintain the old system while the new one is 'run in'.
  • Initially install software or equipment on an isolated part of the system only.
  • Run tests to see what problems occur.
Use existing, rather than new, data to make tests as authentic as possible.

Get help if an upgrade does not work.

  • Call the manufacturer's help desk, or visit its support website.
  • Discussion groups often provide links to useful sources of information.
  • If these steps do not solve the problem, get help from a local IT specialist.
BHP Infosolutions

 
< Prev   Next >