You may still run into a problem. When you terminated forward recovery
on the backup system at log S00001000, you would have lost any logged
updates that were not committed. (The commits would have been done
during the last <5 min of operation before the primary server crashed.)
When you try to restore on the primary server; you will have a
discontinuity in the logs where you start the new log from the backup
server.
I'd backup the database on the backup server immediately after
terminating rollforward and ship that backup to the primary server
immediately. It will be available to restore on the primary server and
you can start rollforward recovery on the primary server until you make
a clean shutdown on the backup server and ship the last log tape back to
the primary server. This way, the outage to return to the primary server
would be transmit and process of a single 5 min log.
Phil Sherman
sh*******@gmail.com wrote:
For the backup site is remote, it takes long time to bring the ***GB
backup image to primary site.
So I am wondering if I can use the image has been taken on primary site
of sunday, and apply the logs from both site. From primary site, I use
log flie since last backup till S0001000.LOG, but ignore all the rest
(for it crash), plus those generated on seconday site (from
S0001001.LOG to end)
I think there could be some loss because of some log was not shipped to
backup site (after S0001000.LOG), but it is acceptable here. I dont the
structure of logs, and hope they are consistent.
