Re: Can not fork server connection

robertwane@hotmail.com wrote: > > Sometimes when I run some commands such as ontape. It will display: > Can not fork server connection. What on earth does this mean? When you perform a full restore (ontape -r or -p) the engine must be offline. The ontape process will bring the engine up into recovery mode as ontape only reads and writes the tape data it is an engine thread that actually performs the archives and restores. The message you have seen means that for one reason or another the 'oninit -r' command that ontape executes either failed or took so long that ontape got tired of waiting for it and killed it off. I see the former when the engine is already online or when you are trying to restore an additional instance or to a new machine and the kernel parameters are insufficient. I see the latter when you have a slow machine (or in my case a machine slow to attach to shared memory) and too much shared memory and too many VPs configured. In the former cases either bring the engine down or adjust the kernel parameters and rebuild the kernel. In the latter case, reduce the number of buffers to a minimum (say 1000 or less you only need a few for the restore), reduce the virtual segment and next segment sizes, and cut the number of CPU, NET, and AIO VPs to bare bones (you will only be running two threads for the restore and writing to one chunk at a time). After the restore bring the engine to online mode (VERY IMPORTANT) then shut it down, restore the original ONCONFIG parameters, and bring it back up. Art S. Kagel