GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Ignite "make_recovery" verification
Operating System - HP-UX
1846973
Members
4585
Online
110257
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
Forums
Discussions
Discussions
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
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-21-2002 01:25 PM
02-21-2002 01:25 PM
Hello Unix world,
Is there a way to verify my Ignite,
"make_recovery" tape to ensure it's a good
tape ? I have had problems where I received
a message "Completed successfully" but when I
attempted to restore the system I had problems.
I have utilized the following commands in the
past to verify if tape is good, but the "/tmp/recovelif" file always has some "failed / error" messages even when the tape is good ?
# mt -t /dev/rmt/0m rew ( 3 times )
# dd if=/dev/rmt/0mn of=/tmp/recovelif bs=2048
# strings /tmp/recovelif | more
# mt -t /dev/rmt/0mn fsf 1
# tar -tvf /dev/rmt/0m
Just want to know if anyone has a successful way of checking and knowing thae tape is good
Is there a way to verify my Ignite,
"make_recovery" tape to ensure it's a good
tape ? I have had problems where I received
a message "Completed successfully" but when I
attempted to restore the system I had problems.
I have utilized the following commands in the
past to verify if tape is good, but the "/tmp/recovelif" file always has some "failed / error" messages even when the tape is good ?
# mt -t /dev/rmt/0m rew ( 3 times )
# dd if=/dev/rmt/0mn of=/tmp/recovelif bs=2048
# strings /tmp/recovelif | more
# mt -t /dev/rmt/0mn fsf 1
# tar -tvf /dev/rmt/0m
Just want to know if anyone has a successful way of checking and knowing thae tape is good
Learn More
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2002 01:28 PM
02-21-2002 01:28 PM
Solution
Hi Jerry,
Installaing the OS on some other system using the make_recovery archive is the only sure way of knowing whether the tape is good or bad.
Other than that the test you have done are the only way to generally accept that the tape is good.
# mt -t /dev/rmt/0mn fsf 1
# tar -tvf /dev/rmt/0m
Hope this helps.
regds
Installaing the OS on some other system using the make_recovery archive is the only sure way of knowing whether the tape is good or bad.
Other than that the test you have done are the only way to generally accept that the tape is good.
# mt -t /dev/rmt/0mn fsf 1
# tar -tvf /dev/rmt/0m
Hope this helps.
regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2002 01:54 PM
02-21-2002 01:54 PM
Re: Ignite "make_recovery" verification
I would first check the log file freom the Ignite backup (/var/opt/ignite/logs/makrec.logxx) to see if there are any errors.
You can also use lifls or lifcp to examine the boot LIF on the disk, however I recommend booting from the make_recovery tape and interrupting the boot sequence before the non-interactive recovery starts and then abort the install. This will verify whether the first image on the tape is actually bootable.
Aftet you confirm that the tape is bootable I would use the the mt and tat commands to verify the the tar archive of the OS and other files that may have been included by your options in make_recovery.
# mt -f /dev/rmt/0mn rew
# mt -f /dev/rmt/0mn fsf 1
# tar tvf /dev/rmt/0m
Elizabeth
You can also use lifls or lifcp to examine the boot LIF on the disk, however I recommend booting from the make_recovery tape and interrupting the boot sequence before the non-interactive recovery starts and then abort the install. This will verify whether the first image on the tape is actually bootable.
Aftet you confirm that the tape is bootable I would use the the mt and tat commands to verify the the tar archive of the OS and other files that may have been included by your options in make_recovery.
# mt -f /dev/rmt/0mn rew
# mt -f /dev/rmt/0mn fsf 1
# tar tvf /dev/rmt/0m
Elizabeth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2002 01:58 PM
02-21-2002 01:58 PM
Re: Ignite "make_recovery" verification
Hi Jerry,
The best method is to use the tape. Not very practical though.
Use copy_boot_tape:
copy_boot_tape -u /dev/rmt/0mn -b -d /target_dir
/target_dir needs to be large enough for the bootimage file that will be copied from the tape. It will be named bootimage. On my servers that's about 60MB.
copy_boot_tape can also be used to extract the system archive from the tape (with -a option) or both the bootimage and system archive. See man copy_boot_image for more info.
As already said, to extract files from the system archive (not the boot image), rewind the tape, fsf 1 file, then either use tar or pax.
Darrell
The best method is to use the tape. Not very practical though.
Use copy_boot_tape:
copy_boot_tape -u /dev/rmt/0mn -b -d /target_dir
/target_dir needs to be large enough for the bootimage file that will be copied from the tape. It will be named bootimage. On my servers that's about 60MB.
copy_boot_tape can also be used to extract the system archive from the tape (with -a option) or both the bootimage and system archive. See man copy_boot_image for more info.
As already said, to extract files from the system archive (not the boot image), rewind the tape, fsf 1 file, then either use tar or pax.
Darrell
"What, Me Worry?" - Alfred E. Neuman (Mad Magazine)
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.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP