- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- pax: The archive is empty.
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-18-2005 08:10 PM
12-18-2005 08:10 PM
pax: The archive is empty.
---------------------------------------------
# First rewind tape and then find end of data
mt -f /dev/rmt/0mn rew
mt -f /dev/rmt/0mn eod
# Write to tape
pax -wv -f /dev/rmt/0mn filenames
---------------------------------------------
When listing the tape an empty archive appears in the beginning and between between each daily written archive:
$ mt -f /dev/rmt/0mn rew
$ pax -v -f /dev/rmt/0mn
pax: The archive is empty.
$ pax -v -f /dev/rmt/0mn
tape archive day x being listed...
$ pax -v -f /dev/rmt/0mn
pax: The archive is empty.
$ pax -v -f /dev/rmt/0mn
tape archive day x+1 being listed...
etc...
Is it ok that pax report the space between two archives as an empty archive?
The pax based script is used to backup data from a samba server, is the pax command a good choice for this purpose?
Lars Bylander
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2005 08:31 PM
12-18-2005 08:31 PM
Re: pax: The archive is empty.
Can you check with tar also with your steps? is there any difference.
-Muthu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2005 08:41 PM
12-18-2005 08:41 PM
Re: pax: The archive is empty.
$ mt -f /dev/rmt/0mn rew
$ tar -tf /dev/rmt/0mn
Tar: blocksize = 0; broken pipe?
$ tar -tf /dev/rmt/0mn
tape archive day x being listed
$ tar -tf /dev/rmt/0mn
Tar: blocksize = 0; broken pipe?
$ tar -tf /dev/rmt/0mn
tape archive day x+1 being listed
-Lars
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2005 09:01 PM
12-18-2005 09:01 PM
Re: pax: The archive is empty.
-Arun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2005 10:56 PM
12-18-2005 10:56 PM
Re: pax: The archive is empty.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2005 12:03 AM
12-19-2005 12:03 AM
Re: pax: The archive is empty.
Now all this is to preface the technique being used to append data. It might work but you'll have to map the appended archives very carefully. DO NOT use this technique for production until you've thoroughly tested the technique. The best way is to save a very short series of files, perhaps 3-4 text files, then append to the backup 3-4 times. Now test what is on the tape by doing a directory list using the no-rewind device. You may see that each backup set is followed by a null data block which is the separator between archives. Thusyou would have to position the tape forward one additional file mark (mt ... fsf).
For several decades, sysadmins have been trying to save tapes by appending backups to long tapes with disasterous results. While it may work for a while, a single mistake (ie, a user accidently writes to the beginning of multi-backup tape) will destroy *everything* on the tape. Modern tape drives (DDS, DLT, Ultrium, etc) write a hardware-generated code at the end of writing, regardless of where the tape is positioned. This is done to prevent despooling (run off the end of the tape) but is has a chilling effect on all backups, especially multiple appends: there is no way to position beyond the hardware marker!!
So the 20 backups appended to the tape are destroyed when someone forgets to position the tape and writes to the beginning. There is no command that will position the tape past this mistake. (actually, data recovery companies have special tape drives and programs to recover data, but they are very expensive services).
So to answer your last question, pax (and tar and cpio) can all be used to backup your data files. As manetioned, there are limits to the maximum filesize that can be saved (2Gb or 8Gb for patched tar). fbackup is the preferred non-commercial tool. fbackup explicitly prevents multiple backups on the same tape by always issuing a rewind from within the program.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2005 07:39 AM
12-20-2005 07:39 AM
Re: pax: The archive is empty.
Writing to the tape:
$ pax -wv -f /dev/rmt/0mn file1 file2 file3
$ pax -wv -f /dev/rmt/0mn file1 file2 file3
$ mt -f /dev/rmt/0mn rew
$ mt -f /dev/rmt/0mn eod
$ pax -wv -f /dev/rmt/0mn file1 file2 file3
Listing the tape contents:
$ mt -f /dev/rmt/0mn rew
$ pax -v -f /dev/rmt/0mn
file1 file2 file3
$ pax -v -f /dev/rmt/0mn
file1 file2 file3
$ pax -v -f /dev/rmt/0mn
pax: The archive is empty.
$ pax -v -f /dev/rmt/0mn
file1 file2 file3
It seems that it works appending archives to the tape. If the tape has been rewound and mt ... eod is executed before writing to the tape an empty archive will appear before the appended archive (as I previously reported).
I do not fullly understand the hardware written code concept? It must be possible to write over the hardware code to be able to reuse a tape writing more bytes the second time than the first time!
-Lars
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2005 08:33 AM
12-20-2005 08:33 AM
Re: pax: The archive is empty.
As you demonstrated, you can write an archve, then write another archive without rewinding, thereby appending to the tape. This can be done all at once or over several days. The hardware code only comes into play when you have, say 10 appended archives, a mistake is made and now there is a new archuve at the beginning of the tape. You can't skip past that new archive and see whatever is left of the 10 archives.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-29-2005 05:03 AM
12-29-2005 05:03 AM
Re: pax: The archive is empty.
Thanks for the valueable comments, the hardware code is important to know about. I will have a script running once per day appending data to the tape. By having the script rewind and seek end of data misstakes writing over older archives are hopefully avoided. I will also carefully follow up that data is correctly appended to the tape. Thanks again - Lars