10 More Discussions You Might Find Interesting
1. HP-UX
I suffered a fault on a tape drive and would like to redirect my fbackup from /dev/rmt/0m to a NFS Share. I have mounted a NFS share in /mnt/NFSShare. When I run the following command:
/etc/fbackup -0 -uv -i /backup2/BEM/BEML1 -c /usr/local/scripts/backup/fbackup_config -f... (2 Replies)
Discussion started by: Iceman_Pol
2 Replies
2. HP-UX
i tried to take a backup by using fbackup command. But it exactly aborted after taking backup of 2GB data. pleasse guide me how should i proceed to overcome this problem.
The command i used is:
fbackup -0 -y -f /dir1 \
-g fbackup_graph \
-c fbackup_config
... (6 Replies)
Discussion started by: siva3492
6 Replies
3. HP-UX
Hello,
I'm still new in HP-UX backup and I want to do a FULL BACKUP of HP-UX server to TAPE device. After reading on several forums and posts, i have list down several steps on how to do a full backup on HP-UX with fbackup. I would like the gurus here to comment/advise on the steps below
1)... (4 Replies)
Discussion started by: miskin
4 Replies
4. HP-UX
Hi,
I have a fbackup step as below in HP-UX
/bin/nice /etc/fbackup -f /dev/rmt/0m -i / -I /opt/monitrol/tmp/Index.full
Now the errors that i will get in case of the fbackup step, I want to redirect them to a file. Please help me how to redirect to a file.
Thanks,
Avik. (4 Replies)
Discussion started by: avik.nandi
4 Replies
5. Shell Programming and Scripting
Hi,
I have a fbackup step as below
/bin/nice /etc/fbackup -f /dev/rmt/0m -i / -I /opt/monitrol/tmp/Index.full
Now the errors that i will get in case of the fbackup step, I want to redirect them to a file. Please help me how to redirect to a file.
Thanks,
Avik. (5 Replies)
Discussion started by: avik.nandi
5 Replies
6. HP-UX
Hi Friends,
I'm new to unix, I have the below script which takes regular backup. Now if fbackup fails I get the below messages in my log as
fbackup(3047): could not open output file /dev/rmt/0m
fbackup(3019): would you like to enter a new output file?
fbackup(3004): writer aborting... (4 Replies)
Discussion started by: avik.nandi
4 Replies
7. HP-UX
Hello,
We've recently had a multiple hardrive failure in our legacy HP9000. Now the drives are repaired and the filesystems are recreated, I went to restore the last of the database tables from our dds3 backup, but cannot. Here's what's going on: BTW, I'm an absolute novice w/ HP-UX
The... (5 Replies)
Discussion started by: jastuart
5 Replies
8. HP-UX
Hi,
I am writing a script that is doing a fbackup during the night and before it shutdown the database then run the fbackup then at the end before restarted the data base, I would like to check the status that the fbackup is fine but I always have warning (about socket: fbackup(1102): WARNING:... (2 Replies)
Discussion started by: touny
2 Replies
9. 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
10. HP-UX
Dear All,
We have Universe database on HP-UX Servers, when we take back on DDS3 it completes around 48 Gb data on just one tape. As per DDS media specs it can hold upto 24 GB compressed data. How it is managing more than double data..? (3 Replies)
Discussion started by: Kashif Raees
3 Replies
bootconf(4) Kernel Interfaces Manual bootconf(4)
NAME
bootconf - boot device configuration table
DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control
scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware
and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
boot devices should be automatically updated, the administrator must edit the file manually.
There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown:
disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following:
Indicates that the root disk is in LVM or VERITAS Volume Manager
(VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.
Indicates that the root disk is in the
"whole disk" format with no partitions, but boot and swap space are reserved outside the file system.
device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root
disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file
that references the entire disk.
Blank lines are permitted. Any line beginning with a is considered to be a comment.
DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self-
explanatory; a few warrant additional explanation:
If there are no other messages about
the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem
is.
The specified device file does not point to a disk where there is a
lif which contains the file
Some character other than
or is in the first field of a line.
As of release 10.0, the boot areas in
must all be on the same type of disk layout.
There are characters after the
device file specification.
EXAMPLES
The boot area is on an LVM root disk:
l /dev/disk/disk7_p2
The boot area is on a whole disk layout:
w /dev/disk/disk7
WARNINGS
All of the boot devices in the file must have the same disk layout.
AUTHOR
was developed by the Hewlett-Packard Company.
FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).
documentation.
bootconf(4)