Robert Robidoux wrote:
> Alexei Novakov <alexei_novakov <at> yahoo.com> writes:
>>I need some advice for setting up SAPDB standby
>>database. I am running SAPDB 7.4.3 on SuSE 8.2 Linux.I
>>saw example of standby setup in SAPDB documentation
>>and trying to do it without big success so far.
>>
>>The idea is to have a cronjob which would do regular
>>log backups (backup_start log_bak) on active instance,
>>FTP it to other Linux box and feed with them standby
>>instance (recover_start log_bak <nnn>). There is no
>>problem to backup logs, but when recovering first log
>>backup on standby instance it returns -8020, which
>>means it expects next log backup (recover_replace
>>...). If I release utility session now the instance
>>will go down. But cronjob solution assumes that
>>multiple calls to dbmcli will be made. And what are we
>>supposed to do if the box needs to be rebooted? So
>>here are the questions:
>>
>>1) Are there alternatives to load log backups on
>>standby instance other then do
>>recover_start-recover_replace in one utility session?
>>2) Can I extend one utility-backup-recover session
>>over multiple dbmcli calls?
>>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.
> 8020 is a normal response. $1 is your first logfile or the previous $2. $2
> is
> an unprocessed log file. 8020 is a normal reponse for recover_start and
> recover_replace. You can do more recover_replaces in one session, but I find
> it easy to have an automated process with just two files. Assume the
> instructions below are script roll.csh. You would do roll.csh 1 2, then
> roll.csh 2 3 and roll.csh 3 4, continuing in this manner.
>
> (Enclose in a dbmcli call)
> db_offline
> db_cold
> util_connect
> recover_start LCLOG LOG $1
> recover_replace LCLOG /sapdb/LP0/fullbackup/saparch/lclog $2
> recover_cancel
> util_release
> db_stop
i have scripts for automatic incremental log backups and recovery,
recovering all available log fragments at once, but the idea is the same
as outlined above.
i would gladly share them (some docs are available in german) but as i
posted to the list - my scripts stop to work after some days. the
fragments stop working. i didn't have the time to investigate further,
but would gladly discuss the issue again.
Raimund
--
Pinuts media+science GmbH http://www.pinuts.de
Raimund Jacob [EMAIL PROTECTED]
Krausenstr. 9-10 voice : +49 30 59 00 90 322
10117 Berlin fax : +49 30 59 00 90 390
Germany
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
