With this specific restore...around 200 logs were applied before it
required the logs I had on disk...so as soon as I started the log
restore....I then copied the logs into the specified restore folder.  By
the time the restore needed the logs that were on disk, everything had
already been copied across.   I noticed also when these logs were being
applied that they didn't show up on the GUI, I guess this is because they
weren't archived   As I said before they get removed from the restore
folder once they are applied.  Once it has finsihed with these logs it
continues applying the logs from tape.

I haven't tried copying the log files across only once they are being
called for, I'm not sure this would work as the process doesn't wait for
that long before deciding the logs aren't available so there isn't a lot
of time to copy them across.


Marc.





"Richard Foster" <Richard.Foster AT HYDRO DOT COM>

Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
23-Oct-2002 14:27
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>




        To:     ADSM-L

        cc:
        Subject:        Re: Transaction Log Restores

Marc

Sorry to hammer this home, but ...

> I didn't do anything differently except copy the log files
> after the applylogs command was issued.

I'm guessing that what you're saying is that
- you issue the applylogs command
- the command waits until you copy a log file into the folder
- it applies the log and then deletes it.
You then repeat the copy for each log until you're done.

Is that a correct guess?

What happens if the applylogs needs logs that *have* been archived by the
TDP, either before or after the manual logs? Is the TDP clever enough to
handle that? At a guess, it should
- restore/apply/delete the logs as usuaul, from before the manual set
- wait for you to copy the logs in, as described above
- then continue with the usual restore/apply/delete of logs from after the
manual set

Is it really that clever?

Richard