Hi Tilo,
Thanks for your response.
> >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.
Yes I tried this, but it seems that next time I have
to start recovery starting from the first log backup
anyways even though it was recovered in previous
session already. I think it kills the idea of feeding
standby instance with sequential log backups. Am I
missing something?
> >2) Can I extend one utility-backup-recover session
> >over multiple dbmcli calls?
>
> No yet. Most probably in the future.
It would definitely be the solution for previous
problem.
> >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
Best regards.
Alexei.
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
