RE: ISM restore to different machine

Malcolm. I know of this problem because we have it as well. So far we haven't been able to solve it, and were forced to go back to ontape; wich doesn't present any problem. Would you be willing to send me this alternative set you got from IBM tech? I would be most gratefull. Regards, Robert A. Reissaus ------------------------------------------------------------------------ R.A. Reissaus Risdi, Amsterdam, the Netherlands Ibm/Informix Consultants Telefoon: +31(0)20 6331140 : Phone Mobiel : +31(0)6 51185352 : Mobile E-mail : r.a.reissaus@risdi.com Website : www.risdi.com ------------------------------------------------------------------------ -----Oorspronkelijk bericht----- Van: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] Namens mweallans@panacea.co.uk Verzonden: maandag 26 september 2005 15:46 Aan: informix-list@iiug.org Onderwerp: Re: ISM restore to different machine Thanks Andreas, I think I followed all the steps but it is a very convoluted procedure. It also assumes that I have control of the source system. In fact in parallel IBM tech support have provided me with a different set of instructions. That too specifies what I have to do on the source system (8 steps) and what to do on the destination system (31 steps). I am just about to set out on the "Thirty Nine Steps". (Now what does that remind me of?) BTW I also enpountered a problem in that I didn't see anywhere any warnings about running ISM backups as root. But if you don't run ISM backups as root the bootstrap does not get copied. And that presents problems later on. But when I modified the source system to run all ism backups as root the backup times grew from 20 minutes to 11 hours. The reason - PRINTER environment variable. It wasn't set but it still seemed to cause a problem. (Funnier and funnier) regards Malcolm (up to my neck in crocodiles - now which swamp was I in when I started?) Andreas Breitfeld wrote: > Hi, > > please check if you did all steps described in 'IBM Informix Storage > Manager Administrator's Guide' chapter 'Transferring Data with the > Imported Restore'. > > If you get an error like > nsrmm: error, file disk data1 not in media index > > when running the ism_op-mount command on the target machine then run > 'ism_catalog -recreate_from' command for each of your devices befor. > > Andreas > > > On Wednesday 21 September 2005 21:58, malcolm weallans wrote: > > IDS 9.40 on Suse Linux SLES8. > > > > We backup IDS to disk using onbar and ISM. We then backup the whole > > Linux disk using cpio. And we have recovered this configuration to > > the same physical machine in the past. We are now trying to "clone" > > the machine for further development purposes. We restored all of > > the informix directories and the ISM backup directories. We then > > created the appropriate devices for ISM, and mounted them. So far > > so good. We started up ism and asked ism_catalog to find_bootstrap > > on the device. It failed to find a bootstrap. It did manage to > > recover the save set info though. > > > > Does anybody have any idea as to the contents of the bootstrap? > > > > Needless to say that - as usual - the development project haven't > > allowed us much time to do this "delicate" operation. > > > > And BTW - we did have propblems with ism_startup but we solved those > > by unsetting the PRINTER environment variable and by installing the > > c compiler. It's interesting that ism needs those facilities to run > > on Linux. I Live and Learn. > > > > Malcolm > > sending to informix-list > sending to informix-list sending to informix-list

