- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: fbackup - frecover 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
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
тАО06-18-2001 07:00 AM
тАО06-18-2001 07:00 AM
We made a fbackup of a system using an external raid. This external raid has two disk
/dev/dsk/c1t6d0 and /dev/dsk/c1t5d0
As the RAID system failed we starting use two internal wide SCSI disk
/dev/dsk/c0t6d0 and /dev/dsk/c0t5d0
the problem we have is that the volume group vg00 is referencing to the old disks. /etc/lvmtab.
ant we the system start the savecore fails too.
I don't know if there is other application proccess who references directly to the hardware devices.
Can someone giveme some advice with this problem?
Thanks
Sergio
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2001 09:08 AM
тАО06-18-2001 09:08 AM
Re: fbackup - frecover problem
#mv /etc/lvmtab /etc/lvmtab.old
#vgscan -v
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2001 10:13 AM
тАО06-18-2001 10:13 AM
Re: fbackup - frecover problem
Thanks for your help. Reading other messages I found your solution will work for the VG problem. I going to try your solution in a an hour , but for saving time Is this solution going to solve the other problem? ie: references for savecore? and all other application, proccesses (if there are) wich are referencing to these devices?
Thanks
Sergio
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2001 10:46 AM
тАО06-18-2001 10:46 AM
Re: fbackup - frecover problem
I tryed your suggestion and now the command lvdisplay works properly, but there is an starting problem yet.
When the system startup the savecore commands fail
# savecore
savecore: open failed /dev/dsk/c1t6d0: No such device or address
savecore: could not open dump
who can I solve this error? Can be others proccess wich are still referencing to c1txd0
Regards
Sergio
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2001 04:54 AM
тАО06-20-2001 04:54 AM
Re: fbackup - frecover problem
On HPUX11
man -k dump | grep crash.
That will lead you to crashconf(1M).
crashconf -v will tell you which dump device is used, and you can change that to your new disk.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2001 01:32 PM
тАО06-20-2001 01:32 PM
Re: fbackup - frecover problem
This is an HP-UX 10.20
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2001 02:09 PM
тАО06-20-2001 02:09 PM
SolutionAnything pointing to the old disks (like your dump device, apparently) will need to be repointed. Do man pages on each comand before playing. In particular, make sure you understand the difference between a boot volume (/stand) and root volume (/).