The Miserable File History problem....<br><br>I actually have a level 0 that takes over 8 hours to pass file history info which means the dump does not start until that point.<br><br>Just for kicks, you could modify your policy to have the first line as &quot;set hist = n&quot; (without quotes).
<br>This will kill the file history. You will be unable to restore files (directories only) and you will not have DAR<br>which means you will have to read the ENTIRE backup tape or tape set.<br>Instead of looking at pure size, do a &quot;df -h&quot; and a &quot;df -i&quot; to how much and how many (files) you are backing up.
<br>You can always dived the size used by the files used to see average file size.<br><br>Heck for that matter you could scan the filesystem with the filestats command and you could scan from a NFS client<br>to see which directories are huge (I have a number of directories that are 50MB in size-&gt; this KILLLLS a backup)
<br><br><br><div><span class="gmail_quote">On 6/19/07, <b class="gmail_sendername">Page, Jeremy</b> &lt;<a href="mailto:jeremy.page@gilbarco.com">jeremy.page@gilbarco.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">




<div>
<div><span><font color="#800000" face="Tahoma" size="2">We 
are backing up a 270c nightly with Netbackup via NDMP to a dual drive LTO3 
machine (only one drive is used for to backup the filer). There are 2.25 TB on 
one head and 1.1TB on the other. For a full backup it takes about 10 hours to 
write to tape, which I don&#39;t think is too bad (larger volumes hit 31200 KB/sec 
reported by Netbackup), but the differentials take 5 hours to run,even though 
the delta on our data is very small.</font></span></div>
<div><span><font color="#800000" face="Tahoma" size="2"></font></span>&nbsp;</div>
<div><span><font color="#800000" face="Tahoma" size="2">&nbsp;I suspect this is more of a Netbackup issue then a filer based one 
but wanted to throw it out there incase there was something I should look at on 
the host side. This is over a normal gigE switched network connection with the 
default settings on the filer, network-wise. We are not using virtual 
interfaces, both heads have a single 1 gig connection to the LAN. Any 
suggestions or inventive flames are welcome.</font></span></div></div>

<p>

This message (including any attachments) contains confidential <br>
and/or proprietary information intended only for the addressee.  <br>
Any unauthorized disclosure, copying, distribution or reliance on <br>
the contents of this information is strictly prohibited and may <br>
constitute a violation of law.  If you are not the intended <br>
recipient, please notify the sender immediately by responding to <br>
this e-mail, and delete the message from your system.  If you <br>
have any questions about this e-mail please notify the sender <br>
immediately. <br>
</p></blockquote></div><br><br clear="all"><br>-- <br>--tmac<br><br>RedHat Certified Engineer&nbsp;