Hi all,

This topic has been discussed before, so I hope this is not a repeat of a
question that has already been resolved.

We use bpstart_notify and bpend_notify scripts to switch Oracle into hot
backup mode (or shut it down, depending on server/database) at the start of
the backup and switch it out of hot backup mode (or start it up) at the end
of the backup.  As the backups are multi-stream, the logic surrounding this
is a bit tricky.  We use a set of lock files created by the first stream and
removed by each stream as it completes, to ensure the processing occurs at
the correct time in the backup.

So far so good, but if for some reason (like some streams failing due to
lack of tapes or having passed their scheduled window) not all streams run,
the databases will be left in hot mode (messy) or down (embarrassing).

While I try to get my head around what to do next, has anyone out there any
helpful suggestions?  I think the only way to be sure of what is happening
is for the client scripts to remote call back to the master to query the
jobs database.  All of this is on Solaris with NBU 3.4.

thanks, Phil

Phil Weber
IT Infrastructure Unix Systems Engineer

Phone: 01384 26 4136
Mobile: n/a


This private and confidential e-mail has been sent to you by Egg.
The Egg group of companies includes Egg Banking plc
(registered no. 2999842), Egg Financial Products Ltd (registered
no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
carries out investment business on behalf of Egg and is regulated
by the Financial Services Authority.  
Registered in England and Wales. Registered offices: 1 Waterhouse Square,
138-142 Holborn, London EC1N 2NA.
If you are not the intended recipient of this e-mail and have
received it in error, please notify the sender by replying with
'received in error' as the subject and then delete it from your
mailbox.