 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: BRMS and IBM 3494 tape library</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/brms-and-ibm-3494-tape-library/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/brms-and-ibm-3494-tape-library/</link>
	<description></description>
	<lastBuildDate>Sat, 18 May 2013 07:32:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: slack400</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/brms-and-ibm-3494-tape-library/#comment-57758</link>
		<dc:creator>slack400</dc:creator>
		<pubDate>Thu, 13 Nov 2008 21:18:46 +0000</pubDate>
		<guid isPermaLink="false">#comment-57758</guid>
		<description><![CDATA[It&#039;s been years since I&#039;ve worked with Fibre on the AS400 but I think the result you&#039;re getting is expected.

I&#039;ve got a managed LPAR w my D.R. provider and they&#039;ve got to manage their backup schedule fairly closely because they have to logically move the tape drive around for the various AS400&#039;s in our rack. They seem to run into a similar issue.

The limitation may also be with how the tape devices are chained (cabled).

Depending how things are chained it&#039;s going to be Tape Library above the 4 drives, so you&#039;ll have no problem assigning all 4 tape drives to 1 as400.

If you can chain 1 tape library with 1 tape drive to one AS400 then perhaps you can get drives 2 thru 4 to show up on the other systems, but you&#039;ll lose the autoloader functionality. At least with SCSI this would happen.

There&#039;s always VTL.
If you have the DASD allocate virtual tape devices to your system.
You can then run all your backups at the same time and then move the stuff to tape 1 server at a time.]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s been years since I&#8217;ve worked with Fibre on the AS400 but I think the result you&#8217;re getting is expected.</p>
<p>I&#8217;ve got a managed LPAR w my D.R. provider and they&#8217;ve got to manage their backup schedule fairly closely because they have to logically move the tape drive around for the various AS400&#8242;s in our rack. They seem to run into a similar issue.</p>
<p>The limitation may also be with how the tape devices are chained (cabled).</p>
<p>Depending how things are chained it&#8217;s going to be Tape Library above the 4 drives, so you&#8217;ll have no problem assigning all 4 tape drives to 1 as400.</p>
<p>If you can chain 1 tape library with 1 tape drive to one AS400 then perhaps you can get drives 2 thru 4 to show up on the other systems, but you&#8217;ll lose the autoloader functionality. At least with SCSI this would happen.</p>
<p>There&#8217;s always VTL.<br />
If you have the DASD allocate virtual tape devices to your system.<br />
You can then run all your backups at the same time and then move the stuff to tape 1 server at a time.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.035 seconds using memcached
Object Caching 267/273 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-18 07:47:33 -->