I have finally been successful in getting an ISM restore working to a different machine. It has been a tough haul but we got there in the end. I say we, but to be brutally frank, I got there without any little bit of help from my friends, neither OpenPSL or IBM. I did have some support From Robert Reissaus who has been there before. It's funny but even that kind of support can be of value. The final solution will need some investigation before I can publish but if you get sent the 39 steps from Informix (8 on the source and 31 on the target) the problem is step 19 on the target. I redid this step manually using the nsradmin visual interface and the system came into life. I did have a few device linking errors and shared memory config problems (it is Linux after all) but I have seen those before when trying to use onbar with other storage managers. Please look out in the near future for "The 39 steps". An Informix adventure. regards Malcolm R.A. Reissaus wrote: > Malcolm. > I know of this problem because we have it as well. So far we haven't been > able to solve it, and were forced to go back to ontape; wich doesn't present > any problem. > > Would you be willing to send me this alternative set you got from IBM tech? > I would be most gratefull. > Regards, > Robert A. Reissaus > > ------------------------------------------------------------------------ > R.A. Reissaus > Risdi, Amsterdam, the Netherlands > Ibm/Informix Consultants > Telefoon: +31(0)20 6331140 : Phone > Mobiel : +31(0)6 51185352 : Mobile > E-mail : r.a.reissaus@risdi.com > Website : www.risdi.com > ------------------------------------------------------------------------ > -----Oorspronkelijk bericht----- > Van: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] > Namens mweallans@panacea.co.uk > Verzonden: maandag 26 september 2005 15:46 > Aan: informix-list@iiug.org > Onderwerp: Re: ISM restore to different machine > > > Thanks Andreas, > > I think I followed all the steps but it is a very convoluted procedure. It > also assumes that I have control of the source system. In fact in parallel > IBM tech support have provided me with a different set of instructions. > That too specifies what I have to do on the source system (8 steps) and what > to do on the destination system (31 steps). > > I am just about to set out on the "Thirty Nine Steps". (Now what does that > remind me of?) > > BTW I also enpountered a problem in that I didn't see anywhere any warnings > about running ISM backups as root. But if you don't run ISM backups as root > the bootstrap does not get copied. And that presents problems later on. > But when I modified the source system to run all ism backups as root the > backup times grew from 20 minutes to 11 hours. The reason - PRINTER > environment variable. It wasn't set but it still seemed to cause a problem. > (Funnier and funnier) > > regards > > Malcolm > (up to my neck in crocodiles - now which swamp was I in when I > started?) > > > Andreas Breitfeld wrote: > > Hi, > > > > please check if you did all steps described in 'IBM Informix Storage > > Manager Administrator's Guide' chapter 'Transferring Data with the > > Imported Restore'. > > > > If you get an error like > > nsrmm: error, file disk data1 not in media index > > > > when running the ism_op-mount command on the target machine then run > > 'ism_catalog -recreate_from' command for each of your devices befor. > > > > Andreas > > > > > > On Wednesday 21 September 2005 21:58, malcolm weallans wrote: > > > IDS 9.40 on Suse Linux SLES8. > > > > > > We backup IDS to disk using onbar and ISM. We then backup the whole > > > Linux disk using cpio. And we have recovered this configuration to > > > the same physical machine in the past. We are now trying to "clone" > > > the machine for further development purposes. We restored all of > > > the informix directories and the ISM backup directories. We then > > > created the appropriate devices for ISM, and mounted them. So far > > > so good. We started up ism and asked ism_catalog to find_bootstrap > > > on the device. It failed to find a bootstrap. It did manage to > > > recover the save set info though. > > > > > > Does anybody have any idea as to the contents of the bootstrap? > > > > > > Needless to say that - as usual - the development project haven't > > > allowed us much time to do this "delicate" operation. > > > > > > And BTW - we did have propblems with ism_startup but we solved those > > > by unsetting the PRINTER environment variable and by installing the > > > c compiler. It's interesting that ism needs those facilities to run > > > on Linux. I Live and Learn. > > > > > > Malcolm > > > sending to informix-list > > sending to informix-list > sending to informix-list

