Subject restore fail hangs
Author Nick Upson
Over the weekend we had a automated backup & restore fail as the backup file
was corrupted, this is ok except that the restore
seemed to think there was another file of the backup and just hung waiting
for it (or user input to tell it). This was all dealt with
before I could get to it so I don't have the exact messages or the back file

Is there a way I can tell gbak there is only 1 file, if it's bad then report
that as normal but do not hang there waiting for input.

[Non-text portions of this message have been removed]