🚀 go-pugleaf

In article <4ohb0p$o6a@mule1.mindspring.com>, dsmith@mindspring.com 
says...
>
snip--------
>Question: What is different about the morning after I run a
>tape backup? The problem happens even if I down the server,
>and disconnect the tape drive after running the backup.
>Could it be that either running the tape backup or downing
>the server is causing Novell to compress a large betrieve
>data file (4+ megs) which is from a very old version of
>betrieve. Then the following morning, when someone uses that
>file, something is causing the SCSI bus to hang?
>
>Thanks for any ideas.


I have a client that has w/s's that hang sometimes when accessing a 
btrieve file.  I have researched the problem and found that compression is 
turned on that volume.  (Ver 4.1) Btrieve has a parameter in the setup 
program that tells it the largest compressed file to be able to handle.  
It deals with memory buffers available.  The default is none.  I haven't 
adjusted the setting yet, so I don't know if that is the problem, but when 
you mentioned compressed Btrieve files, well...........I think it can be 
set with a command line parameter when btrieve is loaded on the server.  I 
don't have the manual in front of me, but it's in the installation and 
setup section of the Btrieve manual. Search the CDROM manual for 
compression.

I have another client that locks up after tape backups.  Colorado has 
specific SCSI cards they approve. (http://www.hp.com)  They also recommend 
third party software if you have Netware 4.1.  Their software looks to 
close the bindery for backup and can't find it and locks up, IE no backup. 
 Conner may have the same situation.