<?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>Config Helper &#187; backup exec</title>
	<atom:link href="http://www.confighelper.com/tag/backup-exec/feed" rel="self" type="application/rss+xml" />
	<link>http://www.confighelper.com</link>
	<description>Technology Configuration and Support Site</description>
	<lastBuildDate>Thu, 30 Jun 2011 13:32:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>VRTSralus Daemon Stopping on Linux Machine</title>
		<link>http://www.confighelper.com/2010/10/vrtsralus-daemon-stopping-on-linux-machine.html</link>
		<comments>http://www.confighelper.com/2010/10/vrtsralus-daemon-stopping-on-linux-machine.html#comments</comments>
		<pubDate>Tue, 26 Oct 2010 04:13:12 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Backup Exec]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Software Configuration]]></category>
		<category><![CDATA[agent]]></category>
		<category><![CDATA[backup exec]]></category>
		<category><![CDATA[daemon]]></category>
		<category><![CDATA[remote]]></category>
		<category><![CDATA[V-79-57344-3844]]></category>
		<category><![CDATA[vrtsralus]]></category>
		<category><![CDATA[watchdog script]]></category>

		<guid isPermaLink="false">http://www.confighelper.com/?p=151</guid>
		<description><![CDATA[Backup Exec job backing up  a Linux system keeps failing with the error message: V-79-57344-3844 - The media server was unable to connect to the Remote Agent on machine The job also show a 0 byte count. When you check the Backup Exec Remote Agent for Linux on the system you are trying to backup [...]]]></description>
			<content:encoded><![CDATA[<p>Backup Exec job backing up  a Linux system keeps failing with the error message:</p>
<h1>V-79-57344-3844 - The media server was unable to connect to the Remote Agent on machine</h1>
<p>The job also show a 0 byte count. When you check the Backup Exec Remote Agent for Linux on the system you are trying to backup you find that the VRTSralus daemon is stopped. After starting the agent the job will run successfully for a few times, but then the job will fail again with the same error message. Again you find that the VRTSralus daemon is stopped. In order to prevent the agent from stopping you can create a watchdog script which will monitor the beremote process and automatically restart it if it is not running.</p>
<h2>Watchdog Script Used to Monitor VRTSralus Daemon</h2>
<p>#!/bin/bash<br />
#<br />
# watchdog<br />
#<br />
# Run as a cron job to keep an eye on what_to_monitor which should always<br />
# be running. Restart what_to_monitor and send notification as needed.<br />
#<br />
# This needs to be run as root or a user that can start system services.</p>
<p>NAME=beremote<br />
START="/etc/init.d/VRTSralus.init restart"<br />
NOTIFY=name@domain.com<br />
GREP=/bin/grep<br />
PS=/bin/ps<br />
NOP=/bin/true<br />
DATE=/bin/date<br />
MAIL=/bin/mail<br />
RM=/bin/rm</p>
<p>$PS -ef|$GREP -v grep|$GREP $NAME &gt;/dev/null 2&gt;&amp;1<br />
case "$?" in<br />
0)<br />
# It is running in this case so we do nothing.<br />
$NOP<br />
;;<br />
1)<br />
echo "$NAME is NOT RUNNING. Starting $NAME and sending notices."<br />
$START 2&gt;&amp;1 &gt;/dev/null &amp;<br />
NOTICE=/tmp/beremote_watchdog.txt<br />
echo "$NAME was not running and was started on `$DATE`" &gt;&gt; $NOTICE<br />
#   $MAIL -n -s "watchdog notice" $NOTIFY &lt; $NOTICE<br />
#   $RM -f $NOTICE<br />
;;<br />
esac</p>
<p>exit﻿</p>
<p>This script will create a log in the /tmp directory and keep track of each time that the watchdog restarts the VRTSralus daemon. You will need to setup a cron job and schedule it to run at a set interval, such as every 15 minutes to ensure the remote Linux agent gets restarted.</p>
&lt;table cellpadding=&quot;0&quot; cellspacing=&quot;0&quot; border=&quot;0&quot;&gt;&lt;tr&gt;&lt;td&gt;&lt;img src=&quot;http://www.confighelper.com/images/0/&quot; /&gt;&lt;td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;td&gt;&lt;/tr&gt;&lt;/table&gt;
]]></content:encoded>
			<wfw:commentRss>http://www.confighelper.com/2010/10/vrtsralus-daemon-stopping-on-linux-machine.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quantum PX502 Doors Locked via SCSI</title>
		<link>http://www.confighelper.com/2009/06/quantum-px502-doors-locked-via-scsi.html</link>
		<comments>http://www.confighelper.com/2009/06/quantum-px502-doors-locked-via-scsi.html#comments</comments>
		<pubDate>Sat, 20 Jun 2009 22:49:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Backup]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Storage]]></category>
		<category><![CDATA[backup exec]]></category>
		<category><![CDATA[doors locked via scsi]]></category>
		<category><![CDATA[problem 4a]]></category>
		<category><![CDATA[px502]]></category>
		<category><![CDATA[quantum]]></category>
		<category><![CDATA[tape library]]></category>
		<category><![CDATA[unlock]]></category>

		<guid isPermaLink="false">http://www.confighelper.com/?p=32</guid>
		<description><![CDATA[I have a Quantum PX502 tape library. When trying to release the door to access the tape magazine I often get an error that says “Problem type 4A: Doors locked via SCSI”. When this happened in the past I would reboot the tape library and backup server in order to get this error to go [...]]]></description>
			<content:encoded><![CDATA[<p>I have a <a title="Quantum tape library" href="http://www.quantum.com/Products/TapeDrives/DLT/Index.aspx" target="_blank">Quantum PX502 tape library</a>. When trying to release the door to access the tape magazine I often get an error that says “Problem type 4A: Doors locked via SCSI”. When this happened in the past I would reboot the tape library and backup server in order to get this error to go away. I figured there must be an easier way to release the door and after poking around in Backup Exec for a minute I figured it out.</p>
<p>The solution is simple. All you have to do is Unlock the library in Backup Exec.<br />
Here is how you do it:<br />
In Backup Exec, go to the Devices tab.<br />
Expand Robotic Libraries and locate the library.<br />
Right click on the library, for me it was Quantum 1.<br />
Then select Unlock and wait for the job to complete.<br />
Once the Unlock job completes you should be able to release the doors on the magazine.</p>
&lt;table cellpadding=&quot;0&quot; cellspacing=&quot;0&quot; border=&quot;0&quot;&gt;&lt;tr&gt;&lt;td&gt;&lt;img src=&quot;http://www.confighelper.com/images/0/&quot; /&gt;&lt;td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;td&gt;&lt;/tr&gt;&lt;/table&gt;
]]></content:encoded>
			<wfw:commentRss>http://www.confighelper.com/2009/06/quantum-px502-doors-locked-via-scsi.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

