Re: pyramid 2 gig limit on backup
Posted in 1996
June Tong (junet@informix.com) wrote:
: David Williams (djw@smooth1.demon.co.uk) wrote:
: : In article <56v3sj$ep6@atglab10.atglab.bls.com>, tolly brumbelow
: : <tolly.brumbelow@bridge.bst.bls.com> writes
: : >We run informix backups to a disk dataset on a nightly basis and then
: This is not true. Informix supports archive devices up to 2 TERAbytes.
: lseek is not used by the Informix archive utilities.
: However, I don't know of any parameter that can be tuned to allow you to
: write more than 2GB into a file. Generally, when this is a problem, it is
: because the OS is counting all the data that is written to the device, and
: overflows when it passes 2GB. However, I didn't think Pyramid was one of
: those OS'es; I used to have a customer on Pyramid who used 5GB tape devices.
: I'd suggest calling Pyramid. I believe the call ontape makes (if you're
: using ontape) is write().
: June
June,
The explanation that Williams gives is exactly the same explanation that
I got from Informix Support when we had the identical problem on a Pyramid
MIS machine. I was told that ontape (don't know about on-archive) does it
all in one long write, and that write is limited to 2GB. They indicated
that Pyramid might be able to up it 4GB by using an unsigned index variable,
but in no case could it go over 4GB. Any customer can use 5GB tape
drives.....but are they really using all of it? I'll bet they blow up at 2 GB.
Joe
: ---- June Tong Informix Software ----
: ---- Senior Consultant (415) 926-6140 ----
: ---- International Support junet@informix.com ----
: ---- Location-du-jour: Menlo Park ----
: *
: * Standard disclaimers apply
: *
: - Please do not send me requests/questions by mail. When I have the knowledge
: - and time permits, I try to answer questions on comp.databases.informix, but
: - travel schedule, time, and volume make responding to personal requests
: - difficult and often slow. Please call your local Informix Technical Support
: - organization for assistance with technical issues.
--
---------------------------------------------------------------------------
Joe Lumbley(jlumbley@netcom.com)
---------------------------------------------------------------------------