ISM Cannot Process DBSPACES that are 2GB or Greater in Size

I am reviewing the doctumentation that came with IDS 9.40.UC5 and something caught my eye. In the file "ids_ism_docnotes_9.40.txt" there is the following statement in section 1.2.1 "1.2.1 ISM Cannot Process DBSPACES that are 2GB or Greater in Size The Legato NetWorker 5.1 code used by ISM has a 2 GB size limitation." So whats the point of getting rid of the 2GB dbspace limitation and still bundling the Legato Networker code that doesn't support it. Come on IBM lets turn on our thinking caps. ---------- CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,is for the sole use of the intended recipient(s), even if addressed incorrectly, and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy or delete all copies of the original message and all attachments, including deletion from the trash or equivalent folder. Thank you. ------------=_1096657582-4311-534--

Cuz IBM provides this bundle free of charge, and most people have other company standard backup software anyway.... Like full blown Legato (not "legato light" which is what Informix used to bundle as ISM), or Veritas Netbackup, etc.... Pick on IBM, but not too hard please.... The didn't drop informix, they are growing it... No, I don't work for them... Norma Jean -----Original Message----- From: forum.subscriber@iiug.org [mailto:forum.subscriber@iiug.org] On Behalf Of Peter J Dia.... Sent: Friday, October 01, 2004 2:11 PM To: ids@iiug.org Subject: ISM Cannot Process DBSPACES that are 2GB or Greater in Size [3522] I am reviewing the doctumentation that came with IDS 9.40.UC5 and something caught my eye. In the file "ids_ism_docnotes_9.40.txt" there is the following statement in section 1.2.1 "1.2.1 ISM Cannot Process DBSPACES that are 2GB or Greater in Size The Legato NetWorker 5.1 code used by ISM has a 2 GB size limitation." So whats the point of getting rid of the 2GB dbspace limitation and still bundling the Legato Networker code that doesn't support it. Come on IBM lets turn on our thinking caps. ---------- CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,is for the sole use of the intended recipient(s), even if addressed incorrectly, and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy or delete all copies of the original message and all attachments, including deletion from the trash or equivalent folder. Thank you. ------------=_1096657582-4311-534-- ----------------------------------------- ============================================================ The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs ============================================================

Peter J Dia.... wrote: > I am reviewing the doctumentation that came with IDS 9.40.UC5 and > something caught my eye. > > In the file "ids_ism_docnotes_9.40.txt" there is the following statement > in section 1.2.1 > > > "1.2.1 ISM Cannot Process DBSPACES that are 2GB or Greater in Size > > The Legato NetWorker 5.1 code used by ISM has a 2 GB size limitation." > > > So whats the point of getting rid of the 2GB dbspace limitation and > still bundling > the Legato Networker code that doesn't support it. Do you mean "chunk limit" or "dbspace limit"? I think the dbspace limit used to be about 4 Tb. Cheers, -- Mark. +----------------------------------------------------------+-----------+ | Mark D. Stock mailto:mdstock@MydasSolutions.com |//////// /| | http://MydasSolutions.com |///// / //| | +-----------------------------------+//// / ///| | |We value your comments, which have |/// / ////| | |been recorded and automatically |// / /////| | |emailed back to us for our records.|/ ////////| +----------------------+-----------------------------------+-----------+

