Paul, <br>Our management would object, for security reasons, to having such a plan posted online. <br>I'll try to show you something with some information scrubbed out. Not sure if I can get it by tomorrow though. Might have to wait until the next meeting :(<br>
<br>Nick.<br><br><div class="gmail_quote">On Tue, Mar 11, 2008 at 3:52 PM, Paul Kortman <<a href="mailto:paulk@teamddm.com">paulk@teamddm.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi All,<br>
<br>
I need to develop a disaster recovery plan (document). As a SysAdmin I<br>
know what I would do in a disaster depending on what the disaster<br>
is/was. But I'm struggling getting what I know in my head out on paper.<br>
<br>
I have searched for examples or templates online and have found a few,<br>
but none really apply, they either are too specific (focus on one<br>
proprietary technology and how to recover it) or too general saying<br>
things like "a disaster recovery plan needs to have statements about<br>
purchasing replacement equipment." Duh. I could have told you this.<br>
<br>
I don't have the time or the money to put draft 0 in front of a<br>
lawyer... instead I'm trying to draft at least version one and two<br>
before it goes to the lawyer for verification and tightening.<br>
<br>
Do you in your various places of employment(s) have Disaster Recovery<br>
Plans, something that covers a few servers (12+-) and premises etc. ?<br>
Would you be willing to post it here for us all to use as examples or<br>
could you send me a copy off list?<br>
<br>
I appreciate the knowledge gained from being apart of this local community.<br>
<br>
-Paul<br>
_______________________________________________<br>
grlug mailing list<br>
<a href="mailto:grlug@grlug.org">grlug@grlug.org</a><br>
<a href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug" target="_blank">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a><br>
</blockquote></div><br>