Date: 10/06
Affected NV Version: 7.4.x
OS Version: Unix/Linux
Plugin version: N/A
Application version: N/A
Description:
The netvault script plugin has a problem with scripts that fork
processes with possessive process handles (ie. they won't let go of the
script plugin). What you see when this happens is the netvault job sat in
the running script state, because it never gets released for the forked
process(i.e. starting oracle db in sh or an oracle listner in any shell).
Solution:
To prevent this from happening on a UNIX/LINUX platform the post script may be re-written using the operating scheduler command 'at' in the following format.
at -f <script name> now
i.e. for a script named orange that resides with directory /usr/scripts
the netvault post script should read as follows:
#!/bin/sh
at -f /usr/scripts/orange now
NB the post script must be located within the ~netvault/scripts directory on the machine where the actual backup is being performed.
i.e. if the backup job is of an oracle client then the post script must reside on the oracle client machine.
This workaround passes the process handle to the unix/linux scheduler and allows the job to complete.
* shexec is replaced by "at -f <script name> now" in NetVault 7.4 and above.
Please refer to the text above
