(This was also posted to the MaxDB Forum on forums.mysql.com.) Hi there.
Quick question for you. For over a year now, we've had Auto Logging enabled on all of our MaxDB databases. (We're currently running 7.5.00.31 on HP-UX & Linux.) This works great... when the log space fills up, MaxDB automatically dumps this log data into the file system in "version files" I think they are called. In our case, this log data creates files of the form /sapdb/backup_log_area/log.xyz where xyz is a unique, sequential number. 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)? Thanks. ~Fred Claypool, Jr.