Hi, actually this is a misunderstanding on our part. ISM _can_ very well process dbspaces greater than 2 GB. Also there's nothing in ISM that would limit chunk size to 2 GB (just to make that clear as well). ISM has an option to use the file system as backup media ("ism_add -device <directory> -type file"). ISM will then create files in this directory to store the backup data. And due to a limit in ISM's file handling, these files cannot be bigger than 2 GB. Therefore ISM creates multiple files when necessary and splits the data of backup objects bigger than 2 GB into these several files. This limit does not apply to tape drive media used with ISM, but only to "file system media". Since the backup data of dbspaces is sent to (and received from) ISM via some special portion in the IDS shared memory (and not the file system), there is no limitation to dbspace/chunk size. However, if you use ISM to backup file system files and these files would grow over 2 GB in size, then you have a problem. Usually backed up files are only some index files of ISM itself and maybe things like the ixbar file. I hope that none of these grows larger than 2 GB. (I guess you'd notice long before that there'd be a significant performance penalty when using ON-Bar and ISM.) [ BTW: a scrutinizing reader of release notes may notice, that the wrong note talks about DBSPACES being greater than 2 GB. But this is nothing new, as dbspaces consist of several chunks, where e.g. 5 chunks 2 GB each add up to 10 GB. And that was before the 2 GB chunk limit was removed. But backing up such a 10 GB dbspace never was a problem before and the ISM code (derived from Legato Networker) hasn't changed. So as I said before there is quite a misunderstanding.] This error in the release notes will be fixed (i.e. removed) with the next version. Regards, Martin -- Martin Fuerderer IBM Informix Development Munich Data Management Solutions forum.subscriber@iiug.org wrote on 01.10.2004 21:10:46: > > I am reviewing the doctumentation that came with IDS 9.40.UC5 and > something caught my eye. > > In the file "ids_ism_docnotes_9.40.txt" there is the following statement > in section 1.2.1 > > "1.2.1 ISM Cannot Process DBSPACES that are 2GB or Greater in Size > > The Legato NetWorker 5.1 code used by ISM has a 2 GB size limitation." > > So whats the point of getting rid of the 2GB dbspace limitation and > still bundling > the Legato Networker code that doesn't support it. > > Come on IBM lets turn on our thinking caps. >

Martin, Thank you very much for clearing this up. :-) -Peter J Diaz de Leon Martin Fuerderer wrote: >Hi, > >actually this is a misunderstanding on our part. > >ISM _can_ very well process dbspaces greater than 2 GB. >Also there's nothing in ISM that would limit chunk size to >2 GB (just to make that clear as well). > >ISM has an option to use the file system as backup media >("ism_add -device <directory> -type file"). ISM will then create >files in this directory to store the backup data. And due to a >limit in ISM's file handling, these files cannot be bigger than >2 GB. Therefore ISM creates multiple files when necessary >and splits the data of backup objects bigger than 2 GB into >these several files. >This limit does not apply to tape drive media used with ISM, >but only to "file system media". > >Since the backup data of dbspaces is sent to (and received from) >ISM via some special portion in the IDS shared memory (and >not the file system), there is no limitation to dbspace/chunk size. > >However, if you use ISM to backup file system files and these >files would grow over 2 GB in size, then you have a problem. >Usually backed up files are only some index files of ISM itself >and maybe things like the ixbar file. I hope that none of these >grows larger than 2 GB. (I guess you'd notice long before that >there'd be a significant performance penalty when using ON-Bar >and ISM.) > >[ BTW: a scrutinizing reader of release notes may notice, that > the wrong note talks about DBSPACES being greater than > 2 GB. But this is nothing new, as dbspaces consist of several > chunks, where e.g. 5 chunks 2 GB each add up to 10 GB. > And that was before the 2 GB chunk limit was removed. But > backing up such a 10 GB dbspace never was a problem before > and the ISM code (derived from Legato Networker) hasn't > changed. So as I said before there is quite a misunderstanding.] > >This error in the release notes will be fixed (i.e. removed) with the >next version. > >Regards, >Martin >-- >Martin Fuerderer >IBM Informix Development Munich >Data Management Solutions > >forum.subscriber@iiug.org wrote on 01.10.2004 21:10:46: > > >>I am reviewing the doctumentation that came with IDS 9.40.UC5 and >>something caught my eye. >> >>In the file "ids_ism_docnotes_9.40.txt" there is the following statement >> >> > > > >>in section 1.2.1 >> >>"1.2.1 ISM Cannot Process DBSPACES that are 2GB or Greater in Size >> >>The Legato NetWorker 5.1 code used by ISM has a 2 GB size limitation." >> >>So whats the point of getting rid of the 2GB dbspace limitation and >>still bundling >>the Legato Networker code that doesn't support it. >> >>Come on IBM lets turn on our thinking caps. >> >> >> ---------- CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,is for the sole use of the intended recipient(s), even if addressed incorrectly, and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy or delete all copies of the original message and all attachments, including deletion from the trash or equivalent folder. Thank you.