- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- fbackup error code = 2
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
05-23-2001 07:13 AM
05-23-2001 07:13 AM
fbackup error code = 2
Output from fbackup:
br_backup: Invoking fbackup. See /var/sam/log/br_log for details.
fbackup(1004): session begins on Wed May 23 04:00:01 2001
fbackup(3203): volume 1 has been used 15 time(s)
fbackup(3024): writing volume 1 to the output file /dev/rmt/c0t6d0BESTn
fbackup(3003): normal EOT
fbackup(3310): enter '^[yY]' when volume 2 is ready on /dev/rmt/c0t6d0BESTn,
or '^[nN]' to discontinue:
fbackup(3004): writer aborting
fbackup(1002): Backup did not complete : Reader or Writer process exit
Although all files are being backed up and volume 1 does not run out of space, I still get the error. What could be the problem?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2001 07:19 AM
05-23-2001 07:19 AM
Re: fbackup error code = 2
Your log is showing that you have ran out of space on the backup medium as it is asking for a second tape:-
fbackup(3003): normal EOT
fbackup(3310): enter '^[yY]' when volume 2 is ready on /dev/rmt/c0t6d0BESTn,
or '^[nN]' to discontinue:
fbackup(3004): writer aborting
fbackup(1002): Backup did not complete : Reader or Writer process exit
Check tape size against data and also look at what you are backing up dirs like /crash and /tmp do not need to be backed up.
HTH
Paula
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2001 07:22 AM
05-23-2001 07:22 AM
Re: fbackup error code = 2
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2001 07:33 AM
05-23-2001 07:33 AM
Re: fbackup error code = 2
Since you are running this from cron, there isn't a way to interact with fbackup, to do that you have to be running from SAM or interactively from the command line.
The best way to get around this would be to look at the data you are backing up and see if you can split it into a couple of different backups that fit on one tape each. If you have multiple tape drives, you can run one backup on one drive and the other on the second drive.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2001 07:35 AM
05-23-2001 07:35 AM
Re: fbackup error code = 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2001 07:39 AM
05-23-2001 07:39 AM
Re: fbackup error code = 2
Normal EOT (end of tape) means that up to the point of filling the current tape in the drive that the backup routine is ok, the fbackup routine will timeout on waiting for a 2nd tape hence the entry in log.
You have several choices.
1. Change the tape when fbackup requests it - ooohh
2. Reduce the ammount of data so that it all fits on one tape.
3. Fit a bigger tape drive.
4. Backup to disks overnight and then backup from these during the normal working day (tape change easier).
from man fbackup:-
The type of device used for backups can affect such things as media
expenses, ability to do unattended backups, and speed of the backup.
Using 36-track tapes will probably result in the highest performance,
but require user intervention for changing tapes. Both DLT and DDS
autochangers and libraries can provide unattended backups. A
magneto-optical autochanger can also provide an unattended backup for
a large system and long life media, however the media cost is high.
Lower cost and good performance can be achieved with a single DLT tape
drive, but multi-volume backups must be attended.
Paula