Re: ISM backups query

OK what I get is this: Start a clean instance of ISM with emtpy storage paths on disk for Data (ISMDiskData) and logs (ISMDiskLogs). Perform a full backup to disk of a test instance. Result: in ISMDiskData are files numbered 180.0 to 193.0, then 195.0 and 196.0, in ISMDiskLogs is file 194.0 I can cross-correlate files 180.0 up to 192.0 using bar_act.log to their related dbspaces. I can cross-correlate file 194.0 using bar_act.log to a logical log. I get an email with the text: date time level ssid file record volume 08/16/10 16:42:05 full 196 196 0 ISMData001 So I can see that file 196.0 is the bootstrap file. If I "strings" file 193.0 I see the text "continued save file from ssid 192, savetime 1281973019" This makes sense because the dbspace that file 192.0 refers to backs up to > 2Gb. SO: now I know which files relate to dbspaces and logical logs and I can identify the bootstrap file from the email. Annoyances that need resolving: I need to be able automatically to produce a report after doing a backup, listing all the files that are necessary if I were to want to restore the backup. There is NOWHERE that I can see that explains that file 192.0 is continued in 193.0, so I can't create a report reflecting this (without doing some dodgy scripting making assumptions regarding the backup time). I can't see anything telling me on the source system that file 196.0 is the bootstrap file, all I have is the email telling me. I can't see anything that refers to file 195.0, anywhere. There's nothing in the sysutils database that gives any of this information, and nothing in the nsr log path either. Does anyone know of an nsradmin command that lists the paths used in any particular backup?

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?

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

On Aug 17, 8:42 pm, "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 Only shows paths to the backed-up files, no other info.

On 17/08/2010 21:19, Malc wrote: > On Aug 17, 8:42 pm, "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 > > Only shows paths to the backed-up files, no other info. ism_show -volume "volume_name"? Not really sure what you are trying to achieve here, but the most salient thing to understand is : 1. ISM will back up "objects" and has no real understanding of "dbspaces" or "logical logs" 2. Informix sends dbspaces and logical log "objects" to ISM (or whatever storage manager is in use). So, I would suggest that you want to look at recovering the ISM catalog, rather than just the bits out of ISM that are required to recover a single activity of a Level 0 archive with logical logs. Anyway, hope it helps

For operational reasons which I'm not going to bother everyone with, we are being tasked to run overnight level 0 backups using onbar & ISM to disk which will then be picked up at a later, arbitrarily decided, time by a corporate storage management system. So it is vital that I can report with certainty that the onbar backup that ran at 8pm last night consists of a given list of files. As far as I can see - and maybe I'm missing something fundamental here - there is nothing created by ISM that says which files were created by a given backup request. ism_show -volume <name> just lists the files on a volume, not which backup session created them. I suppose I'm just going to create a new volume for each backup and then ringfence it.

On 18/08/2010 13:56, Malc wrote: > For operational reasons which I'm not going to bother everyone with, > we are being tasked to run overnight level 0 backups using onbar& ISM > to disk which will then be picked up at a later, arbitrarily decided, > time by a corporate storage management system. > So it is vital that I can report with certainty that the onbar backup > that ran at 8pm last night consists of a given list of files. As far > as I can see - and maybe I'm missing something fundamental here - > there is nothing created by ISM that says which files were created by > a given backup request. > ism_show -volume<name> just lists the files on a volume, not which > backup session created them. > > I suppose I'm just going to create a new volume for each backup and > then ringfence it. > > Well have a look at : nsrinfo -n informix localhost which may give you something close to what you want (excluding bootstrap info) I suggested googling nsrinfo and have a look at the full man page.