Marc-Philip,

Thanks for your reply.  I'm currently using MaxDB 7.5.00.32, and the
dbmevtdisp program appears to work differently than what the online
documentation suggests.  That documentation discusses the commands add,
delete, list, start, state, stop, and version, but the syntax for the
7.5 version of dbmevtdisp looks like this:

-> MaxDB Eventing, Dispatcher, Version 7.5.0
-> Copyright (c) 1998 - 2005 by SAP AG
-> 
-> Version   7.5.0    Build 032-123-111-699
-> 
-> usage: ./dbmevtdisp [<options>]
->   <options>:
->     -n        node      (name of servernode), optional
->     -d        dbname    (name of datbase)
->     -u        user,pwd  (user for authorization; prompt if empty),
optional
->     -U        user_key  (from XUSER), optional
->     -lf       logfile   (log file), optional
->     -cf       cfgfile   (configuration file), optional
->     -q        quiet     (no output to stdout), optional
->     -r        reconnect (try reconnect after loss of connection),
optional 

This program seems to want to use, by default, the file
$DBROOT/env/dbmevtdisp.cfg whose syntax is a little confusing.  Can you
tell me anything about this 7.5 approach to using events?

Thanks,
~Fred

P.S.: I am using Data Protector 5.5 which has a certified "SAP DB
Integration" which does ultimately call the DBM command archive_stage.
Using this technique, our Backup History contains both the original file
reference (such as /sapdb/backup_log_area/log.048) as well as the
reference to the pipe device that DP uses (such as
/var/opt/omni/tmp/TST.BACKDP-Archive).


-----Original Message-----
From: Werner, Marc-Philip [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, December 20, 2005 5:48 AM
To: maxdb@lists.mysql.com
Cc: Claypool, Fred
Subject: RE: Any way to trigger a backup in conjunction with AutoLog?

Hi Fred,

> The only problem then is that those files sit there until our 
> regularly
> scheduled external backup tool (HP's Data Protector) comes to 
> move them
> onto tape. Is there any triggering or event mechanism built 
> in to MaxDB
> that I could configure that would notify the backup tool to start
> working when MaxDB calls it (as opposed to waiting until the next
> regularly scheduled backup)? 

Yes, there is something you can use as of version 7.6. The database
kernel sends so called events. Please check the documentation at
http://dev.mysql.com/doc/maxdb/en/default.htm -> Tools -> Utilities ->
Event Dispatcher.

The events that you are interested in are the AUTOSAVE events which have
the VALUE1 field set to 1. You must configure an Event Dispatcher that
recognizes this event and calls the Data Protector client as soon as it
comes. The documentation covering this topic contains two examples. If
you can't manage to get the Event Dispatcher running, please post your
questions on the MaxDB mailing list.

As you use Data Protector, did you ever consider using their
implementation of Backint for MaxDB (or Backint for Oracle, which we can
also use)? You'd have to buy that from them. If you used one of them,
the Dispatcher could call the DBM Command archive_stage instead of the
Data Protector client. You'd have each file that was backed up in the
backup history!

> 
> Thanks. 
> ~Fred Claypool, Jr.

Regards,
Marc-Philip


--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to