ISM and multiple instances of the database

How does one, assuming it can be done, use ISM to back up more than one instance of IDS on the same database server. We have two volumes created, file disk elmrDataBkup.20070220.101743 mounted on /data/docs1/elmrDataBkup, write enabled file disk elmrLogsBkup.20070220.101743 mounted on /data/docs1/elmrLLogs, write enabled file disk testDataBkup.20070220.110701 mounted on /data/docs1/testDataBkup, write enabled The elmrDataBkup volume will work, but the testDataBkup will not write. It sets and waits for a writable backup disk. Thank you. Carl in Atlanta

Carl, First of all, the ISM is restricted to work with max. 4 parallel backup= streams. Actually for having more db instances, you could think over a unrestricted storage manager solution such as IBM Tivoli Storage Manage= r or 3rd party, which the advantage that you are able to move the storage manager server to a dedicated box and also might cover other backup tas= ks. I strongly suspect for your case, that all 4 backup streams are already= in use, when you ran into problem with 'testDataBkup'. Probably you might = be able to restrict onconfig parameter BAR_MAXBACKUP, for example to value= '2' to get this resolved. Apart the related 'daemon.log' and 'messages.log', actually the output = of 'ism_show -volumes' and 'ism_show -volume <volume>' might point out whi= ch and how many volumes (resp. streams) are in use at time of occurrance t= he reported problem. If you have one db instance only, three backup streams could be used fo= r parallel dbspace backup and one backup stream for the logical log backu= p, all for one particular database instance. This needs to be prepared of course and the related user env and onconfig of this db instance config= ured properly. In case you change the ISM configuration to use one backup stream for dbspace backup and another one for logical log backup, you will have another 2 backup stream left, but the disadvantage that dbspace backup = will be serialized. If you take over this disadvantage you might be able to configure IBM a= nd another parallel running db instance to use one one backup stream of dbspace backup and one stream for logical log backup. In case of using only one db instance at a time, although several insta= lled db instances on one host, you may toggle the ISM config, depending on t= he db instance which is up and running to keep the ability to parallelize = the dbspace backup. HTH, Robert Robert Seifert _______________________________________________________________________= _____ IBM Deutschland GmbH, Software, Information Management, Informix Products, Advanced Support Elite VAR support engineer Development Support for IBM Informix Products on-site @ SAP c/o SAP AG, -PS03-,Neurottstrasse 16, D-69190 Walldorf, Germany _______________________________________________________________________= _____ _______________________________________________________________________= _____ Dieses Mail stammt von Robert Seifert, Mitarbeiter der IBM Deutschland GmbH, handelnd im Auftrag (i.A.) von: This is a mail from Robert Seifert, employee of IBM Deutschland GmbH, on behalf of: IBM Deutschland GmbH Vorsitzender des Aufsichtsrats: Hans Ulrich Maerki Gesch=E4ftsf=FChrung: Martin Jetter (Vorsitzender), Rudol= f Bauer, Christian Diedrich, Christoph Grandpier= re, Matthias Hartmann, Andreas Kerstan Sitz der Gesellschaft: Stuttgart Registergericht: Amtsgericht Stuttgart, HRB 14562 WEEE-Reg.-Nr.: DE 99369940 ids-bounces@iiug.org wrote on 20.02.2007 20:15:01: > How does one, assuming it can be done, use ISM to back up more than o= ne > instance of IDS on the same database server. > We have two volumes created, file disk elmrDataBkup.20070220.101743 > mounted on > /data/docs1/elmrDataBkup, write enabled > file disk elmrLogsBkup.20070220.101743 mounted on > /data/docs1/elmrLLogs, write > enabled > file disk testDataBkup.20070220.110701 mounted on /data/docs1/testDataBkup, > write enabled > The elmrDataBkup volume will work, but the testDataBkup will not writ= e. It > sets and waits for a writable backup disk. > > Thank you. > > Carl in Atlanta > > > ***********************************************************************= ******** > Forum Note: Use "Reply" to post a response in the discussion forum.= >=

