HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Issue with make_tape_recovery
Operating System - HP-UX
1833044
Members
2751
Online
110049
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
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
08-13-2003 01:24 PM
08-13-2003 01:24 PM
when i am running make_tape_recovery -i in graphical interactive mode to create diaster recovery tape for my rp8400 server , i am getting following error
======= 08/07/03 18:57:05 PDT Started /opt/ignite/bin/make_tape_recovery.
(Thu Aug 07 18:57:05 PDT 2003)
@(#) Ignite-UX Revision B.4.3.123
@(#) net_recovery (opt) $Revision: 10.609 $
* User interface starting.
NOTE: vgdisplay -v unsuccessful
NOTE: '' is not an absolute path
* User interface completed successfully.
NOTE: Detected entries in the defaults file at
/var/opt/ignite/recovery/defaults.
* Checking Versions of Ignite-UX filesets
NOTE: vgdisplay -v unsuccessful
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2003-08-07,18:57/system_cfg vg00
save_config: warning - /dev/vg00/crashb has an unmounted VxFS filesystem on it
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg00.mapfile /dev/vg00
vgexport: Volume group "/dev/vg00" is still active.
* Backing Up Volume Group /dev/vg12
* /usr/sbin/vgcfgbackup /dev/vg12
vgcfgbackup: Warning: couldn't query physical volume "/dev/dsk/c24t2d0":
The specified path does not correspond to physical volume attached to
this volume group
vgcfgbackup: Warning: couldn't query physical volume "/dev/dsk/c24t2d1":
The specified path does not correspond to physical volume attached to
this volume group
vgcfgbackup: Warning: couldn't query physical volume "/dev/dsk/c24t2d2":
The specified path does not correspond to physical volume attached to
In Graphical mode, i have selected /dev/vg00 (2 Internal HD 73 GB Mirrored )only.
"/dev/dsk/c24t2d2" devices are no longer existed on my server. It is SAN device. No longer on server. My guess is it is because make_tape_recovery use /etc/lvmtab to select volume group. I don`t have device mounted in /etc/fstab.
Thanks in advance for suggestion.
======= 08/07/03 18:57:05 PDT Started /opt/ignite/bin/make_tape_recovery.
(Thu Aug 07 18:57:05 PDT 2003)
@(#) Ignite-UX Revision B.4.3.123
@(#) net_recovery (opt) $Revision: 10.609 $
* User interface starting.
NOTE: vgdisplay -v unsuccessful
NOTE: '' is not an absolute path
* User interface completed successfully.
NOTE: Detected entries in the defaults file at
/var/opt/ignite/recovery/defaults.
* Checking Versions of Ignite-UX filesets
NOTE: vgdisplay -v unsuccessful
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2003-08-07,18:57/system_cfg vg00
save_config: warning - /dev/vg00/crashb has an unmounted VxFS filesystem on it
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg00.mapfile /dev/vg00
vgexport: Volume group "/dev/vg00" is still active.
* Backing Up Volume Group /dev/vg12
* /usr/sbin/vgcfgbackup /dev/vg12
vgcfgbackup: Warning: couldn't query physical volume "/dev/dsk/c24t2d0":
The specified path does not correspond to physical volume attached to
this volume group
vgcfgbackup: Warning: couldn't query physical volume "/dev/dsk/c24t2d1":
The specified path does not correspond to physical volume attached to
this volume group
vgcfgbackup: Warning: couldn't query physical volume "/dev/dsk/c24t2d2":
The specified path does not correspond to physical volume attached to
In Graphical mode, i have selected /dev/vg00 (2 Internal HD 73 GB Mirrored )only.
"/dev/dsk/c24t2d2" devices are no longer existed on my server. It is SAN device. No longer on server. My guess is it is because make_tape_recovery use /etc/lvmtab to select volume group. I don`t have device mounted in /etc/fstab.
Thanks in advance for suggestion.
Umang
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2003 01:34 PM
08-13-2003 01:34 PM
Solution
Hi,
You have an LVM issue. Ignite is trying to issue a vgcfgbackup of vg12 and it failed.
If you no longer need vg12, then you have to get rid of it from your lvmtab file. Either vgexport it or move lvmtab aside and recreate it with vgscan. Refer to the vgscan(1M) and vgexport(1M) man pages for further information about those commands.
If you still use vg12, then you need to fix the missing luns issue.
Note: You can issue the vgcfgbckup command outside of make_tape_recovery. Refer to the vgcfgbackup(1M) man page for further details.
Until you fix the LVM issues, you wont be able to successfully complete a make_tape_recovery.
Tim
You have an LVM issue. Ignite is trying to issue a vgcfgbackup of vg12 and it failed.
If you no longer need vg12, then you have to get rid of it from your lvmtab file. Either vgexport it or move lvmtab aside and recreate it with vgscan. Refer to the vgscan(1M) and vgexport(1M) man pages for further information about those commands.
If you still use vg12, then you need to fix the missing luns issue.
Note: You can issue the vgcfgbckup command outside of make_tape_recovery. Refer to the vgcfgbackup(1M) man page for further details.
Until you fix the LVM issues, you wont be able to successfully complete a make_tape_recovery.
Tim
Yesterday is history, tomorrow is a mystery, today is a gift. That's why it's called the present.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2003 07:58 AM
08-14-2003 07:58 AM
Re: Issue with make_tape_recovery
This is a LVM issue. Ignite backup does vgcfgbackup of all the volume groups. Volume group /dev/vg12 has issue. If /dev/dsk/c24t2dx devices are not connected then you can do vgreduce.
IT is great!
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 2025 Hewlett Packard Enterprise Development LP