ISM backups query – Informix Archive

david@smooth1.co.uk — Thu, 19 Aug 2010 13:30:44 -0700 (PDT) — source: Usenet: comp.databases.informix

On 17 Aug, 20:42, "da...@smooth1.co.uk" <da...@smooth1.co.uk> wrote: > On 17 Aug, 16:47, Malc <mal...@googlemail.com> wrote: > > > Hah! > > Somehow - and I'm not sure of the route I got there - I found Legato's > > "mminfo" command and the online manual thereto. > > It still needs some serious jiggery-pokery to find all the right info > > but it CAN be made to list the files in a format which needs some grep/ > > sed/awk to make it useable.. > > > It shouldn't be this difficult, surely? > > ism_show -volumes Checking around the net The $INFORMIXDIR/etc/ixbar.<servernum> file contains the saveset id around the 7th column and the saveset id is shown by ism_show -volume <volujme name>.

↪ replying to david@smooth1.co.uk

Malc — Fri, 20 Aug 2010 01:18:32 -0700 (PDT) — source: Usenet: comp.databases.informix

Sure! ism_show -volumes volume pool flags written (%) expires ISMData001 ISMDiskData 3291 MB 100% 08/15/12 ISMData2_001 ISMDiskData 480 KB 100% 08/18/12 ISMLogs001 ISMDiskLogs 320 KB 100% 08/15/12 ISMLogs2_001 ISMDiskLogs 64 KB 100% 08/18/12 ism_show -volumeISMData001 ssid name clflg total date 195 /opt/informix_new/ism/index/dev.enterprise.capita.zone 505848 08/16/10 193 <1>INFORMIX:/evalshm/trans/0 40891552 08/16/10 196 bootstrap 106600 08/16/10 183 INFORMIX:/evalshm/a_blobs/0 127216 08/16/10 186 INFORMIX:/evalshm/bigtabs/0 28890904 08/16/10 181 INFORMIX:/evalshm/biz/0 251761856 08/16/10 190 INFORMIX:/evalshm/deriv_1/0 21779352 08/16/10 180 INFORMIX:/evalshm/evalrootdbs/0 14096344 08/16/10 189 INFORMIX:/evalshm/inetspace/0 484284220 08/16/10 182 INFORMIX:/evalshm/logs/0 63712 08/16/10 187 INFORMIX:/evalshm/misc/0 163438920 08/16/10 184 INFORMIX:/evalshm/print/0 317700 08/16/10 188 INFORMIX:/evalshm/q_blobs/0 63720 08/16/10 185 INFORMIX:/evalshm/ref/0 121531560 08/16/10 191 INFORMIX:/evalshm/sys/0 40193184 08/16/10 192 INFORMIX:/evalshm/trans/0 2048000188 08/16/10 Promising...so this is telling me that 196 is a bootstrap and 195 is an index file, presumably used by the nsr component of ISM. The saveset id is just the file number of one of the dbspace backup files. Hmmmm - using bar_act.log and scanning the output for that particular level 0: 2010-08-16 16:39:14 8834 8316 Completed level 0 backup deriv_1 (Storage Manager copy ID: 190 0) 2010-08-16 16:39:14 8834 8316 Process 8834 8316 completed ...and so on; the onbar backup reference being in this case 8316, 8834 being the id for that dbspace, the Storage Manager copy ID telling me the ISM ssid. OK; so I still need to awk/sed/grep and so on from ism_show -volume <volname> and bar_act.log and cross-correlate. This is a steep learning curve and it's important I get an understanding, but I suppose what I'm looking for is one output file that says "The level 0 backup instigated at 2010-08-16 16:39:00 contains the following files: 180.0

↪ replying to Malc

Malc — Fri, 20 Aug 2010 01:19:27 -0700 (PDT) — source: Usenet: comp.databases.informix

On Aug 20, 9:18 am, Malc <mal...@googlemail.com> wrote: > Sure! > ism_show -volumes > volume pool flags written (%) > expires > ISMData001 ISMDiskData 3291 MB 100% > 08/15/12 > ISMData2_001 ISMDiskData 480 KB 100% > 08/18/12 > ISMLogs001 ISMDiskLogs 320 KB 100% > 08/15/12 > ISMLogs2_001 ISMDiskLogs 64 KB 100% > 08/18/12 > > ism_show -volumeISMData001 > ssid name clflg total > date > 195 /opt/informix_new/ism/index/dev.enterprise.capita.zone 505848 > 08/16/10 > 193 <1>INFORMIX:/evalshm/trans/0 40891552 > 08/16/10 > 196 bootstrap 106600 > 08/16/10 > 183 INFORMIX:/evalshm/a_blobs/0 127216 > 08/16/10 > 186 INFORMIX:/evalshm/bigtabs/0 28890904 > 08/16/10 > 181 INFORMIX:/evalshm/biz/0 251761856 > 08/16/10 > 190 INFORMIX:/evalshm/deriv_1/0 21779352 > 08/16/10 > 180 INFORMIX:/evalshm/evalrootdbs/0 14096344 > 08/16/10 > 189 INFORMIX:/evalshm/inetspace/0 484284220 > 08/16/10 > 182 INFORMIX:/evalshm/logs/0 63712 > 08/16/10 > 187 INFORMIX:/evalshm/misc/0 163438920 > 08/16/10 > 184 INFORMIX:/evalshm/print/0 317700 > 08/16/10 > 188 INFORMIX:/evalshm/q_blobs/0 63720 > 08/16/10 > 185 INFORMIX:/evalshm/ref/0 121531560 > 08/16/10 > 191 INFORMIX:/evalshm/sys/0 40193184 > 08/16/10 > 192 INFORMIX:/evalshm/trans/0 2048000188 > 08/16/10 > > Promising...so this is telling me that 196 is a bootstrap and 195 is > an index file, presumably used by the nsr component of ISM. > The saveset id is just the file number of one of the dbspace backup > files. Hmmmm - using bar_act.log and scanning the output for that > particular level 0: > 2010-08-16 16:39:14 8834 8316 Completed level 0 backup deriv_1 > (Storage Manager copy ID: 190 0) > 2010-08-16 16:39:14 8834 8316 Process 8834 8316 completed > ...and so on; the onbar backup reference being in this case 8316, 8834 > being the id for that dbspace, the Storage Manager copy ID telling me > the ISM ssid. > > OK; so I still need to awk/sed/grep and so on from ism_show -volume > <volname> and bar_act.log and cross-correlate. > This is a steep learning curve and it's important I get an > understanding, but I suppose what I'm looking for is one output file > that says "The level 0 backup instigated at 2010-08-16 16:39:00 > contains the following files: > 180.0 Sorry hit send in the middle there! Should read 180.0

↪ replying to Malc

Malc — Fri, 20 Aug 2010 01:25:02 -0700 (PDT) — source: Usenet: comp.databases.informix

Damn useless web client translating "tab" as "hit send"... Should read "The level 0 backup instigated at 2010-08-16 16:39:00 contains the following files: Volume ISMData001: 180.0 evalrootdbs 181.0 biz [182.0 to 193.0 same format] 195.0 index file 196.0 bootstrap file Volume ISMLogs001: 194.0" This would be very nice.

Re: ISM backups query

Your privacy choices