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]
