Have Geek Brain

When things go wrong: good contingency planning?

I work for a small firm with little technical skill / knowledge.

One of my colleagues died on a hard drive without any backups and we recently contracted a virus and infected our test server (gumblar.cn) which we may or may not be able to transfer to the client server.

After these two events, management danced around promoting good practices to avoid future events during the week.

Changing the culture of the company to take it more seriously is one of the challenges I'll try to deal with, but my question is ...

What events should you plan?

I believe there are natural disasters, hardware failures, people leaving (bus ratio?).

+1


a source to share


2 answers


Here are some common things:

  • Shared directories on the failover server to be used as a policy for user files and data (with appropriate security). Event = limiting data loss
  • Planned server backups. Event = limiting data loss
  • Firewall proxy server with registration and intrusion detection. Event = data corruption and theft.
  • Enterprise Virus Software deployed to server and clients. Event = virus infection, data theft, systemic damage
  • Automated IT asset tracking software that reports hardware and software changes to servers and clients. Event = data and hardware theft, unauthorized modification
  • Off-site data storage. Event = limiting data loss
  • Fire fighting equipment and automated fire extinguishing mechanisms. Event = Fire
  • An internet filtering proxy such as WebMarshall. Event = protection against infections and risks from "wires".


etc .. etc. You should be able to find much more comprehensive strategies, measures, etc. online.

+1


a source


Consider what equipment and services you are using, and how likely they are to fail or become unavailable for a while. Create a list. Assess how likely each problem is, how much it will cost you, and how much the backup solution costs. Then you decide.



+1


a source






More articles:


All Articles