<?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: backup size in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/backup-size/m-p/2775187#M75766</link>
    <description>Michael&lt;BR /&gt;thanks. yes, it does seem that tmp is the directory with the largest difference and the others are much more similar to your example.  thanks for the explanation.&lt;BR /&gt;Maria.</description>
    <pubDate>Tue, 30 Jul 2002 01:53:44 GMT</pubDate>
    <dc:creator>Peter Gillis</dc:creator>
    <dc:date>2002-07-30T01:53:44Z</dc:date>
    <item>
      <title>backup size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/backup-size/m-p/2775182#M75761</link>
      <description>i need to supply a number that indicates how much space is used when we do full system backup.  I have checked output of fbackup:  There is a figure there:  total blocks written to output:  14,358,342.  Since this is blocks, I am wondering how to convert to megabytes?&lt;BR /&gt;Is there any other (more reliable?) way to get&lt;BR /&gt;this type of info?&lt;BR /&gt;system hp-ux 11.00&lt;BR /&gt;machine d220 &lt;BR /&gt;&lt;BR /&gt;Thanks for you help with this&lt;BR /&gt;Maria</description>
      <pubDate>Tue, 30 Jul 2002 00:09:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/backup-size/m-p/2775182#M75761</guid>
      <dc:creator>Peter Gillis</dc:creator>
      <dc:date>2002-07-30T00:09:39Z</dc:date>
    </item>
    <item>
      <title>Re: backup size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/backup-size/m-p/2775183#M75762</link>
      <description>The blocksize for all reasonably  modern versions of fbackup is 1024 bytes; very old versions were 512 bytes.&lt;BR /&gt;&lt;BR /&gt;Since 1MB = 1024X1024 your answer is&lt;BR /&gt;&lt;BR /&gt;Backup Size (MB) = NBLOCKS / 1024.</description>
      <pubDate>Tue, 30 Jul 2002 00:22:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/backup-size/m-p/2775183#M75762</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2002-07-30T00:22:03Z</dc:date>
    </item>
    <item>
      <title>Re: backup size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/backup-size/m-p/2775184#M75763</link>
      <description>Maria,&lt;BR /&gt;&lt;BR /&gt;Clay is absolutely right.  From the man page for fbackup on a 11.11 system:&lt;BR /&gt;&lt;BR /&gt;"Note also that the blocksize used in&lt;BR /&gt; earlier releases (7.0 and before) was 512 bytes, whereas it is now  1024 bytes."           &lt;BR /&gt;&lt;BR /&gt;Tom&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Jul 2002 00:35:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/backup-size/m-p/2775184#M75763</guid>
      <dc:creator>Tom Dawson</dc:creator>
      <dc:date>2002-07-30T00:35:33Z</dc:date>
    </item>
    <item>
      <title>Re: backup size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/backup-size/m-p/2775185#M75764</link>
      <description>Thanks Clay - a related question.  How come on issuing bdf cmd the used field for a filesystem says, for example, /tmp  3150 ;  and when I do a cd /tmp, and then go du -sk it replies back with 1961?&lt;BR /&gt;&lt;BR /&gt;thanks Maria.</description>
      <pubDate>Tue, 30 Jul 2002 00:35:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/backup-size/m-p/2775185#M75764</guid>
      <dc:creator>Peter Gillis</dc:creator>
      <dc:date>2002-07-30T00:35:37Z</dc:date>
    </item>
    <item>
      <title>Re: backup size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/backup-size/m-p/2775186#M75765</link>
      <description>Hi Maria,&lt;BR /&gt;&lt;BR /&gt;# bdf /tmp&lt;BR /&gt;Filesystem          kbytes    used   avail %used Mounted on&lt;BR /&gt;/dev/vg00/lvol5     524288  336820  175795   66% /tmp&lt;BR /&gt;# du -sk&lt;BR /&gt;335397  .&lt;BR /&gt;&lt;BR /&gt;At a guess I would say that your problem relates to file(s) that may have been removed, but are still in use by the system. The example from one of my systems suggests that I don't have a similar problem to yours. Doing this on /tmp may produce these differences many times as it is really a dumping ground for many processes. What happens when you do this on any other filesystems? I think you'll find that they are ok.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;Michael</description>
      <pubDate>Tue, 30 Jul 2002 00:46:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/backup-size/m-p/2775186#M75765</guid>
      <dc:creator>Michael Tully</dc:creator>
      <dc:date>2002-07-30T00:46:17Z</dc:date>
    </item>
    <item>
      <title>Re: backup size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/backup-size/m-p/2775187#M75766</link>
      <description>Michael&lt;BR /&gt;thanks. yes, it does seem that tmp is the directory with the largest difference and the others are much more similar to your example.  thanks for the explanation.&lt;BR /&gt;Maria.</description>
      <pubDate>Tue, 30 Jul 2002 01:53:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/backup-size/m-p/2775187#M75766</guid>
      <dc:creator>Peter Gillis</dc:creator>
      <dc:date>2002-07-30T01:53:44Z</dc:date>
    </item>
  </channel>
</rss>

