- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- fbackup problem
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
01-24-2005 09:24 PM
01-24-2005 09:24 PM
fbackup problem
Ihave make a full backup with the command
fbackup -f /dev/rmt/0m -u0g -I index.full
to restaure I fount this message:
>
># frecover -f /dev/rmt/0m -I index.full
>
>frecover(2105): did not find expected file marker
>
>frecover(5419): checksum on volume header is incorrect.
>
>frecover(5420): not an fbackup volume; magic value is incorrect
>
>frecover(2105): did not find expected file marker
>
>frecover(5412): Do you wish to try to salvage this volume? (^[yY]/^[
I need a help
KUZO
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2005 09:27 PM
01-24-2005 09:27 PM
Re: fbackup problem
your command looks wrong as you do not specify a -i to include files, and if you are trying to use the graph file, you have not specififed a graph file to read.
Also add in the -v option to see what is backed up
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2005 12:45 AM
01-25-2005 12:45 AM
Re: fbackup problem
chmod o-rw /dev/rmt/*
Tape backups are too important to allow ordinary users to write (or even read) them.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2005 01:09 AM
01-25-2005 01:09 AM
Re: fbackup problem
hi,
Actualy the tape work
After the backup I was able to read the tape with getlist of sam.
Now I can't do this a again.
Is the tape corrupted or I can recover it
If a make a backup with
fbackup -f /dev/rmt/0m -u0g -I index.full
Can I recover it with sam?
KSF
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2005 02:37 AM
01-25-2005 02:37 AM
Re: fbackup problem
fbackup -f /dev/rmt/0m -u0g -I index.full
is incorrect. The -g option MUST be followed by the name of a file containing lines such as:
i /usr
e /usr/lib
i /opt
and so on. The fbackup command above would have looked at -u0g -I and be quite confused as to what to do. If you meant to take a full backup, you must use the -i option instead. While you can combine options together (-u -0 -g is the same as -u0g), it can be confusing when an option requires an argument. To create a full backup, use this command:
fbackup -f /dev/rmt/0m -u -0 -v -i / -I /var/tmp/index.full
Note that index.full will be written to whatever directory you are currently in--not a good idea. Use a fullpath (ie, /var/tmp) to specify exactly where to write the index.
Bill Hassell, sysadmin