11-22-2000
Thanks for the man page pointer. Here are my current thoughts of what I would do if this was my problem and some background discussion.
First of all, in my years of HPUX experience, I always tried to avoid using SAM. SAM does many commands when you execute a function and it is hard to debug errors, as you are discovering.
Back away from SAM, decide what you are going to do, use the HP documentation and man pages and do it, step-by-step without SAM in between you and the environment. This has always been my method-of-operating in an HPUX environment. That is not to say that SAM is 'not good' because I use it to add users, groups and other less complex tasks. However,
for non-trivial tasks or tasks that are giving errors, I immediately move from SAM to the command line.
Now, assume you are at the command line. Take a look at the files and their permissions, write them down, etc. Start your reconfiguration step-by-step. If that does not work and you get errors, for example with frecover(); I would use a system call tracing utility to find out what is the exact HPUX system call returning the error and the arguments being passed to the system call. Sometimes the return codes of the systems call are much more informative that the text messages in the console. You will have to read the detailed man pages of the system calls to get this information. Somethings you will have to go into the header files in the associated system libs and look for the #defines in the right includes to get the next level of details.
I don't recall the name of the HPUX system call trace utility, something like ptrace() or strace() or something like that. There is one however, and learning to use it will become one of your greatest sysadmin debugging tools.
However, in many cases, just executing the task from the command line, step-by-step, in a controlled manner, with lead to a discovery of the problem. It may not be necessary to go a level deeper into system call tracing; but you will surely learn a lot about your environment getting out from under SAM and into the nuts-and-bolts of the task at hand.
6 More Discussions You Might Find Interesting
1. HP-UX
I have machine (HP-UX) 11.x and I took backup using fbackup (took 4 DDS tapes) then i did restore using frecover . the restore
failed on the 4th tape . and the process killed .
Can I restore only the 4th tape. or I have to do full recover from biginning ? (1 Reply)
Discussion started by: salhoub
1 Replies
2. UNIX for Dummies Questions & Answers
Hi,
Can someone please explain how I can check whether my files were backed-up to tape.
I issued this command and got an error:-
# frecover -I /tmp/mth -f /dev/rmt/5m
frecover(2105): did not find expected file marker
frecover(5409): unable to read volume header
frecover(5418): not an... (2 Replies)
Discussion started by: gummysweets
2 Replies
3. HP-UX
Hi All,
We have about 7 years worth of data which used the HP fbackup utility. Is there any utility to read these tapes on Solaris? The goal is to create new tapes using Legato.
Do we need to download them to a box first using frecover, then copy them from SUN using Legato?
Any help in... (0 Replies)
Discussion started by: tinakumar
0 Replies
4. HP-UX
Hi,
I have a tape fbackup done (fbackup -f /dev/rmt/0m -i / -I index.fullfbackup) and I need to restore 3 filesystems, I would like to know the correct command and options:
example:
I want to restore the filesystem /data1 under /data1
and /data2 under another filesystem /datatest
I tried... (4 Replies)
Discussion started by: touny
4 Replies
5. HP-UX
I had to do a recovery and restore from backup (using ignite & backups from fbackup job) on hpux 10.20.
Problem is, all users (except root) receive error 'unknown user' when logging in (during script that checks quotas).
They can still successfully log in to the system.
However, the files... (9 Replies)
Discussion started by: mrviking
9 Replies
6. Red Hat
Hello All,
The frecover command on HP UX gives information about the backed up file in the format-
Magic Field:
Machine Identification:
System Identification:HP-UX
Release Identification:B.11.11
Node Identification:
User Identification:
Record Size:
Time:
Media Use:0
Volume Number:1... (1 Reply)
Discussion started by: shamik
1 Replies
LEARN ABOUT CENTOS
sam_initialize
SAM_INITIALIZE(3) Corosync Cluster Engine Programmer's Manual SAM_INITIALIZE(3)
NAME
sam_initialize - Initialize health checking
SYNOPSIS
#include <corosync/sam.h>
cs_error_t sam_initialize (int time_interval, sam_recovery_policy_t recovery_policy);
DESCRIPTION
The sam_initialize function is used to initialize health checking of a process.
Application can have only one instance of SAM. This function must be called before any other of SAM functions. It is recommended to ini-
tialize before the process begins any process initialization.
The time_interval parameter is a timeout in milliseconds before taking recovery action after having not received a healthcheck.
If time_interval parameter is zero, there is no time limit and no healthcheck must be sent by the process. In this operational mode, a
process failure will continue to execute the recovery policy.
The recovery_policy is defined as type:
typedef enum {
SAM_RECOVERY_POLICY_QUIT = 1,
SAM_RECOVERY_POLICY_RESTART = 2,
SAM_RECOVERY_POLICY_QUORUM = 0x08,
SAM_RECOVERY_POLICY_QUORUM_QUIT = SAM_RECOVERY_POLICY_QUORUM | SAM_RECOVERY_POLICY_QUIT,
SAM_RECOVERY_POLICY_QUORUM_RESTART = SAM_RECOVERY_POLICY_QUORUM | SAM_RECOVERY_POLICY_RESTART,
SAM_RECOVERY_POLICY_CMAP = 0x10,
SAM_RECOVERY_POLICY_CONFDB = 0x10,
} sam_recovery_policy_t;
where
SAM_RECOVERY_POLICY_QUIT
on failure, the process will terminate.
SAM_RECOVERY_POLICY_RESTART
on failure, the process will restart.
SAM_RECOVERY_POLICY_QUORUM
is not policy. Used only as flag meaning quorum integration
SAM_RECOVERY_POLICY_QUORUM_QUIT
same as SAM_RECOVERY_POLICY_QUIT but sam_start (3) will block until corosync becomes quorate and process will be terminated if quo-
rum is lost.
SAM_RECOVERY_POLICY_QUORUM_RESTART
same as SAM_RECOVERY_POLICY_RESTART but sam_start (3) will block until corosync becomes quorate and process will be restarted if
quorum is lost.
SAM_RECOVERY_POLICY_CMAP
is not policy. Used only as flag meaning cmap integration. It can be used with all previous policies. For backward compatibility,
SAM_RECOVERY_POLICY_CONFDB with same meaning as SAM_RECOVERY_POLICY_CMAP is also provided.
To perform event driven healthchecking, sam_register(3) and sam_start(3) functions must called. Event driven healthchecking causes the
duplicate standby process running the SAM serve rto periodically request healthchecks from the active process.
RETURN VALUE
This call return CS_OK value if successful, otherwise and error is returned.
ERRORS
CS_ERR_BAD_HANDLE
can happened in case of double initialization.
CS_ERR_INVALID_PARAM
recovery_policy has invalid value.
SEE ALSO
sam_register(3), sam_start(3), sam_hc_callback_register(3)
CS_ERR_TRY_AGAIN Resource temporarily unavailable
CS_ERR_INVALID_PARAM Invalid argument
CS_ERR_ACCESS Permission denied
CS_ERR_LIBRARY The connection failed
CS_ERR_INTERRUPT System call inturrupted by a signal
CS_ERR_NOT_SUPPORTED The requested protocol/functuality not supported
CS_ERR_MESSAGE_ERROR Incorrect auth message received
CS_ERR_NO_MEMORY Not enough memory to completed the requested task
corosync Man Page 21/05/2010 SAM_INITIALIZE(3)