GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Recover vg01-2-3 information
Operating System - HP-UX
1847207
Members
3431
Online
110263
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
11-15-2001 10:01 AM
11-15-2001 10:01 AM
All.
10.20
Rclass
Jbod 10x9gb disks
My root disk crashed last week and I needed to re-install the o/s which is now complete.
Previously, my machine had some additional vg's defined. It was my understanding that the VG groups would still be instact after I re-installed my o/S.
Question is, how do I do that, if at all possible? I have a bdf from the previous installation.
Lastly, if it is too difficult, I can re-create the vg's and restore the data in about 2 days.
Thanks,
Nickd
10.20
Rclass
Jbod 10x9gb disks
My root disk crashed last week and I needed to re-install the o/s which is now complete.
Previously, my machine had some additional vg's defined. It was my understanding that the VG groups would still be instact after I re-installed my o/S.
Question is, how do I do that, if at all possible? I have a bdf from the previous installation.
Lastly, if it is too difficult, I can re-create the vg's and restore the data in about 2 days.
Thanks,
Nickd
Always learning
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2001 10:06 AM
11-15-2001 10:06 AM
Re: Recover vg01-2-3 information
Hi Nick,
If you have a vgcfgbackup from the old system, restore that to the new system and you can reclaim the Vg. Another choice is to do a "vgscan". This should rebuild your lvmtab file.
use "vgscan -v" . Do keep a copy of /etc/lvmtab before you run vgscan.
Hope this helps.
Regds
If you have a vgcfgbackup from the old system, restore that to the new system and you can reclaim the Vg. Another choice is to do a "vgscan". This should rebuild your lvmtab file.
use "vgscan -v" . Do keep a copy of /etc/lvmtab before you run vgscan.
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2001 10:19 AM
11-15-2001 10:19 AM
Solution
Hi Nick:
The data on your non-vg00 disks will be intact. Do a 'vgimport' do "reclaim" the disks. SAM can do this for you if you are uncomfortable with doing this via commandline.
Otherwise, look at the 'vgimport' man (1M) pages; essentially:
# vgimport -m mapfile -v -f infile vg_name
List the physical device files (/dev/dssk/cXtYdZ) in the ASCII file. In the ASCII place the logical volume names, one per line, like "lvol1", "lvol2", etc.
Regards!
...JRF...
The data on your non-vg00 disks will be intact. Do a 'vgimport' do "reclaim" the disks. SAM can do this for you if you are uncomfortable with doing this via commandline.
Otherwise, look at the 'vgimport' man (1M) pages; essentially:
# vgimport -m mapfile -v -f infile vg_name
List the physical device files (/dev/dssk/cXtYdZ) in the ASCII file
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2001 10:52 AM
11-15-2001 10:52 AM
Re: Recover vg01-2-3 information
Hi Nick,
If you have not re-used the disks that were previously used for vg01-3 then you can vgimport them easily. The data needed for vgimport is written on all the disks in the VG by LVM whenever something changes about the VG.
I presume you reloaded the OS on the same disks you had it on before (or if you replaced a disk because of the crash it was the same device path). If so, piece of cake.
If you don't have Ignite, you should get it. Rebuilding becomes a snap. You simply reload from a make_tape_recovery tape, re-mirror vg00 LVs, and vgimport the remaining VGs. Good stuff.
Darrell
If you have not re-used the disks that were previously used for vg01-3 then you can vgimport them easily. The data needed for vgimport is written on all the disks in the VG by LVM whenever something changes about the VG.
I presume you reloaded the OS on the same disks you had it on before (or if you replaced a disk because of the crash it was the same device path). If so, piece of cake.
If you don't have Ignite, you should get it. Rebuilding becomes a snap. You simply reload from a make_tape_recovery tape, re-mirror vg00 LVs, and vgimport the remaining VGs. Good stuff.
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