Re: restore with onbar and bcv: How to apply logs

"Neil Truby" <neil.truby@ardenta.com> wrote in message news:bot9p5$1gh2sh$1@ID-162943.news.uni-berlin.de... > 1.. Shutdown the instance to be restored, onmode -kuy > 2.. Salvage any logical logs which have not been backed up, onbar -l -s > 3.. Initiate a BCV restore from the Timefinder group. > 4.. Once the BCV's are restored, split them. > 5.. Inform onbar that an external restore has occurred, onbar -r -e -p After splitting the BCVs, Max is doing a backup with onbar and not a raw device dump. This means the log position will be different than the log position of the production instance. Isn't this a problem while logical recovery after an external restore? > 6.. Rollforward logical logs, onbar -r -l > 7.. Bring the instance online, once in quiescent, onstat - ; onmode -m > We've perfected this at a number of sites, so call me if you need further > advice. > > -- > Neil Truby t:01932 724027 > Director m:07798 811708 > Ardenta Limited e:neil.truby@ardenta.com > > "Max Thoran" <m.thoran@t-online.de> wrote in message > news:9ad86a88.0311120104.350cc74e@posting.google.com... > > Hello, > > > > I have a problem with an EMC Timefinder restore. We have a production > > database running on EMC storage. To make a backup, i establish a bcv, > > put the database to archive mode with "onmode -c block", split the bcv > > an resume the production. Then i import the data from the bcv on a > > different server ( the netbackup machine ), start the database and > > backup it to tape with onbar. Works fine. > > Now I want to restore the database. On the backup server, i can > > restore the database to the state it was in when i split the bcv. But > > from this time, production has continued to produce logs ( and write > > these to tape ). How can i apply these logs ? I thought about merging > > the data from the ixbar files from production ( for the logs ) and > > from the backup server ( for the tablespace backups ). Is this legal ? > > > > Thanks in advance > > > > Max Thoran > >

"itsme" <please.no.spam@no-spam.net.org.com> wrote in message news:bovhsp$4m0$1@reader08.wxs.nl... > > "Neil Truby" <neil.truby@ardenta.com> wrote in message > news:bot9p5$1gh2sh$1@ID-162943.news.uni-berlin.de... > > 1.. Shutdown the instance to be restored, onmode -kuy > > 2.. Salvage any logical logs which have not been backed up, onbar -l -s> > 3.. Initiate a BCV restore from the Timefinder group. > > 4.. Once the BCV's are restored, split them. > > 5.. Inform onbar that an external restore has occurred, onbar -r -e -p > > After splitting the BCVs, Max is doing a backup with onbar and not a raw > device dump. This means the log position will be different than the log > position of the production instance. Isn't this a problem while logical > recovery after an external restore? Is he? I didn't notice that. It's not going to work then, is it? The act of bringing the server online to perform the onbar backup initiates fast recovery, which will prevent logical logs being subsequently applied.