<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>TheSysAdminLog &#187; disaster recovery</title>
	<atom:link href="http://thesysadminlog.com/tag/disaster-recovery/feed/" rel="self" type="application/rss+xml" />
	<link>http://thesysadminlog.com</link>
	<description></description>
	<lastBuildDate>Wed, 10 Feb 2010 04:14:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Don&#8217;t Forget To Document</title>
		<link>http://thesysadminlog.com/uncategorized/dont-forget-to-document/</link>
		<comments>http://thesysadminlog.com/uncategorized/dont-forget-to-document/#comments</comments>
		<pubDate>Sun, 18 Oct 2009 21:20:42 +0000</pubDate>
		<dc:creator>Charles Pearson</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[disaster recovery]]></category>
		<category><![CDATA[documentation]]></category>

		<guid isPermaLink="false">http://thesysadminlog.com/?p=28</guid>
		<description><![CDATA[Greetings. I would like to make my debut to TheSysAdminLog by discussing a fundamental necessity of any IT department. While not as glamorous as virtualization, disaster recovery, or Windows/Linux debates, this concept is equally as important to those of us who must support a large number of systems on a daily basis&#8230;
Documentation.
While most of us [...]]]></description>
			<content:encoded><![CDATA[<p>Greetings. I would like to make my debut to TheSysAdminLog by discussing a fundamental necessity of any IT department. While not as glamorous as virtualization, disaster recovery, or Windows/Linux debates, this concept is equally as important to those of us who must support a large number of systems on a daily basis&#8230;</p>
<p>Documentation.</p>
<p>While most of us acknowledge the importance of documentation, we all hate doing it. It&#8217;s a cumbersome and inconvenient chore. Why spend time diagramming, taking screenshots, and writing intricate details about the setup of a particular system, when we could be lab-testing the features of a new upgrade or stringing CAT5 cable around the office of a vacationing co-worker? (guilty)</p>
<p>However, documentation can be a life-saver in a number of situations. Firstly, your co-workers will one day appreciate it. I am a member of a team of about a half dozen people. While each of us hold an over-arching knowledge of all the systems we support, we also each have our own areas of specialty. Documentation can be a lifeline for your co-workers in the event that you are unavailable. It is bad enough being called in the middle of the night because of a critical system crash. It&#8217;s even worse being unable to reach the person who set up the system, then being left to feel your way through the dark to get the system back online.</p>
<p>Also, your own documentation can provide a much-needed help to yourself. Whether it be short-term memory loss, or simply the span of a couple of years since the initial setup, we may often forget the intricate details of system. The only problem with a stable system is that we deal with them so little that we tend to forget exactly how they work. In the midst of a crisis, we should not be taking the time to re-learn or re-familiarize ourselves with a particular setup. It&#8217;s game time! Open up that PDF and get to work!</p>
<p>Next, keep your successors in mind. This may be the weakest motivation for writing documentation, since day to day system administration at a former employer no longer seems important. However, once you leave your company, someone else needs to take care of your responsibilities. If you leave behind a flaming pile of chaos, this won&#8217;t reflect well on you. If nothing else, summon some compassion and empathy for your IT descendants. They&#8217;re people too!</p>
<p>Undoubtedly, many system admins avoid documenting in an attempt to ensure job security for themselves. However, what does it say about one&#8217;s confidence in their job performance when they hold their knowledge hostage to keep their job? It&#8217;s also important to realize that securing a current position in this manner could also secure a lack of any promotion in the future.</p>
<p>So, save yourself and your co-workers a bit of headache, and document your work. If you don&#8217;t, then please be sure to look both ways before crossing the street. Your fellow employees will appreciate it.</p>
]]></content:encoded>
			<wfw:commentRss>http://thesysadminlog.com/uncategorized/dont-forget-to-document/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