We do this on v7 at a customer site. I can let you have a copy of the documention we wrote for it if you like .. Can you send us the "39 Steps" document you refer to below - never heard of it previously: we, like you, had to work it out for ourselves. -- Neil Truby t:01932 724027 Director m:07798 811708 Ardenta Limited e:neil.truby@ardenta.com <mweallans@panacea.co.uk> wrote in message news:1127817724.585331.244440@f14g2000cwb.googlegroups.com... >I have finally been successful in getting an ISM restore working to a > different machine. It has been a tough haul but we got there in the > end. I say we, but to be brutally frank, I got there without any > little bit of help from my friends, neither OpenPSL or IBM. > > I did have some support From Robert Reissaus who has been there before. > It's funny but even that kind of support can be of value. > > The final solution will need some investigation before I can publish > but if you get sent the 39 steps from Informix (8 on the source and 31 > on the target) the problem is step 19 on the target. I redid this step > manually using the nsradmin visual interface and the system came into > life. I did have a few device linking errors and shared memory config > problems (it is Linux after all) but I have seen those before when > trying to use onbar with other storage managers. > > Please look out in the near future for "The 39 steps". An Informix > adventure. > > regards > > Malcolm > R.A. Reissaus wrote: >> Malcolm. >> I know of this problem because we have it as well. So far we haven't been >> able to solve it, and were forced to go back to ontape; wich doesn't >> present >> any problem. >> >> Would you be willing to send me this alternative set you got from IBM >> tech? >> I would be most gratefull. >> Regards, >> Robert A. Reissaus >> >> ------------------------------------------------------------------------ >> R.A. Reissaus >> Risdi, Amsterdam, the Netherlands >> Ibm/Informix Consultants >> Telefoon: +31(0)20 6331140 : Phone >> Mobiel : +31(0)6 51185352 : Mobile >> E-mail : r.a.reissaus@risdi.com >> Website : www.risdi.com >> ------------------------------------------------------------------------ >> -----Oorspronkelijk bericht----- >> Van: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] >> Namens mweallans@panacea.co.uk >> Verzonden: maandag 26 september 2005 15:46 >> Aan: informix-list@iiug.org >> Onderwerp: Re: ISM restore to different machine >> >> >> Thanks Andreas, >> >> I think I followed all the steps but it is a very convoluted procedure. >> It >> also assumes that I have control of the source system. In fact in >> parallel >> IBM tech support have provided me with a different set of instructions. >> That too specifies what I have to do on the source system (8 steps) and >> what >> to do on the destination system (31 steps). >> >> I am just about to set out on the "Thirty Nine Steps". (Now what does >> that >> remind me of?) >> >> BTW I also enpountered a problem in that I didn't see anywhere any >> warnings >> about running ISM backups as root. But if you don't run ISM backups as >> root >> the bootstrap does not get copied. And that presents problems later on. >> But when I modified the source system to run all ism backups as root the >> backup times grew from 20 minutes to 11 hours. The reason - PRINTER >> environment variable. It wasn't set but it still seemed to cause a >> problem. >> (Funnier and funnier) >> >> regards >> >> Malcolm >> (up to my neck in crocodiles - now which swamp was I in when I >> started?) >> >> >> Andreas Breitfeld wrote: >> > Hi, >> > >> > please check if you did all steps described in 'IBM Informix Storage >> > Manager Administrator's Guide' chapter 'Transferring Data with the >> > Imported Restore'. >> > >> > If you get an error like >> > nsrmm: error, file disk data1 not in media index >> > >> > when running the ism_op-mount command on the target machine then run >> > 'ism_catalog -recreate_from' command for each of your devices befor. >> > >> > Andreas >> > >> > >> > On Wednesday 21 September 2005 21:58, malcolm weallans wrote: >> > > IDS 9.40 on Suse Linux SLES8. >> > > >> > > We backup IDS to disk using onbar and ISM. We then backup the whole >> > > Linux disk using cpio. And we have recovered this configuration to >> > > the same physical machine in the past. We are now trying to "clone" >> > > the machine for further development purposes. We restored all of >> > > the informix directories and the ISM backup directories. We then >> > > created the appropriate devices for ISM, and mounted them. So far >> > > so good. We started up ism and asked ism_catalog to find_bootstrap >> > > on the device. It failed to find a bootstrap. It did manage to >> > > recover the save set info though. >> > > >> > > Does anybody have any idea as to the contents of the bootstrap? >> > > >> > > Needless to say that - as usual - the development project haven't >> > > allowed us much time to do this "delicate" operation. >> > > >> > > And BTW - we did have propblems with ism_startup but we solved those >> > > by unsetting the PRINTER environment variable and by installing the >> > > c compiler. It's interesting that ism needs those facilities to run >> > > on Linux. I Live and Learn. >> > > >> > > Malcolm >> > > sending to informix-list >> > sending to informix-list >> sending to informix-list >

