<?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: fbackup script question in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-script-question/m-p/4220010#M327355</link>
    <description>The default values have not changed since fbackup was first written more than 15 years ago. At that time, reel-to-reel tape drives and cartridge tapes were the standard and there was no such thing as a DDS or DLT tape drive. Reel drives had very primitive electronics and recording technology with limited record sizes and very low throughput. This is due in part to the start-stop nature of the old drives. &lt;BR /&gt; &lt;BR /&gt;Today's tape drives are very fast and require a constant stream of data to avoid resync cycles. Modern tape drives cannot stop and start instantly but instead are designed to run continuously. If the data is delayed due to competing activity on the disks, the drive stops, backs up and once more data arrives, takes a running start to resync and continue -- a very long cycle with zero throughput.&lt;BR /&gt; &lt;BR /&gt;These values are the values needed for DDS, DLT, LTO and any modern tape drive.</description>
    <pubDate>Sat, 21 Jun 2008 13:17:15 GMT</pubDate>
    <dc:creator>Bill Hassell</dc:creator>
    <dc:date>2008-06-21T13:17:15Z</dc:date>
    <item>
      <title>fbackup script question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-script-question/m-p/4220005#M327350</link>
      <description>&lt;!--!*#--&gt;I recently started running out of disk space and need to change my oracle cold backup. I had been copying all the relevant files to disk and backuping them up to tape. Now that I am low on disk space I am trying to back them up in place, to tape while the database is down.   &lt;BR /&gt;After the database has been shutdown, the fbackup command runs / executes and immediately (before the backup to tape is complete), then the db starts and a backup of my online database is put to tape.&lt;BR /&gt;&lt;BR /&gt;Anyone have any idea how I can get the database start command to wait for fbackup to finish..  I tried "if" fbackup without sucess.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance for any scripting techniques / idea to accomplish this.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 21 Jun 2008 00:09:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-script-question/m-p/4220005#M327350</guid>
      <dc:creator>Michael Treacy</dc:creator>
      <dc:date>2008-06-21T00:09:26Z</dc:date>
    </item>
    <item>
      <title>Re: fbackup script question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-script-question/m-p/4220006#M327351</link>
      <description>&amp;gt; Anyone have any idea how I can get the database start command to wait for fbackup to finish..  I tried "if" fbackup without sucess.&lt;BR /&gt; &lt;BR /&gt;Not sure what you have tried. In simple code:&lt;BR /&gt; &lt;BR /&gt;mydbscript shutdown&lt;BR /&gt;fbackup ...&lt;BR /&gt;mydbscript startup&lt;BR /&gt; &lt;BR /&gt;fbackup will not return until it is finished, so mydbscript startup will run at the right time. Now the above will work correctly so I suspect that there is something different that you are doing.&lt;BR /&gt; &lt;BR /&gt;&amp;gt; fbackup command runs / executes and immediately (before the backup to tape is complete)&lt;BR /&gt; &lt;BR /&gt;This is very abnormal -- unless you run fbackup ... &amp;amp; where the &amp;amp; character runs fbackup in the background (never recommended). When you put a process into the background, the scheduling of fbackup returns immediately while fbackup continues to run. While you could write some monitoring code, why bother? Just run fbackup normally and run your &lt;BR /&gt; &lt;BR /&gt;Your fbackup command line should look like this:&lt;BR /&gt; &lt;BR /&gt;fbackup -g graph-file -v -c config-file -f /dev/rmt/some-tape&lt;BR /&gt; &lt;BR /&gt;Your graph-file would contain i /dirpath1 and e /dirpath2, etc to define the actual backup path(s). Repeat i and e as required.&lt;BR /&gt; &lt;BR /&gt;Your config file should look like this:&lt;BR /&gt; &lt;BR /&gt;Contents of the config-file:&lt;BR /&gt;============================&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;</description>
      <pubDate>Sat, 21 Jun 2008 00:42:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-script-question/m-p/4220006#M327351</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2008-06-21T00:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: fbackup script question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-script-question/m-p/4220007#M327352</link>
      <description>Sorry if I wasn't clear. Thanks for the reply.&lt;BR /&gt;&lt;BR /&gt;What you describe is what I expected, so I thought that maybe fbackup spawned a subprocess or something. Maybe the fbackup command just isn't executing so it goes to the next step..&lt;BR /&gt;The script looks like this.&lt;BR /&gt;&lt;BR /&gt;su - oracle -c $ORABIN/stop_database.sh &lt;BR /&gt;/var/adm/fbackupfiles/daily_fbackup.sh &amp;gt;&amp;gt;$LOGFILE&lt;BR /&gt;su - oracle -c $ORABIN/start_database.sh &amp;gt;&amp;gt;$LOGFILE&lt;BR /&gt;&lt;BR /&gt;# more daily_fbackup.sh&lt;BR /&gt;#!/usr/bin/sh&lt;BR /&gt;# HPM Daily FBACKUP Tape creation script&lt;BR /&gt;mt -f /dev/rmt/0m status   &lt;BR /&gt;/usr/sbin/fbackup -v -g /var/adm/fbackupfiles/hpm_daily.graph -f /dev/rmt/0m&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sorry about the formatting. I gues there must be something about my fbackup command that keeps it from running.  I never really used the config file, but find the graph files helpfull.</description>
      <pubDate>Sat, 21 Jun 2008 00:56:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-script-question/m-p/4220007#M327352</guid>
      <dc:creator>Michael Treacy</dc:creator>
      <dc:date>2008-06-21T00:56:33Z</dc:date>
    </item>
    <item>
      <title>Re: fbackup script question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-script-question/m-p/4220008#M327353</link>
      <description>&amp;gt; /var/adm/fbackupfiles/daily_fbackup.sh &amp;gt;&amp;gt;$LOGFILE&lt;BR /&gt; &lt;BR /&gt;That's is the problem. You are not running fbackup but a script. While the script seems to contain simply:&lt;BR /&gt; &lt;BR /&gt;&amp;gt; mt -f /dev/rmt/0m status&lt;BR /&gt;&amp;gt; /usr/sbin/fbackup -v -g /var/adm/fbackupfiles/hpm_daily.graph -f /dev/rmt/0m&lt;BR /&gt; &lt;BR /&gt;I would not use this extra script at all as it complicates the process without adding value. Change your primary script to use the mt and fbackup commands directly. And unless you are using (very old) reel to reel tapes, you need to use a config file. It will improve performance from 30-100%.&lt;BR /&gt; &lt;BR /&gt;So your backup script would look like this:&lt;BR /&gt; &lt;BR /&gt;su - oracle -c $ORABIN/stop_database.sh&lt;BR /&gt;mt -f /dev/rmt/0m status&lt;BR /&gt;/usr/sbin/fbackup -v -g /var/adm/fbackupfiles/hpm_daily.graph -f /dev/rmt/0m &amp;gt;&amp;gt; $LOGFILE&lt;BR /&gt;su - oracle -c $ORABIN/start_database.sh &amp;gt;&amp;gt;$LOGFILE</description>
      <pubDate>Sat, 21 Jun 2008 02:02:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-script-question/m-p/4220008#M327353</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2008-06-21T02:02:28Z</dc:date>
    </item>
    <item>
      <title>Re: fbackup script question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-script-question/m-p/4220009#M327354</link>
      <description>Thanks Bill,&lt;BR /&gt;&lt;BR /&gt;I pulled the fbackup command from the batch file and entered it directly into the script. I think it will work better that way. How did you decide on the parms for the config file ? especially the blocksperrecord and records.&lt;BR /&gt;&lt;BR /&gt;the man page lists these as the defaults on this system as.&lt;BR /&gt;&lt;BR /&gt;blocksperrecord   16&lt;BR /&gt;records           16&lt;BR /&gt;checkpointfreq    256&lt;BR /&gt;readerprocesses   2 (maximum of 6)&lt;BR /&gt;maxretries        5&lt;BR /&gt;retrylimit        5000000&lt;BR /&gt;maxvoluses        100                    chgvol            /var/adm/fbackupfiles/chgvol                          error             /var/adm/fbackupfiles/error                          filesperfsm       200&lt;BR /&gt;&lt;BR /&gt;Each value listed is also the default value, except chgvol and error, which default to null values.&lt;BR /&gt;</description>
      <pubDate>Sat, 21 Jun 2008 02:04:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-script-question/m-p/4220009#M327354</guid>
      <dc:creator>Michael Treacy</dc:creator>
      <dc:date>2008-06-21T02:04:30Z</dc:date>
    </item>
    <item>
      <title>Re: fbackup script question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-script-question/m-p/4220010#M327355</link>
      <description>The default values have not changed since fbackup was first written more than 15 years ago. At that time, reel-to-reel tape drives and cartridge tapes were the standard and there was no such thing as a DDS or DLT tape drive. Reel drives had very primitive electronics and recording technology with limited record sizes and very low throughput. This is due in part to the start-stop nature of the old drives. &lt;BR /&gt; &lt;BR /&gt;Today's tape drives are very fast and require a constant stream of data to avoid resync cycles. Modern tape drives cannot stop and start instantly but instead are designed to run continuously. If the data is delayed due to competing activity on the disks, the drive stops, backs up and once more data arrives, takes a running start to resync and continue -- a very long cycle with zero throughput.&lt;BR /&gt; &lt;BR /&gt;These values are the values needed for DDS, DLT, LTO and any modern tape drive.</description>
      <pubDate>Sat, 21 Jun 2008 13:17:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-script-question/m-p/4220010#M327355</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2008-06-21T13:17:15Z</dc:date>
    </item>
    <item>
      <title>Re: fbackup script question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-script-question/m-p/4220011#M327356</link>
      <description>Thanks again, I think my tape backups will be running faster real soon.</description>
      <pubDate>Sun, 22 Jun 2008 04:50:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-script-question/m-p/4220011#M327356</guid>
      <dc:creator>Michael Treacy</dc:creator>
      <dc:date>2008-06-22T04:50:58Z</dc:date>
    </item>
  </channel>
</rss>

