Informix and Commvault

IDS v10.00.UC8 Commvault v8.0 Solaris 10 We just changed storage managers, much to my dismay, from Netbackup to Commvault. Our backups and restores run fine when initiated from the GUI. When I try to run onbar backups/restores from the Unix cmd line however it fails. I figured out I had to set the CvClientName to the name of the Informix Server I wanted to back up and the CvInstanceName variable to the pre-configured instance name, which in our case is Instance001. To make matters worse I cannot locate any log files on the Unix box and the network admin told me that the failed backups did not write anything to the logs that he manages from the GUI. The error I get is not very helpful either: From bar_act.log: 2009-10-27 09:42:04 2374 2372 /opt/informix/bin/onbar_d complete, returning 149 (0x95) 2009-10-27 09:43:34 2706 2704 /opt/informix/bin/onbar_d -b -L 0 2009-10-27 09:43:35 2706 2704 Working with cvsm as generic storage manager. 2009-10-27 09:43:36 2706 2704 Archive started on [list of dbspaces here -edited for this post] (Requested Level 0). 2009-10-27 09:43:37 2706 2704 Begin level 0 backup rootdbs. 2009-10-27 09:43:37 2706 2704 Successfully connected to Storage Manager. 2009-10-27 09:43:37 2706 2704 XBSA Error: (BSACreateObject) A system error occurred. Aborting XBSA session. From the bar_debug.log: 2009-10-27 09:43:37 2706 2704 BSACreateObject: INFORMIX informix /testfmsS /testfmsS/rootdbs/0 0 0 0 0 0 0 2009-10-27 09:43:37 2706 2704 BSACreateObject: copytype copyid restoreOrder size resource type status desc objectInfo 2009-10-27 09:43:37 2706 2704 BSACreateObject: 3 0 0 0 0 0 10409984 R 4 1 2009-10-27 09:43:37 2706 2704 BSACreateObject: return 3 (0x03) 2009-10-27 09:43:37 2706 2704 do_xbsa_error: enter 2009-10-27 09:43:37 2706 2704 do_xbsa_error: input the_error 3 function BSACreateObject 2009-10-27 09:43:37 2706 2704 do_xbsa_error: return 138 (0x8a) The 138 error: 138 An XBSA error occurred. Verify that you are using the correct XBSA for the storage manager. Also check the bar_act.log for XBSA error messages. For information, consult your storage-manager manual. Anyone out there using Commvault who can lend a hand here? Yeah yeah, I am consulting my Commvault manual also... MM

You wrote: "IDS v10.00.UC8 Commvault v8.0 Solaris 10 We just changed storage managers, much to my dismay, from Netbackup to Commvault. Our backups and restores run fine when initiated from the GUI. When I try to run onbar backups/restores from the Unix cmd line however it fails. I figured out I had to set the CvClientName to the name of the Informix Server I wanted to back up and the CvInstanceName variable to the pre-configured instance name, which in our case is Instance001. To make matters worse I cannot locate any log files on the Unix box and the network admin told me that the failed backups did not write anything to the logs that he manages from the GUI. The error I get is not very helpful either: " Take a look at your ALARMPROGRAM to see if the correct variables are being exported. The job needs to exist in the backup software.

Thanks for the response Ralph, I am not clear as to what role the ALARMPROGRAM plays here. Our alarm program is a pretty standard one, simply controls how errors are handled - who gets emailed etc. Does Commvault rely upon ALARMPROGRAM? Regarding the job being registered - does the fact that we can run backups of the instance in question from the admin console indicate that we have a job registered for this instance or do I need to register separate jobs for backing up an instance from the command line versus from the admin console? Again - appreciate the help. Mike

Figured out my mistake... I was setting CvClientName=$INFORMIXSERVER when it should have been set to my hostname... all is good now. I am now a Commvault/Informix expert... MM