- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- make_tape_recovery and 2GB file size limitation
Operating System - HP-UX
1752734
Members
5563
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО02-28-2002 10:35 AM
тАО02-28-2002 10:35 AM
I think I know the answer to this one (that I'm outta luck) but thought I'd check anyway. We've got a 4GB Oracle DB file that fails to be written to tape via make_tape_recovery (everything else goes to tape just fine). The error:
WARNING: Skipping file '/users/oracle/oradata/ora/plant.dbf' because it is
larger than 2GB, which is not supported. This file should be
backed-up with your normal system backup -- Value too large to be
stored in data type (errno = 72)
WARNING: list_expander returned a warning,please check the log file.
(I'll guess the list_expander error is related)
Anyway, this is on an HP L1000, HPUX 11.00 (64-bit), largefiles are enabled on this VxFS system. Using IgniteUX B.3.5.89.
Have done a fair amount of research that seems to indicate pax not supporting >2GB files (and that make_tape_recovery uses pax). Nonetheless, want to see if anyone's come up with a workaround.
Thanks,
Mike
WARNING: Skipping file '/users/oracle/oradata/ora/plant.dbf' because it is
larger than 2GB, which is not supported. This file should be
backed-up with your normal system backup -- Value too large to be
stored in data type (errno = 72)
WARNING: list_expander returned a warning,please check the log file.
(I'll guess the list_expander error is related)
Anyway, this is on an HP L1000, HPUX 11.00 (64-bit), largefiles are enabled on this VxFS system. Using IgniteUX B.3.5.89.
Have done a fair amount of research that seems to indicate pax not supporting >2GB files (and that make_tape_recovery uses pax). Nonetheless, want to see if anyone's come up with a workaround.
Thanks,
Mike
System Administrator
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-28-2002 11:13 AM
тАО02-28-2002 11:13 AM
Solution
You are correct in that pax, which is what make_tape_recovery uses, does not support files larger than 2GB. There's no workaround for that.
Now what you could possibly do is make a copy of your 4GB file and then try gzip'ing or compressing it and see if that takes it under the 2GB limit. If so, when you restore from your tape, you just uncompress or gunzip it.
Otherwise, you'll have to create another tape that is an fbackup of your DB file and restore it after you've restored from the make_tape_recovery tape.
Now what you could possibly do is make a copy of your 4GB file and then try gzip'ing or compressing it and see if that takes it under the 2GB limit. If so, when you restore from your tape, you just uncompress or gunzip it.
Otherwise, you'll have to create another tape that is an fbackup of your DB file and restore it after you've restored from the make_tape_recovery tape.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-28-2002 12:03 PM
тАО02-28-2002 12:03 PM
Re: make_tape_recovery and 2GB file size limitation
Thank you Patrick, that's what I was afraid of. Luckily in our case, that 4GB file is recreated by Oracle if there's ever a problem so it's not imperative that we actually archive it or back it up - but it did raise a red flag for us. We may in the future still have to deal with 2GB+ files that MUST be backed up or archived. In which case, we'd turn to your gzip/fbackup suggestions.
Of course the rhetorical question is when will HP fix tar/pax/cpio/ftio (or, maybe just make newer versions of them like tar64/pax64/cpio64/ftio64), so they'll support those 2GB+ files. Or, make it so make_tape_recovery uses fbackup instead (which does support 2GB+ file sizes).
Thanks again,
Mike
Of course the rhetorical question is when will HP fix tar/pax/cpio/ftio (or, maybe just make newer versions of them like tar64/pax64/cpio64/ftio64), so they'll support those 2GB+ files. Or, make it so make_tape_recovery uses fbackup instead (which does support 2GB+ file sizes).
Thanks again,
Mike
System Administrator
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP