Hello Alexei, >1) Are there alternatives to load log backups on >standby instance other then do >recover_start-recover_replace in one utility session?
End your log recovery with a recover_cancel (DBM Server should do that by default, when ending with a still open utility session.) And restore the next needed log backup with recover_start. You can determine the next needed log backup with the dbmcli command db_restartinfo on the standby database and a look into the backup history of your source database. >2) Can I extend one utility-backup-recover session >over multiple dbmcli calls? No yet. Most probably in the future. >3) Are there any other common solutions to setup >standby instance? I read article of Dr. Yves Trudeau >on the topic, but that solution is not possible in our >environment and since this article was written 3 years >passed, so I would expect that some developments has >been done in this field. You could buy expensive hardware and implement our new Hot Standby solution, where the kernel of the standby databases share the same log volume as the master database and read the log entries, as they are written. But most probably that solution will be too expensive. Best Regards, Tilo Heinrich SAP Labs Berlin -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
