- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: SAM -fbackup exit code
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
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
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
тАО11-30-2005 01:53 PM
тАО11-30-2005 01:53 PM
I have a few automated fbackup schedule using SAM.
Some of the fbackup run with exit code=4, and some with exit code=2.
When check at the man page, it only say exit code=2 is Error, while Exit code=4 is Warning.
How can I find out what is the cause of my fbackup failure? Is it tape full? Is it bad media?
So far I have look into /var/adm/fbackupfiles, it also didn't state the cause of failure there.
Below is the example of error message at SAM:
Full backup started on mpcim1 : Thu Dec 1 05:39:00 mal 2005 (Scheduled Backup)
{ fbackup -0 -u -g /etc/sam/br/graphOEAa23245 -I /var/sam/log/br_index.full -c /etc/sam/br/fbackup_config -d /var/adm/fbackupfiles/dates -f /dev/rmt/0m } 2>&1
Full backup completed with warnings on mpcim1 : Thu Dec 1 08:38:45 mal 2005 .
Exit code = 4
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2005 02:38 PM
тАО11-30-2005 02:38 PM
Solutionrefer to similar cases:
http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000079971897
http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000080064976
btw, r u on 11.00?
regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2005 02:42 PM
тАО11-30-2005 02:42 PM
Re: SAM -fbackup exit code
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2005 03:02 PM
тАО11-30-2005 03:02 PM
Re: SAM -fbackup exit code
I wouldn't be too concerned about the exit codes of 4. That can be caused by using a new tape, or rather writing a new fbackup on a tape. (the tape doesn't have to be new.)
To check if you're running out of tape you can add a line the config file,
/etc/sam/br/fbackup_config in your case, to get a notice of a change tape request. Add a chgvol line with a script that will email you. Even if you're not around to switch tapes you'll at least know that causing problems with your backups.
Regards,
Tom
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2005 04:44 PM
тАО11-30-2005 04:44 PM
Re: SAM -fbackup exit code
How about exit code=2? what does it mean?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2005 06:06 PM
тАО11-30-2005 06:06 PM
Re: SAM -fbackup exit code
refer to this doc which shows some common causes for exit code 2:
http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000079312799
regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2005 07:05 PM
тАО11-30-2005 07:05 PM
Re: SAM -fbackup exit code
Thanks got the respond.
Is it conculded that the fbackup will just return exit code 0,1,2,4.
If I suspect the exit code=2 that i encountered is due to "requesting 2nd tape" . Will the system give me a prompt before the backup failed and time out?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2005 07:48 PM
тАО11-30-2005 07:48 PM
Re: SAM -fbackup exit code
there should be a warning/prompt, refer to this post:
http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=733451
regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2005 12:13 AM
тАО12-01-2005 12:13 AM
Re: SAM -fbackup exit code
If you're running the backup interactively from SAM you'll be prompted for another tape, but when the backup is scheduled via cron you will not get a prompt.
To check if you're running out of tape you can add a line the config file,
/etc/sam/br/fbackup_config in your case, to get a notice of a change tape request. Add a chgvol line with a script that will email you. Even if you're not around to switch tapes you'll at least know that causing problems with your backups.
Make a simple script to let you know
vi /usr/local/bin/tapechange
Add these lines
#!/usr/bin/ksh
echo "Tape change needed for backup" | \
mailx -s "Backup Alert" your_email_here
Make the script executable.
chmod 555 /usr/local/bin/tapechange
Then add a line to the fbackup configuration file to call then when a tape change is needed.
vi /etc/sam/br/fbackup_config
add this line
chgvol /usr/local/bin/tapechange
It will work, but you have to set it up.
Regards,
Tom