As many people seem to want this information here goes:- This is the 39 steps as sent to me by IBM Tech Support. Be warned that target step 19 is suspect. I had to do it manually using nsradmin. ###### IBM Comments I have found this article which may help.. Steps used during imported restores using ISM Source system Assumptions: Using the following disk devices for back up /archive/arc1 /archive/logs1 Source system = eagles Target system = ts19208 Source SEVERNAME=eagles_tcp1 Source SERVERNUM = 108 Source ONCONFIG=onconfig.eagles_tcp1 1. On source system(eagles) take Level 0 backup. 2. Run onstat -d. Use this output as the guide to setup the proper devices on the target system. 3. run ism_show -admin Current admin for ISM are administrator: root@eagles, informix; If informix is not listed then add it. 4. Run ism_catalog -create_bootstrap -pool ISMDiskData 5. Copy $INFORMIXDIR/etc/ixbar.108, oncfg_eagles.108, onconfig.eagles_tcp1, and sqlhosts to /archive directory 6. cd /archive 7. tar cvf archive.tar * This will archive the files needed to restore on target system. 8. Compress and ftp binary, archive.tar.Z to target system. ------------------------------------------------------------------------------ TARGET This is assuming you are creating a brand new instance on the target machine and no other engines are running. Assumptions: Using the following disk devices for back up /opt/eagles/arch_eagles /opt/eagles/logs_eagles Source system = eagles Target system = ts19208 Target SERVERNAME ko_tcp1 Target SERVERNUM = 110 Target ONCONFIG=onconfig.ko_tcp Working directory will by /opt --------------------------------- 1. Login as root cd /opt mkdir archive chmod 777 archive 2. Set targets's environment for informix. INFORMIXDIR, INFORMIXSERVER,ONCONFIG,PATH 3. If ISM is running run ism_shutown %ism_shutdown 4. %cd $INFORMIXDIR/bin %cp ism_startup ism_startup.orig %vi ism_startup a. locate the following line in the startuup script: hostname=$(hostaname) b. Add the following line IMMEDIATELY after that line and save hostname="source_hostname" 5. Run ism_startup -init 6. %cd /opt/archive 8. Create file call nsr.client and type create type: NSR client; name: source_hostname; remote access: Administrator @target_hostname, informix@target_hostname example: create type: NSR client; name: eagles; remote access: Administrator@ts19208, inf ormix@ts19208 *** must be all one line 9. Run nsradmin -s target_hostname -i nsr.client ex: nsradmin -s ts19208 -i nsr.client 10.cd /opt/archive Uncompress and extract archive.tar into a directory ex: tar xvf archive.tar 11.Run ism_add -device /opt/archive/arch1 -type file ism_add -device /opt/archive/logs1 -type file 12.ism_catalog -find_bootstrap device_name ex: ism_catalog -find_bootstrap /opt/archive/arch1 Get SSID number for all bootstap save sets on the volume 13. ism_catalog -recover Wait util the following message displays *** THIS MAY TAKE AWHILE. BE PATIENT. nsrindexasm: Didn't find earlier versions to recover! Warning: The on-line index for hostname was NOT fully recovered.... 14. ism_shutdown 15 cd $INFORMIXDIR/ism rm -rf res mv res.R res 16. ism_startup 17. ism_show devices Remove all devices listed from Source system ism_rm -device 18. Re-Add your devices for target system(ts19208) ism_add -device /opt/archive/arch1 -type file ism_add -device /opt/archive/logs1 -type file 19.Create file nsr_client2 type the following print type: NSR client; name: source_hostname update remote access: informix@target_hostname, root@target_hostname,informix example: print type: NSR client; name: eagles update remote access: informix@ts19208, root@ts19208, informix 20. run nsradmin -s target_hostname -i nsr_client2 ex: nsradmin -s ts19208 -i nsr_client2 21. Set the following Environment INFORMIXDIR,INFORMIXSERVER,PATH,ONCONFIG ISM_CLIENT=Source_server ISM_SERVER=Target_server ISM_DATA_VOLUME_POOL=ISMDiskData ISM_LOG_VOLUME_POOL=ISMDiskLogs export ISM_CLIENT ISM_SERVER ISM_DATA_VOLUME_POOL ISM_LOG_VOLUME_POOL example: INFORMIXSERVER=ko_tcp1 INFORMIXDIR=/opt/informix PATH=/opt/informix/bin:.:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin ONCONFIG=onconfig.ko_tcp SM_CLIENT=eagles ISM_SERVER=ts19208 ISM_DATA_VOLUME_POOL=ISMDiskData ISM_LOG_VOLUME_POOL=ISMDiskLogs export ISM_CLIENT ISM_SERVER ISM_DATA_VOLUME_POOL ISM_LOG_VOLUME_POOL 22. Create Symbolic links that match source system. Device names for chunks must match source system ln -s existing_device /path/match/source ex: ln -s /space/import/rootdbs /usr2/chunks/rootdbs or ln -s /dev/rdsk/c1t2d0s3 /usr2/chunks/rootdbs 23 run ism_catalog -recreate_from /opt/archive/arch_eagles 24 run ism_catalog -recreate_from /opt/archive/logs_eagles 25 run nsrim -v 26. Do the following on the "data" device ism_show -devices ism_op -umount /opt/archive/arch_eagles ism_show -volumes ism_config -volume volume_name -only_restore no ism_op -mount /opt/archive/arch_eagles ism_show -devices (should be write enabled) 27. cd /opt/archive (Directory where you uncompressed and untared files from source) * cp oncfg_source_dbservername.servnum to oncfg_target_dbservername.servernum example oncfg_eagles_tcp1.108 $INFORMIXDIR/etc/oncfg_ko_tcp1.110 * cp ixbar.source_serv_num to ixbar.target_serv_num example ixbar.108 to $INFORMIXDIR/etc/ixbar.110 * cp onconfig.source to onconfig.target cp onconfig.eagles_tcp1 $INFORMIXDIR/etc/onconfig.ko_tcp * cp sqlhost_source to sqlhosts_target cp sqlhosts $INFORMIXDIR/etc/sqlhosts 28. Edit the targets onconfig and sqlhosts. Change the DBSERVERNAME and number to match targets names. 29. Add source_hostname to /etc/hosts 30. Login as informix Set enviroment see step 21 Run onbar -r -p Run onbar -r -l Run onmode -m. 31. Copy orginal $INFORMIXDIR/bin/ism_startup back. Technical Analyst IBM Data Management Solutions ###### End and this script will save having problems with the PRINTER environment variable UNSETTING THE PRINTER ENV VARIABLE Document Number: 825 Last reviewed: 03/11/2002 -------------------------------------------------------------------------------- Summary: Unsetting the PRINTER env. variable has no effect on the ism_catalog -create_bootstrap command even after stopping and resta