- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- make_recovery problem
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
Discussions
Discussions
Discussions
Forums
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
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-19-2000 01:11 PM
тАО12-19-2000 01:11 PM
#make_recovery -p -A -d /dev/rmt/0m
/var/opt/ignite/recovery/config.recover is created successfully on both machines.
#make_recovery -r -d /dev/rmt/0m
make_recovery(482) Call to system failed.
and
make_recovery(486) Call to system failed.
I would greatly appreciate any help!
Troy
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-19-2000 01:20 PM
тАО12-19-2000 01:20 PM
Re: make_recovery problem
that means don't rewind the tape when you use a configuration file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-19-2000 01:25 PM
тАО12-19-2000 01:25 PM
Re: make_recovery problem
http://my1.itrc.hp.com/cm/QuestionAnswer/1,1150,0xfca583667c40d4118feb0090279cd0f9!0,00.html
/rcw
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-20-2000 06:24 PM
тАО12-20-2000 06:24 PM
Re: make_recovery problem
The reason for this is that it will write the things needed to boot the system to the beginning of the tape, and then after that it uses pax to write the rest of your backup. If you don't use the no-rewind device you could potentially have a non-bootable make_recovery tape, which wouldn't do you much good.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-21-2000 04:11 AM
тАО12-21-2000 04:11 AM
Re: make_recovery problem
/var/opt/ignite/logs/makrec.log1
and see if vgcfgbackup has failed.
Possibly your /etc/lvmtab is out of date.
If you found something like this you have to check your LVM.
Ie: recreate /etc/lvmtab with
mv /etc/lvmtab /etc/lvmtab.old
vgscan -v
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-21-2000 04:28 AM
тАО12-21-2000 04:28 AM
Solution- The volumegroup given to be incorrect, in /var/opt/ignite/logs/makrec.log1.
Check with:
- strings /etc/lvmtab
- vgdisplay -v /dev/vg??
If it comes back with an error-message, couldn't query ....
If the above is the case it is possible that you need to run:
- vgreduce -f /dev/vg??
- mv /etc/lvmtab /etc/lvmtab.old
- vgscan -v
- vgcfgbackup /dev/vg??
Good Luck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-21-2000 06:32 AM
тАО12-21-2000 06:32 AM
Re: make_recovery problem
fighting with it.
Troy