Informix Storage Manager ISM

Hi everybody I'm playing with ism and onbar, in order to establishing an onbar policy of backups. Im very confused with some ism topics. I defined a directory on disk (apart from the database disks box) where I direct data backups and another directory for logs backups. ism_add /home0/cintasbar/cinta0 -type file ism_op -label /home0/cintasbar/cinta0 -pool ISMDiskData -volume ISMData ism_op mount /home0/cintasbar/cinta0 First issue: on first test, volume was full at about 8 Gigabytes (the filesystem is about 60 Gigabytes). Then I initialized ISM again, configure volumes, and test... onbar was OK and stored all of the dbspaces on level 0, 1 and 2. no problem with space. But... after I cleaned the volume, unmount, label again, and mount, once again I have the 8 Gigabytes limit. The filesystem is plenty of space. Second issue: I tried to make a clone. I have read the ism manual and another documents about ism and onbar but, for some reason (may be my brain ;-) I'am unable to understand the ism_clone command. I had played with variations of ism_op -label and ism_clone -parameters, but I can't make a successfull clone at this time. I try to make a clone on disk in my test, but the final intention is clone to tape. Again, I will appreciate your comments and experience about the topics. Greatings. --Nestor Gomez

On 2/10/06, Néstor Góme.... <nestorgm@prodigy.net.mx> wrote: > I'm playing with ism and onbar, in order to establishing an onbar policy > of backups. Im very confused with some ism topics. Which version of IDS? Which platform? > I defined a directory on disk (apart from the database disks box) where > I direct data backups and another directory for logs backups. > > ism_add /home0/cintasbar/cinta0 -type file > ism_op -label /home0/cintasbar/cinta0 -pool ISMDiskData -volume ISMData > ism_op mount /home0/cintasbar/cinta0 > > First issue: on first test, volume was full at about 8 Gigabytes (the > filesystem is about 60 Gigabytes). Then I initialized ISM again, > configure volumes, and test... onbar was OK and stored all of the > dbspaces on level 0, 1 and 2. no problem with space. But... after I > cleaned the volume, unmount, label again, and mount, once again I have > the 8 Gigabytes limit. The filesystem is plenty of space. > > Second issue: I tried to make a clone. I have read the ism manual and > another documents about ism and onbar but, for some reason (may be my > brain ;-) I'am unable to understand the ism_clone command. I had played > with variations of ism_op -label and ism_clone -parameters, but I can't > make a successfull clone at this time. > I try to make a clone on disk in my test, but the final intention is > clone to tape. > > Again, I will appreciate your comments and experience about the topics. Are you hitting a 2 GB limit - 4 times? This is why it could be very important to know about which version of IDS you're working with. If you're on a 64-bit platform, or on 9.40 or later, it should not be the trouble. If you're on a 32-bit platform and a version earlier than 9.40, it could easily be a problem in this area. ** ALWAYS include basic version and platform information when you ask questions. (Not just you - everyone!) -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/

