Hi,
Currently, we are doing make recovery in our servers but dds tape drive of 1 of our servers is not working. I suppose to use external dds tape drive but the problem is that there is no slot from the server for the scsi type external dds device. Is it possible to use drives from other... (5 Replies)
Hello All,
I need to bring down our old 9000 series d350, but my supervisor wants an ignite backup created. I cannot find ignite in the usual places (/opt/ignite) nor can I find it in swlist. As far as I can tell the cd's are long gone.
Is there anywhere else I could look for ignite being... (6 Replies)
Hi All,
I am getting below error while igniting(restoring image) on 2470 server. i tried with different images it is giving same error. please help me out to resolve this issue
* Making VxFS filesystem for "/usr/aethos/snss/suppimpapp1",
(/dev/vg00/rsuppimpapp1).
*... (3 Replies)
I am looking to make bootable tape backups of four machines running HP-UX 09.02, 09.05 and 09.07.
I successfully located Ignite 10.20 and installed it and made a backup on the one machine running HP-UX 10.20. I am having trouble locating information about Ignite for HP-UX 9. Does it exist? Is... (3 Replies)
I've read the Ignite User/Admin Guide but I'm having trouble figuring out if I can do a make_net_recovery if the ignite server and client server are on completely different networks? If this can be done is there any special configuration? If I initiate the command from the server it looks like it... (3 Replies)
Works all.
Depot shared via nfs
dhcp working
setting file system,network,root password,etc
But when i start "go!" with installation,give me
this error.
How to fix,debug?
Thanks
http://s24.postimg.org/5hzbgk551/unixbell3.png (3 Replies)
Hi
Does anybody know how to get hold of a very old (A.3.7.n) copy of the ignite software depot for HP-UX 10.20? (7 Replies)
Discussion started by: gregsih
7 Replies
LEARN ABOUT HPUX
statd
statd(1M)statd(1M)NAME
statd, rpc.statd - network status monitor
SYNOPSIS DESCRIPTION
is an RPC server. It interacts with to provide the crash and recovery functions for the locking services on NFS (see lockd(1M)).
keeps track of the clients with processes which hold locks on a server. When the server reboots after a crash, sends a message to the on
each client indicating that the server has rebooted. The client processes then informs the on the client that the server has rebooted.
The client then attempts to reclaim the lock(s) from the server.
on the client host also informs the on the server(s) holding locks for the client when the client has rebooted. In this case, the on the
server informs its that all locks held by the rebooting client should be released, allowing other processes to lock those files.
Options
recognizes the following options and command-line arguments:
This is an obsolete option. All messages and errors are logged to
WARNINGS
The crash of a server is only detected upon its recovery.
FILES
lists hosts and network addresses to be contacted after a reboot
lists hosts and network addresses that could not be contacted after last reboot
includes a number which changes during a reboot
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSO lockd(1M), fcntl(2), lockf(2), signal(2), sm(4).
statd(1M)