This behaviour you describe is not supported, but.. The Data and Log volumes of one online database are not logical compatible to another. You can use the Data backup from A install it on B but do not restart it. You can then "feed" B with log backups from A. But at the moment you restart B to mode online(warm) you have finally created a new instance with its own "life-cycle". This is often used as a kind of standby szenario. If you want to re enable the standby you have to start again with a complete backup from A install a new instance B and restore the log backups from A (without restarting B).
regards Uwe > -----Original Message----- > From: Mohamed Koker [mailto:Mohamed.Koker@;mentatsolutions.com] > Sent: Montag, 4. November 2002 11:01 > To: [EMAIL PROTECTED] > Subject: Restore instance under Windows > > > I created a database instance on machine A, added some data, created a > backup for migration, and used this to create a database > instance on machine > B by recovering the backup from machine A. > > So far, so good. > > My problem begins when I update the data on machine A, make a > new backup and > try to bring both machines into sync by restoring the new > backup on machine > B. This always fails at the point when I restart the database. > > The only way I have managed to bring the two databases into sync is by > dropping the instance on machine B and recreating it based on > the backup > from machine A. > > This strikes me as more than a little odd. > > Can someone tell me what I am doing wrong ? Is there a step I > am missing ? > > I am using 7.30.28 under Windows 2000 on both machines and am > using the > DBMGUI. > > Thanks in advance > > -Mohamed > > > > > _______________________________________________ > 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
