- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Recover all VG's after server crash.
Operating System - HP-UX
1819933
Members
3499
Online
109607
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
Discussions
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
тАО01-06-2011 03:14 PM
тАО01-06-2011 03:14 PM
Recover all VG's after server crash.
I am looking for help to rebuild the server after root disk crash.
1. there are 3 internal and 3 external disks.
2. No information about the VG's
I have replaced the root disk rebuild the server with ignite image of similar server.
How to recover all VG's without data lose.
I am eagerly waiting for your valuable reply.
Thanks and regards
Santhosh
1. there are 3 internal and 3 external disks.
2. No information about the VG's
I have replaced the root disk rebuild the server with ignite image of similar server.
How to recover all VG's without data lose.
I am eagerly waiting for your valuable reply.
Thanks and regards
Santhosh
santhosh
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2011 03:36 PM
тАО01-06-2011 03:36 PM
Re: Recover all VG's after server crash.
Hi:
> ...rebuild the server with ignite image of similar server.
Similar != same
...so I suggest that you use 'vgscan' in preview mode to expose the missing volume group devices. See the manpages for 'vgscan' for the options appropriate for your release. Having noted the physical devices associated with each volume group, use 'vgimport' to update the '/etc/lvmtab' (or '/etc/lvmtab_p').
If you don't have a mapfile (which appears to be the case), your logical volumes will be named 'lvol1', 'lvol2', etc. for the first, second, etc. logical volume on each volume group. These names can easily be changed after-the-fact, if necessary.
The extra work you are going to encounter, should underscore the value of mirrored disks together with Ignite recovery images from *every* server that you consider a production one.
Regards!
...JRF...
> ...rebuild the server with ignite image of similar server.
Similar != same
...so I suggest that you use 'vgscan' in preview mode to expose the missing volume group devices. See the manpages for 'vgscan' for the options appropriate for your release. Having noted the physical devices associated with each volume group, use 'vgimport' to update the '/etc/lvmtab' (or '/etc/lvmtab_p').
If you don't have a mapfile (which appears to be the case), your logical volumes will be named 'lvol1', 'lvol2', etc. for the first, second, etc. logical volume on each volume group. These names can easily be changed after-the-fact, if necessary.
The extra work you are going to encounter, should underscore the value of mirrored disks together with Ignite recovery images from *every* server that you consider a production one.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2011 05:49 PM
тАО01-06-2011 05:49 PM
Re: Recover all VG's after server crash.
Hi ,
After crash you can follow the steps as below.
Please find the example below.
when you run #vgscan -p it will tell you which and all PVs are part of single volume group.
# vgscan -p
Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c2t0d0
======================
# mkdir /dev/sooraj
# mknod /dev/sooraj/group c 64 0x010000
# vgimport /dev/sooraj /dev/dsk/c2t0d0
vgimport: Volume group "/dev/sooraj" has been successfully created.
Warning: A backup of this volume group may not exist on this machine.
Please remember to take a backup using the vgcfgbackup command after activating the volume group.
# vgchange -a y sooraj
Activated volume group
Volume group "sooraj" has been successfully changed.
===============================
Please note that the LV names will be created as /dev/vgname/lvol1 lvol2 lvol3
If you need the exact name you should have map file created with -m option with vgexport comand.
==> How ever you can mount the filesystems using the defualt LV name and rename later using #mv command to /dev/vgname/rlvol and lvol to the new name.
Regards,
Sooraj
After crash you can follow the steps as below.
Please find the example below.
when you run #vgscan -p it will tell you which and all PVs are part of single volume group.
# vgscan -p
Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c2t0d0
======================
# mkdir /dev/sooraj
# mknod /dev/sooraj/group c 64 0x010000
# vgimport /dev/sooraj /dev/dsk/c2t0d0
vgimport: Volume group "/dev/sooraj" has been successfully created.
Warning: A backup of this volume group may not exist on this machine.
Please remember to take a backup using the vgcfgbackup command after activating the volume group.
# vgchange -a y sooraj
Activated volume group
Volume group "sooraj" has been successfully changed.
===============================
Please note that the LV names will be created as /dev/vgname/lvol1 lvol2 lvol3
If you need the exact name you should have map file created with -m option with vgexport comand.
==> How ever you can mount the filesystems using the defualt LV name and rename later using #mv command to /dev/vgname/rlvol and lvol to the new name.
Regards,
Sooraj
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity" - Dennis Ritchie
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
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP