Sponsored Content
Full Discussion: frecover
Top Forums UNIX for Dummies Questions & Answers frecover Post 314 by Neo on Wednesday 22nd of November 2000 01:17:47 AM
Old 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

frecover

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

frecover on HP 11.11

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

HP fbackup/frecover to SUN UNIX format?

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

frecover command need help urgent please

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

frecover problem

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

frecover counterpart on linux

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
SG_RESET(8)							     SG3_UTILS							       SG_RESET(8)

NAME
sg_reset - sends SCSI device, target, bus or host reset; or checks reset state SYNOPSIS
sg_reset [--bus] [--device] [--help] [--host] [--no-esc] [--target] [--verbose] [--version] DEVICE DESCRIPTION
The sg_reset utility with no options (just a DEVICE) reports on the reset state (e.g. if a reset is underway) of the DEVICE. When given a --device, --target, --bus or --host option it requests a device, target, bus or host reset respectively. A device reset is applied to the Logical Unit (LU) corresponding to DEVICE. It is most likely implemented by a Low level Driver (LLD) in Linux as a LOGICAL UNIT RESET task management function. The ability to reset a SCSI target was added in Linux kernel 2.6.27 . A LLD may send Low level Drivers (LLDs) the I_T NEXUS RESET task man- agement function. Alternatively it may use a transport mechanism to do the same thing (e.g. a hard reset on the link containing a SAS tar- get). In the Linux kernel 2.6 and 3 series this utility can be called on sd, sr (cd/dvd), st or sg device nodes; if the user has appropriate per- missions. Users of this utility can check whether a reset recovery is already underway before trying to send a new reset with this utility. Calling this utility with no options, just the DEVICE, will do such a check. OPTIONS
-b, --bus attempt a SCSI bus reset. A bus reset is a SCSI Parallel Interface (SPI) concept not found in modern transports. A recent LLD may implement it as a series of resets on targets that might be considered as siblings to the target on the DEVICE path. -d, --device attempt a SCSI device reset. This would typically involve sending a LOGICAL UNIT RESET task management function to DEVICE. -h, --help print the usage message then exit. -H, --host attempt a host reset. The "host" in this context is often called a Host Bus Adapter (HBA) and contains one or more SCSI initiators. -N, --no-esc without this option, if a device reset (--device) fails then it will escalate to a target reset. And if a target reset (--target) fails then it will escalate to a bus reset. And if a bus reset (--bus) fails then it will escalate to a host reset. With this option only the requested reset is attempted. An alternate option name of --no-escalate is also accepted. -t, --target attempt a SCSI target reset. A SCSI target contains one or more LUs. This would typically involve sending a I_T NEXUS RESET task management function to DEVICE There may be a transport action that is equivalent (e.g. in SAS a hard reset on the link that con- tains the target). -v, --verbose increase the degree of verbosity (debug messages). -V, --version prints the version string then exits. NOTES
The error recovery code within the Linux kernel (SCSI mid-level) when faced with a SCSI command timing out and no response from the device (LU) does the following. First it tries a device reset and if that is not successful tries a target reset. If that is not successful it tries a bus reset. If that is not successful it tries a host reset. The "device,target,bus,host" order is the reset escalation that the --no-esc option attempts to stop. In large storage configurations the escalation may be (very) undesirable. This utility calls the SG_SCSI_RESET ioctl and as of lk 3.10.7 the --no-esc option is not supported. Patches to implement this functional- ity have not been accepted. If you want it, post your concern to linux-scsi@vger.kernel.org which is the linux-scsi list. SAM-4 and 5 define a hard reset, a LOGICAL UNIT RESET and a I_T NEXUS RESET. A hard reset is defined to be a power on condition, a microcode change or a transport reset event. LOGICAL UNIT RESET and I_T NEXUS RESET can be requested via task management functions (and support for LOGICAL UNIT RESET is mandatory). In Linux the SCSI subsystem leaves it up to the LLDs as to exactly what type (if any) of reset is performed. The "bus reset" is SCSI Parallel Interface (SPI) concept that may not map well to recent SCSI transports so it may be a dummy operation. A "host reset" attempts to re-initialize the HBA that the request passes through en route to the DEVICE. Note that a "host reset" and a "bus reset" may cause collateral damage. This utility does not allow individual SCSI commands to be aborted. SAM-4 defines ABORT TASK and ABORT TASK SET task management functions for that. Prior to SAM-3 there was a TARGET RESET task management function. And in SAM-4 I_T NEXUS RESET appeared which seems closely related: the "I_T" stands for Initiator-Target. Transports may have their own types of resets not supported by this utility. For example SAS has a link reset in which both ends of a physical link (e.g. between a SAS expander and a SAS tape drive) renegotiate their connection. Prior to version 0.57 of this utility the command line had short options only (e.g. -d but not --device). Also -h invoked a host reset while in the current version -h is equivalent to --help and both -H and --host invoke a host reset. For backward compatibility define the environment variable SG3_UTILS_OLD_OPTS or SG_RESET_OLD_OPTS . In this case -h will invoke a host reset and the output will be verbose as it was previously (equivalent to using the --verbose option now). For example: SG_RESET_OLD_OPTS=1 sg_reset -h /dev/sg1 sg_reset: starting host reset sg_reset: completed host reset AUTHORS
Written by Douglas Gilbert. COPYRIGHT
Copyright (C) 1999-2013 Douglas Gilbert This software is distributed under the GPL version 2. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR- POSE. sg3_utils-1.37 August 2013 SG_RESET(8)
All times are GMT -4. The time now is 06:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy