- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: make_tape_recovery error
Operating System - HP-UX
1753731
Members
4675
Online
108799
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
тАО05-16-2005 11:13 PM
тАО05-16-2005 11:13 PM
HP-UX 11.11 on a B1000.
Ignite version B.3.3.116
The machine has one disk in one volume group, so the Ignite backup is actually a full backup as well. The tape device is a HP C1533A
I Ran ...
# make_tape_recovery -A -v -a /dev/rmt/1mn
The last few lines of the output are as follows ...
* Preparing to create system archive
* Archiving contents of XXXXX via tar image to local device /dev/rmt/1mn
awk: Cannot divide by zero.
The input line number is 21815
The source line number is 2.
* Creation of system archive complete
* Cleaning up old configuration file directories
====== 05/17/05 12:00:49 BST make_tape_recovery completed successfully!
So my questions are
(1) Why does it say it completed succesfully, when it also reported an error message?
(2) What does the error message mean, i.e. how can I tell what is causing the problem?
Upon examining the pax archive after the LIF on the tape, I discovered that a lot of /var files have not been backed up. So much for 'completed successfully!'
I have run make_tape_recovery before on this machine and it has worked fine up until now. I regressed to this version of Ignite because the later version didn't create a bootable image that would actually boot, so don't tell me to install the latest version of Ignite!
Ignite version B.3.3.116
The machine has one disk in one volume group, so the Ignite backup is actually a full backup as well. The tape device is a HP C1533A
I Ran ...
# make_tape_recovery -A -v -a /dev/rmt/1mn
The last few lines of the output are as follows ...
* Preparing to create system archive
* Archiving contents of XXXXX via tar image to local device /dev/rmt/1mn
awk: Cannot divide by zero.
The input line number is 21815
The source line number is 2.
* Creation of system archive complete
* Cleaning up old configuration file directories
====== 05/17/05 12:00:49 BST make_tape_recovery completed successfully!
So my questions are
(1) Why does it say it completed succesfully, when it also reported an error message?
(2) What does the error message mean, i.e. how can I tell what is causing the problem?
Upon examining the pax archive after the LIF on the tape, I discovered that a lot of /var files have not been backed up. So much for 'completed successfully!'
I have run make_tape_recovery before on this machine and it has worked fine up until now. I regressed to this version of Ignite because the later version didn't create a bootable image that would actually boot, so don't tell me to install the latest version of Ignite!
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2005 11:18 PM
тАО05-16-2005 11:18 PM
Solution
Hi Stephen,
Check if you can open next doc.
http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062921978
Best regards,
Robert-Jan
Check if you can open next doc.
http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062921978
Best regards,
Robert-Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2005 11:22 PM
тАО05-16-2005 11:22 PM
Re: make_tape_recovery error
Stephen,
A couple of thoughts. First, that version of Ignite is quite old. The current version is C.6.1x. I would download and install that from here:
http://www.docs.hp.com/en/IUX/download.html
Second, to get a complete backup, I would use the following syntax:
make_tape_recovery -a /dev/rmt/1mn -I -v -x inc_entire=vg00
Unless you specify the "-x inc_entire" option, Ignite just backs up a selected list of essential files.
Pete
Pete
A couple of thoughts. First, that version of Ignite is quite old. The current version is C.6.1x. I would download and install that from here:
http://www.docs.hp.com/en/IUX/download.html
Second, to get a complete backup, I would use the following syntax:
make_tape_recovery -a /dev/rmt/1mn -I -v -x inc_entire=vg00
Unless you specify the "-x inc_entire" option, Ignite just backs up a selected list of essential files.
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2005 11:30 PM
тАО05-16-2005 11:30 PM
Re: make_tape_recovery error
I thought that the -A flag meant the entire root VG was included.
That certainly explains (2), but not why HP can't get their basic error handling right.
Yes I know it's an old version of Ignite, but as I said, the later version I tried created a bootable image that wouldn't boot. I believe that latter problem was due to an IDE patch that had been installed, which wrecked kernels from then on, thus making any new kernel unbootable, so maybe (now that I've uninstalled the rogue patch - thanks HP!) I'll upgrade the Ignite version.
That certainly explains (2), but not why HP can't get their basic error handling right.
Yes I know it's an old version of Ignite, but as I said, the later version I tried created a bootable image that wouldn't boot. I believe that latter problem was due to an IDE patch that had been installed, which wrecked kernels from then on, thus making any new kernel unbootable, so maybe (now that I've uninstalled the rogue patch - thanks HP!) I'll upgrade the Ignite version.
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