HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- fbackup errors (not the same in the "search")
Operating System - HP-UX
1834261
Members
57571
Online
110066
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2001 08:06 AM
03-14-2001 08:06 AM
Hello everyone,
I'm just starting the "fbackup" in place of our current "tar" to do the back-up. I'd read the man page for fbackup (>3X) and when I ran my script, I have these 2 errors that I can't find document anywhere. I went and search it through the forum but none for the type of error that I encounter. Any help would be greatly appreciate.
fbackup -f $tape -u0g $BUDIR/fullbkup -d $FULLOGFL -I $INDXFILE
These are the errors:
WARNING: unable to read a volume header
warnings encountered during backup: 4
I've read that "volume header" is general structure of fbackup - so it should be there right??
I'm just starting the "fbackup" in place of our current "tar" to do the back-up. I'd read the man page for fbackup (>3X) and when I ran my script, I have these 2 errors that I can't find document anywhere. I went and search it through the forum but none for the type of error that I encounter. Any help would be greatly appreciate.
fbackup -f $tape -u0g $BUDIR/fullbkup -d $FULLOGFL -I $INDXFILE
These are the errors:
WARNING: unable to read a volume header
warnings encountered during backup: 4
I've read that "volume header" is general structure of fbackup - so it should be there right??
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2001 08:08 AM
03-14-2001 08:08 AM
Re: fbackup errors (not the same in the "search")
It is possible these were non-fbackup tapes you are reusing. fbackup looks for volume header info.
You shouldn't get them once fbackup has written on them.
You shouldn't get them once fbackup has written on them.
There be dragons...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2001 08:13 AM
03-14-2001 08:13 AM
Solution
Hi:
This is expected. If you have a virgin tape, or one that wasn't last used with 'fbackup', then you will see warning "unable to read a volume header". This will result in a returncode of <4> for the fbackup execution as documented in the man pages. In fact, the <4> is the value in the second line.
If you use the same tape again and again for 'fbackup', you will see that it keeps track of the number of times a tape is used. This is part of the header that 'fbackup' looks for on the tape.
Regards!
...JRF...
This is expected. If you have a virgin tape, or one that wasn't last used with 'fbackup', then you will see warning "unable to read a volume header". This will result in a returncode of <4> for the fbackup execution as documented in the man pages. In fact, the <4> is the value in the second line.
If you use the same tape again and again for 'fbackup', you will see that it keeps track of the number of times a tape is used. This is part of the header that 'fbackup' looks for on the tape.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2001 08:13 AM
03-14-2001 08:13 AM
Re: fbackup errors (not the same in the "search")
Every tape being written by the fbackup program will have its own header information such as how many times such tape has been written for, so, if your tape is new for fbackup then you should see that warning, but next time the warning message should be gone.
~Philip
~Philip
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP