We just went through this ourselves. We're a relatively small organization, and had to update our very-basic plan to a somewhat-more-detailed-but-still-pretty-basic plan.
The first step is to identify key applications and processes. That's why templates aren't super helpful; critical apps and process aren't going to be the same between any two entities. Once you've identified them, you can then work on the rest. What would it take to get those things up and running in the event of a disaster? For instance, in our case payroll and accounts payable were among the critical apps and processes identified. Our plan includes having agreements with other school districts which stipulates that they'll print checks for us on their stock and allow us to reimburse them. The plan also needs to specify precisely who is responsible for what (we prefer to identify by job title rather than name, since the names change). And each of those people needs to have a backup identified. Our plan is pretty simple--just a few pages. But it covers what it needs to. John Hornbuckle MIS Department Taylor County School District www.taylor.k12.fl.us -----Original Message----- From: jesse-r...@wi.rr.com [mailto:jesse-r...@wi.rr.com] Sent: Monday, October 18, 2010 4:48 PM To: NT System Admin Issues Cc: Erik Goldoff Subject: RE: Oh no, not again! I realize that, but I'm moreso after that 'typical' things you might find in a disaster recovery document and the basics to include. I'll check out the links, thanks. J ---- Erik Goldoff <egold...@gmail.com> wrote: > Especially in small arenas, there is no one size fits all plan, all are > unique situations. > > Check out the links on http://www.scpa-us.org and http://www.drii.org > for help > > > Erik Goldoff > IT Consultant > Systems, Networks, & Security > > ' Security is an ongoing process, not a one time event ! ' > > > > -----Original Message----- > From: jesse-r...@wi.rr.com [mailto:jesse-r...@wi.rr.com] > Sent: Monday, October 18, 2010 4:11 PM > To: NT System Admin Issues > Subject: Oh no, not again! > > Seems like this is something brought up every now and then... and I hate > bringing it up againt BUT... > > I have a small client that is interested in putting together a small/basic > disaster recovery plan for their IT department. Anyone know of any fairly > decent boiler templates or examples of this? It's for a 'small' sized > client, not for a major data-center or anything like that. I remember seeing > something a year or two ago regarding this but have since lost the > information, argh. > > Thanks. > J NOTICE: Florida has a broad public records law. Most written communications to or from this entity are public records that will be disclosed to the public and the media upon request. E-mail communications may be subject to public disclosure. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
