ontape moseying around, a bit aimless

IDS 9.20, HP-UX 11.0, kaio enabled, tcp_ip connections. Does anyone know why ontape -r takes such an inordinate amount of time (3-4 minutes) before bring up the dhe details of the archive tape/file, then a similar period of time before actually begining a restore? The restore of a small server (<1 GByte) takes about 15 minutes, 10 of which is seemingly wasted waiting time. Also, restores on occasion "hang" and have to be re-started. And it seems only to be using tcp-ip connections, rather than shm. I've tried shouting "Get on with it!" at the terminal, but to no avail. Just me, is it?!

Neil Truby wrote: > > IDS 9.20, HP-UX 11.0, kaio enabled, tcp_ip connections. > > Does anyone know why ontape -r takes such an inordinate amount of time (3-4 > minutes) before bring up the dhe details of the archive tape/file, then a > similar period of time before actually begining a restore? It has to read one or more tape blocks from the backup device, if your block size is large that can take a while. Then the tape device is closed and ontape has to wait for the tape drive to rewind before the close() returns. Then it first formats and prints out the archive header info for you to approve. > The restore of a small server (<1 GByte) takes about 15 minutes, 10 of which > is seemingly wasted waiting time. Next ontape has to wait for the engine to start and enter "Recovery" mode. Then finally the restore begins. > Also, restores on occasion "hang" and have to be re-started. And it seems > only to be using tcp-ip connections, rather than shm. Ontape always uses the default connection, whatever that is. > I've tried shouting "Get on with it!" at the terminal, but to no avail. I'm partial to banging on the upper right side of my monitor myself 80) Art S. Kagel

Art S. Kagel <kagel@bloomberg.net> wrote in message news:39CA8714.27D5E81E@bloomberg.net... > Neil Truby wrote: > > > > IDS 9.20, HP-UX 11.0, kaio enabled, tcp_ip connections > It has to read one or more tape blocks from the backup device, if your block > size is large that can take a while. Then the tape device is closed and > ontape has to wait for the tape drive to rewind before the close() returns. > Then it first formats and prints out the archive header info for you to > approve. Yes, I thought about that, but you see the same multi-minute delay restoring from disk. There's definitely something different about it wrt v5 or v7. > Ontape always uses the default connection, whatever that is. Really? It ignores the INFORMINSERVER setting? > I'm partial to banging on the upper right side of my monitor myself 80 Unfortunately an old bug has been re-introduced onto v9.20 on HP-UX that precludes enabling the side-of-monitor accelerator driver. My server responds to speed-up instructions only via the aural or the tantrum interfaces.