The log recovery interface permits you to abort the current recovery. The cited answer of Tilo described the normal standard case. With "recover_cancel" the current recovery is aborted. Then you can define additional volumes or simply interrupt and go on later. If you are going on with an interrupted recovery it will begin with the last read log. sincerely Uwe
> -----Original Message----- > From: SAP Hosting, VTC-BAS [mailto:[EMAIL PROTECTED]] > Sent: Donnerstag, 28. November 2002 15:14 > To: 'sapdb.general' > Subject: Standby Database > > > Hello > > We are currently establishing a "Hot Standby" Database, so we > can switch > from the original database to the standby system in case of an error. > Therefore we made a data backup of the original database > which we recovered > into the standby database. Afterwards we apply the logs from > the autolog > backup. > The main problem is, that the dbmcli must not be stopped > during the recovery > process > (http://listserv.sap.com/pipermail/sapdb.general/2002-July/012 891.html) I also do not see a way to create a backup of the current state or to add further data devspaces. So we can not prevent an overflow in the standby database. Transfering a regular backup is not possible because the connection between the two db-hosts is to small to handle the volume of a regular data backup. Are there any alternatives? TIA Torsten --------------------------------------------------------- This Mail has been checked for Viruses Attention: Encrypted mails can NOT be checked! ** Diese Mail wurde auf Viren geprueft Hinweis: Verschluesselte mails koennen NICHT auf Viren geprueft werden! --------------------------------------------------------- _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
