pajama

iiug.org에서 onbar에서 사용되는 XBSA API에 대한 설명을 발췌하였습니다. 

onbar 명령으로 백업을 수행하면 onbar 프로세스는 백업 솔루션의 프로세스와 통신하게 되는데, 그 과정에서 아래의 API들을 사용하게 됩니다.

onbar로 백업을 하고 계신 곳에서는 백업 로그에서 아래의 일부 API 이름을 보셨을 겁니다.

Onbar can communicate with multiple storage managers. The reason we can pull this off is because recently a standard api has been developed so that different vendors can communicate with each other. This standard/language is know as XBSA. Below are the XBSA calls that onbar uses in order to backup and restore dbspaces to/from the online engine. The functions below are the complete set of XBSA call. It is mearly the calls that onbar uses.

• BSABeginTxn()- starts an XBSA API transaction.
• BSACreateObject()- Creates an XBSA object. This basically tells that storage manager to make room for a new backup. The storage manager passes back the copyid (inside the objectdescriptor) that is the unique identifier that onbar uses when it need to get that back/object.
• BSAEndData()-Tells the storage manager that there is no more data to send. (we are finished sending data associated with that particular object)
• BSAEndTxn()- Tell the storage manager that we are finished with a backup transaction.
• BSAGetData()- This function returns a single buffer of data from that storage manager. We pass it the copyid (in the object descriptor) and the storage manager is responsible for finding the requested data.
• BSAGetObject()- Called to gather information about a particular storage manager object (ie, date created , size, owner etc).
• BSAInit()- connects to the storage manager and starts a session. This function will return a 'handle' that is a unique identifier associated to that session.
• BSAQueryApiVersion()- Called to validate which version of the XBSA libraries onbar is talking to.
• BSASendData()- Sends a buffer full of data to the storage manager.
• BSATerminate()- Terminates a session with the storage manager. It also frees up and resources that were allocated in the BSAinit call.

Below is a simplistic diagram on how an XBSA application goes. onbar (which is an XBSA applicalion in it self) follows this flow chart as well when creating/restoring archives. onbar will loop calling BSASendData (and BSAGetDATA) until the is no more data to process.

출처 : http://www.iiug.org/onbar/xbsa.html

onbar physical restore (onbar -r -p) 또는 onbar logical restore중 out of virtual shared memory 오류가 발생하는 경우가 있습니다.

여러 원인이 있겠습니다만 저의 경우는 Virtual segment 크기를 큰 값으로 재설정한 후 재시작했었습니다.

그러나 다시 생각해보면 oninit 프로세스를 재시작(oninit -r)해서 된것이지 Virtual segment 크기가 때문이 아닐 수도 있겠네요.

SunOS 5.10, 인포믹스 11.50, Netvault 백업 솔루션 환경이었고

커널파라미터까지는 확인하지 못했는데, 커널 파라미터 값이 문제가 될가능성이 높습니다.

ENOSPC error while allocating shared memory

http://www-01.ibm.com/support/docview.wss?uid=swg21614434

Running oninit but error shmget: [EEXIST][17]: key 52604801: shared memory already exists

http://www-01.ibm.com/support/docview.wss?uid=swg21430996

Problem(Abstract)

You observe messages in your online.log file referencing alarmprogram.sh and with return code 126 or 127. What do they mean?

Symptom

Cause

Resolving the problem

Restriction: ON-Bar does not use the TAPEDEV, TAPEBLK, TAPESIZE, LTAPEBLK, and LTAPESIZE configuration parameters.

To start ISM on UNIX for the first time, issue the ism_startup -init command. The following shell script is an example of a simple setup for making on–Bar storage-space and logical-log backups to disk files:

#!/usr/bin/ksh

# setup for ISM storage manager

INFORMIXDIR=/data/informix

export INFORMIXDIR

echo "ISM setup begins"

# the user must edit these two lines to select

# appropriate disk locations for storage manager use.

SM_DISKDEV1=/backups/dbspaces

SM_DISKDEV2=/backups/logfiles

export SM_DISKDEV1

export SM_DISKDEV2

# start ISM server

echo "initalize ISM server, must be done as root"

$INFORMIXDIR/bin/ism_startup -init

$INFORMIXDIR/bin/ism_add -admin informix@server (server=hostname)

Important: To make informix the ISM user and thereby ensure informix has access to conduct ISM operations during daily routines, you must run the following command after any ism_startup -init or ISM installation:

# create some devices and media

# the ISM user, defined in ism_add -admin, can do these tasks

echo "create and mount ISM devices and pools"

ism_add -device $SM_DISKDEV1 -type file

ism_add -device $SM_DISKDEV2 -type file

ism_op -label $SM_DISKDEV1 -pool ISMDiskData -volume ISMData

ism_op -label $SM_DISKDEV2 -pool ISMDiskLogs -volume ISMLogs

ism_op -mount $SM_DISKDEV1

ism_op -mount $SM_DISKDEV2

echo "end of ISM setup"