TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: Ideas on Development of Disaster Recovery Procedures
Subject:Re: Ideas on Development of Disaster Recovery Procedures From:"Shane Herring" <herrings -at- bigbutton -dot- com -dot- au> To:"Lyse Tremblay" <tremblay -dot- lyse -at- tremblayprudly -dot- com> Date:Mon, 19 Jun 2006 8:14:49
Hi Lyse.
David and Geoff bring some valuable info. The hardest part is you
coordinating.
To add to the other two comments I think one important aspect has been
missed. Risk/threat analysis. You need to know what the weak points are
and the potential threats (users, power company, it staff). By doing this
you can prioritise and gain a bigger picture. It will get bigger.
Procedures will minimise the risks and threats. Items such as change
control, security policies are an example.
Below is a simplistic view but I hope it will help.
I start from the source and work back. For example.
1. Risk - Data corruption.
Response - Restore database
Action - Instructions to restore database
Policy - maintenance schedule
2. Risk - OS failure
Response - Rebuild OS
Action - Instructions to reinstall OS and restore DB to operating status
Policy - No untested updates. Change logs.
3. Risk - Hardware failure
Response - Replace hardware (HDD, power supply)
Action - Instruction to replace hardware.
Policy - Hot spares.
and it goes on. As I said, a simplistic view but it's an approach that
worked for me in my last job. It helped me identify modules and write to
those modules.
HTHs
Cheers
Shane
--------- Original Message --------
From: Lyse Tremblay <tremblay -dot- lyse -at- tremblayprudly -dot- com>
To: techwr-l -at- lists -dot- techwr-l -dot- com <techwr-l -at- lists -dot- techwr-l -dot- com>
Subject: Ideas on Development of Disaster Recovery Procedures
Date: Fri 06/16/06 08:22 PM
>
>
> Hi all,
>
> I am fairly new as a technical writer. I am responsible for coordinating
> the development and creation of disaster recovery procedures for various
> technological areas for the business continuity project for which I am the
> Project Coordinator.
>
> Basically, I see these as being more actionable steps/procedures that can
> sometimes performed in parallel but most often performed sequentially by
> the various cross-functional responsible SME in each functional area.
>
> For example: database server fails and not only does the server needs to
> be recovered but the databases and data that resided on that server would
> also need to be recovered and synchronized. I see that there would be a
> series of steps performed by each SME that would need to happen in a
> particular sequence. (In a full resilient environment the procedures
> would include procedural steps to failover to another server until the one
> that failed can be recovered. That is the environment we are setting up
> and writing procedures for.) My goal is to ensure standardized formatting
> and content of these procedures. I am researching through this group what
> would be the best way to write and present these in a standardized way?
>
> Any thoughts you may have would be greatly appreciated.
>
> PS. I only have Word, at this time, to work with. Looking at
> FrameMaker
> with DITA. I have a little experience with XML.
>
> Thanks,
> Lyse
>
>
>
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> WebWorks ePublisher Pro for Word features support for every major Help
> format plus PDF, HTML and more. Flexible, precise, and efficient content
> delivery. Try it today!. http://www.webworks.com/techwr-l
>
> Doc-To-Help includes a one-click RoboHelp project converter. It's that
easy. Watch the demo at http://www.DocToHelp.com/TechwrlList
>
> ---
> You are currently subscribed to TECHWR-L as herrings -at- bigbutton -dot- com -dot- au -dot-
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit http://lists.techwr-l.com/mailman/options/techwr-l/herrings%40bigbutton.com.au
>
>
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>
> Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/techwhirl/ for more resources and info.
>
>
>
>
>
-----------------------------------------------------------
Speed up your Internet connection by up to 7X.
>From only $4 per month Make Dial-Up feel like Broadband,
make Broadband fly! No need to change ISP
For full details see http://www.bigbutton.com.au/webspider/
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l