<?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>TapeAlert.org &#187; architecture</title>
	<atom:link href="http://www.tapealert.org/archives/tag/architecture/feed" rel="self" type="application/rss+xml" />
	<link>http://www.tapealert.org</link>
	<description>Tape drive, library, and autochanger monitoring, specifications, and diagnostics</description>
	<lastBuildDate>Sun, 26 Apr 2009 19:43:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>What is the TapeAlert architecture?</title>
		<link>http://www.tapealert.org/archives/73</link>
		<comments>http://www.tapealert.org/archives/73#comments</comments>
		<pubDate>Fri, 16 Jan 2009 05:41:20 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Specifications and Reference Docs]]></category>
		<category><![CDATA[architecture]]></category>

		<guid isPermaLink="false">http://www.tapealert.org/?p=73</guid>
		<description><![CDATA[TapeAlert software, such as SMARTMon-UX polls the tape drive, autochanger, or library via the SCSI, FibreChannel or iSCSI interface via SCSI commands and reads the
error and warning flags defined by the TapeAlert specification from the hardware.  These flags are converted to diagnostic and status messages and made available to the user.
Tape Drive Implementation
Based on the principle of [...]]]></description>
			<content:encoded><![CDATA[<p>TapeAlert software, such as <a title="SANtools SMARTMon-UX Manual" href="http://www.santools.com/smart/unix/manual" target="_blank">SMARTMon-UX</a> polls the tape drive, autochanger, or library via the SCSI, FibreChannel or iSCSI interface via SCSI commands and reads the</p>
<div id="attachment_75" class="wp-caption alignright" style="width: 160px"><a href="http://www.tapealert.org/wp-content/uploads/2009/01/architecture.png"><img class="size-thumbnail wp-image-75" title="TapeAlert architecture block diagram" src="http://www.tapealert.org/wp-content/uploads/2009/01/architecture-150x150.png" alt="Block diagram of TapeAlert process" width="150" height="150" /></a><p class="wp-caption-text">Block diagram of TapeAlert process</p></div>
<p>error and warning flags defined by the<span id="more-73"></span> TapeAlert specification from the hardware.  These flags are converted to diagnostic and status messages and made available to the user.</p>
<p><strong>Tape Drive Implementation</strong><br />
Based on the principle of the tape drive or library performing constant self-diagnosis using its internal device-specific information, and then interpreting this into standard highlevel error flags<br />
• Device firmware constantly checking for problems using internal device information, for example looking for:</p>
<p style="PADDING-LEFT: 30px">Read or Write margin warning<br />
Read or Write failure (hard error)<br />
Hardware failure<br />
Media worn out<br />
Cleaning required<br />
Cleaning tape worn out<br />
Using non-data grade media</p>
<p>• When problem trigger conditions are met, then the appropriate TapeAlert error flag is set in the TapeAlert Log Sense page 0&#215;2e.</p>
<p><strong>TapeAlert Software Implementation</strong><br />
Software reads TapeAlert information via the Log Sense page, and actions any error flags that are set</p>
<p>• Actions are to log the pre-defined TapeAlert error message and notify user through normal error notification methods e.g. display on server console<br />
• The TapeAlert error messages are related to the flag number (see TapeAlert specification) and have been extensively tested with users<br />
• Error messages are clear and understandable, eg:</p>
<p><em><strong>&#8220;The tape drive needs cleaning:<br />
1. If the operation has stopped, eject the tape and clean the drive.<br />
2. If the operation has not stopped, wait for it to finish and then clean the drive&#8221;</strong></em></p>
<p><a href="http://www.tapealert.org/wp-content/uploads/2009/01/architecture.png"></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.tapealert.org/archives/73/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How does TapeAlert work?</title>
		<link>http://www.tapealert.org/archives/56</link>
		<comments>http://www.tapealert.org/archives/56#comments</comments>
		<pubDate>Fri, 16 Jan 2009 02:04:15 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Using TapeAlert and Related Diagnostics]]></category>
		<category><![CDATA[architecture]]></category>
		<category><![CDATA[messages]]></category>
		<category><![CDATA[SCSI]]></category>

		<guid isPermaLink="false">http://www.tapealert.org/?p=56</guid>
		<description><![CDATA[internal TapeAlert firmware constantly monitors the drive hardware and the media, checking for errors and potential difficulties. Any problems identified are]]></description>
			<content:encoded><![CDATA[<blockquote><p><span class="bodytext">TapeAlert compatible tape drives &#8211; such as the DELL PowerVault 110T SDLT drive &#8211; are delivered with TapeAlert features as standard. The internal TapeAlert firmware constantly monitors the drive hardware and the media, checking for errors and potential difficulties. Any problems identified are flagged on a new SCSI log page, where 64 bytes have been reserved for use by TapeAlert.<span id="more-56"></span></span></p>
<p class="bodytext">After a backup has been completed, the TapeAlert-compatible backup application automatically reads the drive&#8217;s TapeAlert SCSI log page to check for any problems. If an error is flagged, the backup software displays a clear warning message on the user&#8217;s monitor screen, and adds the TapeAlert messages to its logs. These messages are standard across all applications that support TapeAlert, and are designed to give clear explanation of the problem and suggested resolution. For example, a user attempting to backup onto a worn-out tape would encounter the message:</p>
<p><span style="font-size: x-small; font-family: Courier New, Courier, mono;">WARNING: The tape cartridge has reached the end of its useful life:</span></p>
<p>1. Copy the data you need to another tape<br />
2. Discard the old tape</p></blockquote>
<p><span style="font-size: x-small; font-family: Courier New;">The full article can be found at: </span><a href="http://support.dell.com/support/edocs/storage/pv110t/ug/diag.htm">http://support.dell.com/support/edocs/storage/pv110t/ug/diag.htm</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.tapealert.org/archives/56/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

