Re: Multiple instances and ISM

Posted in 2003

The Big Potatoe — Tue, 01 Jul 2003 12:39:13 +0100 — source: Usenet: comp.databases.informix

No ;) You can have many instances using the same pools within one Storage Manager. The pools just represent where to shove the data / logs. The unique ids returned from the storage manager and placed in the ixbar.servernum are how a restore identifies what objects are needed. If you list what is stored on the volumes you will see the sernername is used to identify the objects on the media as well. So all your instances can have ISMData / ISMLlogs or ISMDiskData or ISMDiskLogs. I have version 7, version 8 and version 9 all going to one ISM which is running under the Version 7 environment. Squashed potato Weallans, Malcolm wrote: > This message is in MIME format. Since your mail reader does not understand > this format, some or all of this message may not be legible. > > ------_=_NextPart_001_01C33F1C.ADA3E760 > Content-Type: text/plain > > We are using ISM and archiving the system and logs to a filesystem for > later filesystem archive to tape. We have two instances. I assume that we > need to specify different pool names for system and logs for each instance. > > e.g. instance a would have 2 pools ISMLogs.a and ISMdata.a and instance b > would have 2 pools ISMLogs.b and ISMdata.b > > But there is only one onbar script which referes to a pool ISMData. > > Am I right in assuming that we would need to pass a parameter to the onbar > script to specify the instance so that we can clean up for that instance > only? > > Has anybody else used onbar and ISM on a multi-instance server? If so, any > guidelines/gotchas? > > Regards > > > > Malcolm > > > ************************************************************************** > The information transmitted herewith is sensitive information intended only > for use by the individual or entity to which it is addressed. If the reader > of this message is not the intended recipient, you are hereby notified that > any review, retransmission, dissemination, distribution, copying or other > use of, or taking of any action in reliance upon this information is > strictly prohibited. If you have received this communication in error, > please contact the sender and delete the material from your computer. > > ------_=_NextPart_001_01C33F1C.ADA3E760 > Content-Type: text/html > Content-Transfer-Encoding: quoted-printable > > <html> > > <head> > <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = > charset=3DUS-ASCII"> > > > <meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)"> > > <style> >  > </style> > > </head> > > <body lang=3DEN-GB link=3Dblue vlink=3Dpurple> > > <div class=3DSection1> > > style=3D'font-size:10.0pt; > font-family:Arial'>We are using ISM and archiving the system and logs = > to a filesystem >  for later filesystem archive to tape.  We have two = > instances.  > I assume that we need to specify different pool names for system and = > logs for > each instance. > > style=3D'font-size:10.0pt; > font-family:Arial'>e.g. instance a would have 2 pools ISMLogs.a and = > ISMdata.a > and instance b would have 2 pools ISMLogs.b and = > ISMdata.b > > style=3D'font-size:10.0pt; > font-family:Arial'>But there is only one onbar script which referes to = > a pool ISMData.  > > > style=3D'font-size:10.0pt; > font-family:Arial'>Am I right in assuming that we would need to pass a > parameter to the onbar script to specify the instance so that we can = > clean up > for that instance only? > > style=3D'font-size:10.0pt; > font-family:Arial'>Has anybody else used onbar and ISM on a = > multi-instance > server?  If so, any guidelines/gotchas? > > style=3D'font-size:10.0pt; > font-family:Arial'>Regards > > style=3D'font-size:10.0pt; > font-family:Arial'>  > > style=3D'font-size:10.0pt; > font-family:Arial'>Malcolm > > </div> > > </body> > > </html> > > = > ************************************************************************= > ** The information transmitted herewith is sensitive = > information intended only for use by the individual or entity to which = > it is addressed. If the reader of this message is not the intended = > recipient, you are hereby notified that any review, retransmission, = > dissemination, distribution, copying or other use of, or taking of any = > action in reliance upon this information is strictly prohibited. If you = > have received this communication in error, please contact the sender = > and delete the material from your computer. > > ------_=_NextPart_001_01C33F1C.ADA3E760-- > sending to informix-list