So You Survived the Disaster. Did Your Company? - The Business Continuity Table of Contents (Page 4 of 5 ) This document, once fully put together will be quite thick and it should contain (at a minimum): - The exact procedure on how to fully startup every server on your network. This includes exact click-by-click and word-by-word descriptions of any commands that need to be typed in after the ON button has been hit, and it should have a picture of each server and the location of the ON button labeled.
- The name of your virus software.
- Virus software revision level.
- The phone number to the technical support for your virus software.
- Virus signature update frequency.
- Location of the scripts that obtain the new virus signature file(s) from your vendor. If you do not have scripts to do this, then it should contain an exact click-by-click and word-by-word explanation on how to obtain a new signature file and get it loaded into the virus software.
- A printout of the script that performs the update (if your company uses one).
- Exact click-by-click and word-by-word explanation on how to launch the script.
- Exact click-by-click and word-by-word procedures for performing a manual virus scan.
- Exact procedures for what to do when a virus is found that can be cleaned from a file.
- Exact procedures for what to do when a virus is found that can NOT be cleaned from a file.
- The name of your backup and recovery software.
- The revision level of your backup software.
- The phone number to the technical support for your backup software.
- The storage location of your back up media.
- The rotation schedule for your backup media, where and when you obtain a new clean tape, where to put the tapes that are being swapped out, and where and when the offsite people pickup the tapes.
- The exact procedure to startup your backup software if it is not started upon system launch.
- The exact procedure to perform a full manual backup.
- The exact procedure to restore a file and how to find the appropriate media the file will be on.
- Exact procedures (including passwords and the like) for obtaining backup media from your offsite storage company.
- A detailed description of your security system (e.g. firewalls, proxy servers, security groups, access levels, etc.).
- A listing of the rev levels for each piece of software.
- The phone numbers to technical support for each piece of software.
- Contact phone numbers for each of your security and network admin personnel.
- Contact phone numbers for network security experts (unless you’ve hired a “white hat” hacker, you don’t have one in your company, so you should have the number to a consulting company with an expert) in case you suspect a hacker attack is taking place or you suspect your security has been breached.
- The name, phone number, and address to your reciprocal partner company.
- The full reciprocal agreement.
- An English language summary of what the contract says.
- A detailed procedure to get your reciprocal partner company online with your data.
- Detailed procedures on how to “do business” with all of your data sitting on servers you are not used to working with.
- Detailed procedures on how to input orders, process them, how to run payroll, how to run AR, how to run AP, and anything else you simply must have computer access to run the basics of your business.
- Detailed procedures on how to send your reciprocal partner your data, and an explanation on how your partner gets that data, loads it, and gives you access to it.
- Detailed procedures on how to get your reciprocal partner up and running with the most up to date data possible for the systems being run on their servers.
- Finally, it should contain the dates of when you tested all of this and exactly what was tested. Just to be clear, you should be testing the various processes at least twice a year, the more often, the better.
Next: Putting It Together >>
More Administration Articles
More By Danny Wall |
