<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: tape volume usage in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/tape-volume-usage/m-p/4023860#M300421</link>
    <description>Easy. The usage counter is in the first data record on the tape, a header created by fbackup. Just do this:&lt;BR /&gt; &lt;BR /&gt;tar tvf /dev/rmt/0m /etc/copyright&lt;BR /&gt; &lt;BR /&gt;And now fbackup will see them as new tapes. The 100 use limitation sounds like you are not using a config file and that is really slowing you down. Create this config file, something like /etc/fbackup.conf &lt;BR /&gt; &lt;BR /&gt;blocksperrecord 4096&lt;BR /&gt;records 64&lt;BR /&gt;checkpointfreq 4096&lt;BR /&gt;readerprocesses 6&lt;BR /&gt;maxretries 5&lt;BR /&gt;retrylimit 5000000&lt;BR /&gt;maxvoluses 200&lt;BR /&gt;filesperfsm 2000&lt;BR /&gt; &lt;BR /&gt;then run fbackup with the -c option as in:&lt;BR /&gt; &lt;BR /&gt;fbackup -c /etc/fbackup.conf ...&lt;BR /&gt; &lt;BR /&gt;This changes the use count to a maximum of 200, about right for DLT drives. It also runs 6 reader processes to speed up the backup as well as increase the blocksize and filespersm.</description>
    <pubDate>Wed, 20 Jun 2007 17:31:36 GMT</pubDate>
    <dc:creator>Bill Hassell</dc:creator>
    <dc:date>2007-06-20T17:31:36Z</dc:date>
    <item>
      <title>tape volume usage</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tape-volume-usage/m-p/4023859#M300420</link>
      <description>we replaced new DLT tapes when the fbackup said 'volume used more than 100 times', however&lt;BR /&gt;the way the person did it caused the new tapes to retain the 100 times used. Is there any way to write to the tapes to reset the uasge  - we have brand new tapes saying they have been used 100 + times.&lt;BR /&gt;</description>
      <pubDate>Wed, 20 Jun 2007 15:28:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tape-volume-usage/m-p/4023859#M300420</guid>
      <dc:creator>Linda Lux</dc:creator>
      <dc:date>2007-06-20T15:28:01Z</dc:date>
    </item>
    <item>
      <title>Re: tape volume usage</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tape-volume-usage/m-p/4023860#M300421</link>
      <description>Easy. The usage counter is in the first data record on the tape, a header created by fbackup. Just do this:&lt;BR /&gt; &lt;BR /&gt;tar tvf /dev/rmt/0m /etc/copyright&lt;BR /&gt; &lt;BR /&gt;And now fbackup will see them as new tapes. The 100 use limitation sounds like you are not using a config file and that is really slowing you down. Create this config file, something like /etc/fbackup.conf &lt;BR /&gt; &lt;BR /&gt;blocksperrecord 4096&lt;BR /&gt;records 64&lt;BR /&gt;checkpointfreq 4096&lt;BR /&gt;readerprocesses 6&lt;BR /&gt;maxretries 5&lt;BR /&gt;retrylimit 5000000&lt;BR /&gt;maxvoluses 200&lt;BR /&gt;filesperfsm 2000&lt;BR /&gt; &lt;BR /&gt;then run fbackup with the -c option as in:&lt;BR /&gt; &lt;BR /&gt;fbackup -c /etc/fbackup.conf ...&lt;BR /&gt; &lt;BR /&gt;This changes the use count to a maximum of 200, about right for DLT drives. It also runs 6 reader processes to speed up the backup as well as increase the blocksize and filespersm.</description>
      <pubDate>Wed, 20 Jun 2007 17:31:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tape-volume-usage/m-p/4023860#M300421</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2007-06-20T17:31:36Z</dc:date>
    </item>
    <item>
      <title>Re: tape volume usage</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tape-volume-usage/m-p/4023861#M300422</link>
      <description>Thank you I did do a tar but I used a file in my directory - I will re-run with the command.&lt;BR /&gt;As far as the usage - what happened was the operator got the message about the tape usage then instead of replyig to the messages - put in a new tape and responded with yes - the new tape had the 100 times written to it then&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 21 Jun 2007 07:59:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tape-volume-usage/m-p/4023861#M300422</guid>
      <dc:creator>Linda Lux</dc:creator>
      <dc:date>2007-06-21T07:59:18Z</dc:date>
    </item>
    <item>
      <title>Re: tape volume usage</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tape-volume-usage/m-p/4023862#M300423</link>
      <description>My example should have read:&lt;BR /&gt; &lt;BR /&gt;tar cvf /dev/rmt/&lt;SOME_TAPE&gt; &lt;SOME_FILE&gt;&lt;BR /&gt; &lt;BR /&gt;It doesn't matter whether you use /etc/copyright or files in /tmp or whatever. Just overwrite the tape with something other than fbackup.&lt;BR /&gt; &lt;BR /&gt;The example I showed simply lists the contents of your tape if it was recorded with tar. you'll know that the tape was correctly overwritten if this command:&lt;BR /&gt; &lt;BR /&gt;frecover -V - -f /dev/rmt/&lt;SOME_TAPE&gt; &lt;BR /&gt; &lt;BR /&gt;produces an error that the tape is not an fbackup volume.&lt;BR /&gt;&lt;/SOME_TAPE&gt;&lt;/SOME_FILE&gt;&lt;/SOME_TAPE&gt;</description>
      <pubDate>Thu, 21 Jun 2007 08:49:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tape-volume-usage/m-p/4023862#M300423</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2007-06-21T08:49:45Z</dc:date>
    </item>
  </channel>
</rss>