IDS 9.40 FC2 Solaris 9 Veritas VM and Solaris VM Suncluster 3.0 Plataform is working on 64 bits. Indeed, as I wrote, I was able to ma= ke a successful backup at levels 0, 1 and 2 just after reinstalling-reinitializing iSM. The problem backs up when I relabel = the devices to clean up and start again. I should be making something wrong or not doing something. I don't th= ing will be normal reinitializing all of the ISM service every time I restart a backup cicle. By the way, I forgot to ask, on the ism_clone topic, my question: = =C2=BFwhat does it mean each parameter -volume and -pool? source volume, destination volume, destinations pool, source pool, ...? May be somebody could tell me about readings on the Internet about on= bar and ism. What I have read lack of real situations and examples. Have a nice weekend. -Nestor. El s=C3=A1b, 11-02-2006 a las 02:21 -0500, Jonathan Le.... escribi= =C3=B3: > On 2/10/06, Nstor Gme.... <nestorgm@prodigy.net.mx> wrote:=20 > > I'm playing with ism and onbar, in order to establishing an onbar= policy=20 > > of backups. Im very confused with some ism topics.=20 >=20 > Which version of IDS? Which platform?=20 >=20 > > I defined a directory on disk (apart from the database disks box)= where=20 > > I direct data backups and another directory for logs backups.= =20 > >=20 > > ism_add /home0/cintasbar/cinta0 -type file=20 > > ism_op -label /home0/cintasbar/cinta0 -pool ISMDiskData -volume I= SMData=20 > > ism_op mount /home0/cintasbar/cinta0=20 > >=20 > > First issue: on first test, volume was full at about 8 Gigabytes = (the=20 > > filesystem is about 60 Gigabytes). Then I initialized ISM again,= =20 > > configure volumes, and test... onbar was OK and stored all of the= =20 > > dbspaces on level 0, 1 and 2. no problem with space. But... after= I=20 > > cleaned the volume, unmount, label again, and mount, once again I= have=20 > > the 8 Gigabytes limit. The filesystem is plenty of space.=20 > >=20 > > Second issue: I tried to make a clone. I have read the ism manual= and=20 > > another documents about ism and onbar but, for some reason (may b= e my=20 > > brain ;-) I'am unable to understand the ism_clone command. I had = played=20 > > with variations of ism_op -label and ism_clone -parameters, but I= can't=20 > > make a successfull clone at this time.=20 > > I try to make a clone on disk in my test, but the final intention= is=20 > > clone to tape.=20 > >=20 > > Again, I will appreciate your comments and experience about the t= opics.=20 >=20 > Are you hitting a 2 GB limit - 4 times? This is why it could be ver= y=20 > important to know about which version of IDS you're working with. I= f=20 > you're on a 64-bit platform, or on 9.40 or later, it should not be = the=20 > trouble. If you're on a 32-bit platform and a version earlier than= =20 > 9.40, it could easily be a problem in this area.=20 >=20 > ** ALWAYS include basic version and platform information when you a= sk=20 > questions.=20 >=20 > (Not just you - everyone!)=20 >=20

Hi, regarding the capacity problem you may want to look at the configuration of the "disk device". For that you have to run the command "nsradmin -c" as user root. You first have to enable the hidden options and parameters. You do this under "Options" by a toggle on the "Dispaly options" value of "Hidden". Then go back to the main menu and choose "Select" and then choose "NSR device". Use "Next" until you get to the device in question. There is parameter "volume default capacity:". On my system this is empty. You may try setting it to something suitable on your system. See the help (CTRL-H) for the format of the value. I have not tried this as I have currently no > 8 GB space for this and no such large data to do a test. But maybe this can solve the problem. Cloning I've not done in a longer time. But it may be a problem due to your setup, media definition, etc. (Like that it may not make much sense to clone something to the same disk ...). Maybe first try with small data (for speed) but clone to a real tape (rather than another file on the same disk) ? Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Information Management ids-bounces@iiug.org wrote on 11.02.2006 07:02:34: > > Hi everybody > > I'm playing with ism and onbar, in order to establishing an onbar policy > of backups. Im very confused with some ism topics. > > I defined a directory on disk (apart from the database disks box) where > I direct data backups and another directory for logs backups. > > ism_add /home0/cintasbar/cinta0 -type file > ism_op -label /home0/cintasbar/cinta0 -pool ISMDiskData -volume ISMData > ism_op mount /home0/cintasbar/cinta0 > > First issue: on first test, volume was full at about 8 Gigabytes (the > filesystem is about 60 Gigabytes). Then I initialized ISM again, > configure volumes, and test... onbar was OK and stored all of the > dbspaces on level 0, 1 and 2. no problem with space. But... after I > cleaned the volume, unmount, label again, and mount, once again I have > the 8 Gigabytes limit. The filesystem is plenty of space. > > Second issue: I tried to make a clone. I have read the ism manual and > another documents about ism and onbar but, for some reason (may be my > brain ;-) I'am unable to understand the ism_clone command. I had played > with variations of ism_op -label and ism_clone -parameters, but I can't > make a successfull clone at this time. > I try to make a clone on disk in my test, but the final intention is > clone to tape. > > Again, I will appreciate your comments and experience about the topics. > > Greatings. > > --Nestor Gomez > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >