Onbar Pools and File System with ISM

Hi Folks, I got a IDS 9.40 UC5 on Red Hat Enterpirse 3. I´m trying to implement the onbar archive utility and wish that it could be make to disk. I already did it with ontape utility, but is so easy. The ISM configuration is my problem. I couldn´t see clearly what is each parameter with some line commands. 1. What is really a disk pool and what is the device that I want to write my archive. 2. I made a "cut and paste" from google page of this command # ism_op -label $SM_DISKDEV1 -pool ISMDiskData -volume ISMData and it returns me nsrmm: Invalid pool name `ISMDiskData' I don´t even know what is a valid pool name. Where do I have to look up to see what is right to do ? Last question. Which value do I have to use to set ISMData and ISMLogs onconfig parameters? Thanks a lot, André Luiz Informix DBA _________________________________________________________________ O Windows Live Spaces está aqui! Descubra como é fácil criar seu espaço na Web e sua rede amigos. http://spaces.live.com/signup.aspx

Andre, You could start by checking out the following online manuals. The firs= t link is to the IBM Informix Storage Manager Guide and the second is to the IBM Informi= x Backup and Restore Guide, both of which will be helpful to you in answering yo= ur questions. I believe the page you are referring to is 1-12 in the ISM Guide, where= we discuss the basic setup for using ISM with Onbar. The value for the pool has t= o already exist in your $ONCONFIG file using the ISM_DATA_POOL and ISM_LOG_POOL parameters for you to be able to use it with the ism_op command. If yo= u review both documents, I think that your questions will be answered. http://publib.boulder.ibm.com/epubs/pdf/ct1swna.pdf http://publib.boulder.ibm.com/epubs/pdf/ct1slna.pdf = "Andr=E9 Luiz = Rufino" = <andre_rufino@msn = To .com> ids@iiug.org = Sent by: = cc ids-bounces@iiug. = org Subj= ect Onbar Pools and File System with= ISM [8043] = 12/20/2006 01:02 = PM = = = Please respond to = ids@iiug.org = = = Hi Folks, I got a IDS 9.40 UC5 on Red Hat Enterpirse 3. I=B4m trying to implement= the onbar archive utility and wish that it could be make to disk. I already= did it with ontape utility, but is so easy. The ISM configuration is my problem. I couldn=B4t see clearly what is e= ach parameter with some line commands. 1. What is really a disk pool and what is the device that I want to wri= te my archive. 2. I made a "cut and paste" from google page of this command # ism_op -label $SM_DISKDEV1 -pool ISMDiskData -volume ISMData and it returns me nsrmm: Invalid pool name `ISMDiskData' I don=B4t even know what is a valid pool name. Where do I have to look = up to see what is right to do ? Last question. Which value do I have to use to set ISMData and ISMLogs onconfig parameters? Thanks a lot, Andr=E9 Luiz Informix DBA _________________________________________________________________ O Windows Live Spaces est=E1 aqui! Descubra como =E9 f=E1cil criar seu = espa=E7o na Web e sua rede amigos. http://spaces.live.com/signup.aspx ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. =

1. What is really a disk pool and what is the device that I want to write my archive. It can be a bit confusing Andre, but I'll have a go for you if you can bear with me. Onbar talks to an xbsa compliant storage manager; ISM is such a storage manager with a limit of 4 connected devices at any one time. Pools are organisational units managed by the storage manager. Onbar backs up dbspaces, sbspaces, and blobspaces to physical media (volumes) mounted on a device. These volumes would normally belong to the pool defined in the $ONCONFIG file ISM_DATA_POOL parameter. Logical Logs are backed up to volumes (media) in the pool defined in the ISM_LOG_POOL. Out of the box, the ONCONFIG file designates ISMData and ISMLogs to these parameters. The ISMData and ISMLogs pools are defined in the bowels if ISM when you first run the ism_startup -init. It is essential that ism_startup -init be run (as root) on every host where you want to use ISM. In addition, ISM creates the ISMDiskData and ISMDiskLogs Pools during this initialization. The ISMData and ISMLog pools are used to manage media mounted on Non File Type Devices, eg: a tape drive like /dev/rmt0. The ISMDiskData and ISMDiskLogs pools are used to manage File type devices (directories). I know I'm not talking disk pools yet, but hang in and I'll get there. If you only had a single 4mm DAT tape drive to backup your database server you would need to first add the tape device with:- ism_add -device /dev/rmt0 -type 4mm Before ISM can store data or logical logs on a tape the tape needs to be registered as a volume with ISM. So, you would get the tapes you want to use to store your backup on (you may need 2 or more depending on the amount of Data), and label them one at a time using:- ism_op -label -volume volumeName -pool ISMData and or ISMLogs. This will write a header to each tape. This header is used to identify what the volume name of the tape is when it is mounted on the tape device for backup and restore operations. The volume is also registered in the bowels of ISM along with the pool to which that volume belongs and other info. So now you come along and do an onbar -b -L 0 for the DBServer to be backed up. In the ONCONFIG file the ISM_DATA_POOL and ISM_LOG_POOL would be set to ISMData and ISMLogs respectively. You can then use ism_watch to monitor activity and any messages that ism needs to communicate to the backup operator, you presumably. For example, if when you ran onbar there was not a labelled tape (volume) mounted in the tape drive; ism_watch would prompt you to mount a tape registered with ISM in the ISMData pool. Onbar will wait for ISM to tell it that it is ready to start storing the backup data/logs. So, the idea is that you pre-register volumes in pools before you use them. This registration can be while the backup is going on, but usually you would prepare your media to fit in with you backup schedule. Now, if you want your backups to be stored on a file system(s) ISM needs to use a different driver, a file driver if you like as opposed to a tape (non file) driver. However the concept of media management is the same as with tapes. You need to create a directory which will serve as both the device and the volume. So you need to make 1 or more directories and add them as devices (up to 4 at a time) with: Ism_add -device /pathToDirectory -type file To turn the directory into a volume, you need to label it with:- Ism_op -label volumeName -pool ISMDiskData or ISMDiskLogs This creates a couple of files (.nsr and volume) in the directory which, like with the tape media, identify the volume. The volume and its pool are Now that the directory (device) is labelled (a registered volume), you can mount it with:- Ism_op -mount /pathToDirectory Note that the volume name is not does not have to be the same as the directory(basename of device), but it might suit you to have it that way. Must go. Hope that make sense and is of some help to you. *************************************************************** This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of the Department of Lands. This email message has been swept by MIMEsweeper for the presence of computer viruses. ***************************************************************