- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Header indexes and du -sk output
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
12-09-2001 05:24 AM
12-09-2001 05:24 AM
I understand that the index size reported on a tape header represents the 'intended' amount of data fbackup will attempt to backup - but why does this not match the output from a 'du -sk' ?
What's the best way to determine just how much data fbackup will attempt to backup, prior to starting the backup process?
Many thanks
Darren
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2001 08:04 AM
12-09-2001 08:04 AM
Re: Header indexes and du -sk output
live free or die
harry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2001 09:22 AM
12-09-2001 09:22 AM
Re: Header indexes and du -sk output
Thanks for your reply.
We have over 200 unix servers and each has a full backup each week. Recently, many of these have been asking for a second tape (we use 120m DDS2's). Typically, the index size is somewhere around the 8Gb mark, but 'du -sk' returns up to 2Gb less than that.
Many thanks
Darren
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2001 09:56 AM
12-09-2001 09:56 AM
SolutionThe most likely cause would be inuse files that are recopied.
'fbackup' is designed to backup active filesystems. When a file is copied to tape, 'fbackup' makes note of its timestamp at the beginning of the transfer and compares it to the timestamp of the file *on disk* once it has been fully copied to tape. If the timestamps match, the tape copy for that file is "good". If the timestamps don't match the file on tape is marked as "bad" and another attempt is made to copy from disk to tape. This cycle of "note", "copy", "compare" is repeated 'maxretries' as specified by the 'config' file used with the 'fbackup' session (see 'man 1M fbackup'). The default number of retries is five.
Marking the file as "bad" on the tape allows 'frecover' to skip it as necessary. However, the penalty is that extra tape is used for every retry whether or not a good copy is ever achieved.
I personally like to run 'fbackup' with '-v'erbose logging redirected to a file from which I can extract warning messages like retries. Too, if any warning messages are generated during an 'fbackup' session, 'fbackup' will return a value of four (4).
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2001 11:18 AM
12-09-2001 11:18 AM
Re: Header indexes and du -sk output
I can understand how such retries would affect the amount of data physically written to tape, but would they affect the index size as reported in the tape volume header before any data has actually been written?
It would be nice if I could just run the section of the fbackup program which estimates how much data is to be backed up.
Many thanks again
Darren