[GRLUG] disaster recovery plan examples

Godwin geektoyz at gmail.com
Wed Mar 12 23:36:18 EDT 2008


Amongst other things, ours mainly lists network/server/infrastructure
configuration (hardware, OSes, topology, etc.) and some licensing
info.  Something we can present to the insurance company for
compensation in case of total loss and/or someone else could rebuild
from if I'm not around...  ;-)

G-

On Wed, Mar 12, 2008 at 12:02 PM, Nathan <ndrier at gmail.com> wrote:
>
> On Wed, Mar 12, 2008 at 10:28 AM, Tim Schmidt <timschmidt at gmail.com> wrote:
>  > On Wed, Mar 12, 2008 at 10:57 AM, MailToNick <mailtonick at gmail.com> wrote:
>  >  > Paul,
>  >  > Our management would object, for security reasons,  to having such a plan
>  >  > posted online.
>  >
>  >  Blech.  Like locks, disaster recovery plans should be strong enough to
>  >  stand up to public scrutiny, and show improvement for it.
>  >
>  >  --tim
>  >
>  >
>  > _______________________________________________
>  >  grlug mailing list
>  >  grlug at grlug.org
>  >  http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
>  >
>
>  NIST has a good outline for building DR plans,  they even include some examples.
>
>  http://csrc.nist.gov/publications/nistpubs/800-34/sp800-34.pdf
>
>  The hard part about finding 'sample' DR plans is that they include
>  very sensitive information,  and they are usually very specific to a
>  individual businesses needs.  That said,  a good DR plan is a very,
>  very important thing to have and can make all the difference when you
>  need it.
>
>  Nate
>
>
> _______________________________________________
>  grlug mailing list
>  grlug at grlug.org
>  http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
>



-- 

Ubber::Geek
http://grlug.org/


More information about the grlug mailing list