- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- fbackup 1421
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
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
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
тАО08-14-2003 02:13 AM
тАО08-14-2003 02:13 AM
I have a problem with my backup history error 1421. The fbackup has not been set via sam and calls several config files the graph and fbackup_config which contains the following:
blocksperrecord 128
records 32
checkpointfreq 256
readerprocesses 2
maxretries 0
retrylimit 5000000
maxvoluses 100
I have looked in the /etc/sam/br_log which contains information up until June which is about when the problem appeared.
Can anyone advise me if I rename this and create a new br_log will this cure the problem?
Grace
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2003 02:19 AM
тАО08-14-2003 02:19 AM
Re: fbackup 1421
Looking at this link,
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xab988d77ef20d411b66300108302854d,00.html
It appears that you may just be able to rename the log for the graph file to resolve the problem (if the rename doesn't work on its own, you'll need to remove and re-add the backup).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2003 02:23 AM
тАО08-14-2003 02:23 AM
Re: fbackup 1421
fbackup(1421): no history is available for graph file /var/backup/graph_daily (below level 0)
rather than there error message:
(1421) no profile history is available for graph file
/etc/sam/br/graphQeAa03524
could you please explain
thanks
Grace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2003 02:29 AM
тАО08-14-2003 02:29 AM
Re: fbackup 1421
Try removing and recreating the device files;
steve STEEL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2003 02:37 AM
тАО08-14-2003 02:37 AM
SolutionThere's no particular problem with the file name (they're just using a different location).
If you rename /var/backup/graph_daily to /var/backup/graph_daily.save, then try again, the error may vanish.
If not, you'll need to remove the current backup entry from sam, then add it back in again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2003 02:39 AM
тАО08-14-2003 02:39 AM
Re: fbackup 1421
The error 1421 is likely to be caused by fbackup not being able to write into the file /var/adm/fbackupfiles/dates. Check that the dir /var/adm/fbackupfiles exists and is writeable.
If you're not using SAM, or br_backup (which is a backup script used by SAM) then it's unlikely that you'll be using br_log. Are you using fbackup directly from the command line, or perhaps in a script? If so, then it would be useful to capture the info into your own log.
regards,
Darren.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2003 03:32 AM
тАО08-14-2003 03:32 AM
Re: fbackup 1421
Thanks that has worked.
Grace