OT My apologies for this bad formatted mail. It looks to me that I have to switch over to use a personal mail account to cover also this issue. It seems something changed in my mail appl, since the mail will now terribly reformatted while sending. OT off Thanks in advance for understanding, Robert ----- Forwarded by Robert Seifert/Germany/IBM on 21.02.2007 10:57 ----- ids-bounces@iiug.org wrote on 21.02.2007 10:36:39: > Carl, > > First of all, the ISM is restricted to work with max. 4 parallel backup= > > streams. Actually for having more db instances, you could think over a > unrestricted storage manager solution such as IBM Tivoli Storage Manage= > r or > 3rd party, which the advantage that you are able to move the storage > manager server to a dedicated box and also might cover other backup tas= > ks. > > I strongly suspect for your case, that all 4 backup streams are already= > in > use, when you ran into problem with 'testDataBkup'. Probably you might = > be > able to restrict onconfig parameter BAR_MAXBACKUP, for example to value= > '2' > to get this resolved. > Apart the related 'daemon.log' and 'messages.log', actually the output = > of > 'ism_show -volumes' and 'ism_show -volume <volume>' might point out whi= > ch > and how many volumes (resp. streams) are in use at time of occurrance t= > he > reported problem. > > If you have one db instance only, three backup streams could be used fo= > r > parallel dbspace backup and one backup stream for the logical log backu= > p, > all for one particular database instance. This needs to be prepared of > course and the related user env and onconfig of this db instance config= > ured > properly. > > In case you change the ISM configuration to use one backup stream for > dbspace backup and another one for logical log backup, you will have > another 2 backup stream left, but the disadvantage that dbspace backup = > will > be serialized. > > If you take over this disadvantage you might be able to configure IBM a= > nd > another parallel running db instance to use one one backup stream of > dbspace backup and one stream for logical log backup. > > In case of using only one db instance at a time, although several insta= > lled > db instances on one host, you may toggle the ISM config, depending on t= > he > db instance which is up and running to keep the ability to parallelize = > the > dbspace backup. > > HTH, > Robert > > Robert Seifert > _______________________________________________________________________= > _____ > > IBM Deutschland GmbH, Software, Information Management, > Informix Products, Advanced Support > > Elite VAR support engineer > Development Support for IBM Informix Products on-site @ SAP > c/o SAP AG, -PS03-,Neurottstrasse 16, D-69190 Walldorf, Germany > _______________________________________________________________________= > _____ > > _______________________________________________________________________= > _____ > > Dieses Mail stammt von Robert Seifert, Mitarbeiter der IBM Deutschland > GmbH, > handelnd im Auftrag (i.A.) von: > This is a mail from Robert Seifert, employee of IBM Deutschland GmbH, > on behalf of: > > IBM Deutschland GmbH > > Vorsitzender des Aufsichtsrats: Hans Ulrich Maerki > Gesch=E4ftsf=FChrung: Martin Jetter (Vorsitzender), Rudol= > f Bauer, > > Christian Diedrich, Christoph Grandpier= > re, > > Matthias Hartmann, Andreas Kerstan > Sitz der Gesellschaft: Stuttgart > Registergericht: Amtsgericht Stuttgart, HRB 14562 > WEEE-Reg.-Nr.: DE 99369940 > > ids-bounces@iiug.org wrote on 20.02.2007 20:15:01: > > > How does one, assuming it can be done, use ISM to back up more than o= > ne > > instance of IDS on the same database server. > > We have two volumes created, file disk elmrDataBkup.20070220.101743 > > mounted on > > /data/docs1/elmrDataBkup, write enabled > > file disk elmrLogsBkup.20070220.101743 mounted on > > /data/docs1/elmrLLogs, write > > enabled > > file disk testDataBkup.20070220.110701 mounted on > /data/docs1/testDataBkup, > > write enabled > > The elmrDataBkup volume will work, but the testDataBkup will not writ= > e. > It > > sets and waits for a writable backup disk. > > > > Thank you. > > > > Carl in Atlanta > > > > > > > ***********************************************************************= > ******** > > > Forum Note: Use "Reply" to post a response in the discussion forum.= > > >= > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >

You should be able to just back up the other DBServers with onbar. You may need to check the ONCONFIG file for other DBServers and make sure that the ISM_DATA and ISM_LOGS pools are the same as the DBServer which you are already backing up.