HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Importing VG from a failed server
Operating System - HP-UX
1837212
Members
2347
Online
110115
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
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
10-18-2010 08:35 PM
10-18-2010 08:35 PM
Importing VG from a failed server
Guys,
I'm trying to assist one of my friend here to recover data from a failed server.
The server in question is a RP5430 running HP-UX 11.11. Both of the internal disks failed meaning I can't boot into OS. The latest WORKING make_tape_recovery backup tape was made somewhere in late 2009. There are 4 LUNs assigned to this server from an EMC CX3 storage.
What we did so far was:
1. Get an almost identical server up and running.
2. Install tape drive and FC HBA
3. Restore from make_tape_recovery.
4. The system is up and running so far.
-The make_tape_recovery was made BEFORE the LUNs were assigned to this server.
a) How do i recover or import data from the EMC LUNs? I don't have the LVM map and I don't know what VGxxx is inside the EMC storage? Is it possible to import data from SAN without knowing anything related to the LVM or VG config/setup?
Thank you for your kind assistance
I'm trying to assist one of my friend here to recover data from a failed server.
The server in question is a RP5430 running HP-UX 11.11. Both of the internal disks failed meaning I can't boot into OS. The latest WORKING make_tape_recovery backup tape was made somewhere in late 2009. There are 4 LUNs assigned to this server from an EMC CX3 storage.
What we did so far was:
1. Get an almost identical server up and running.
2. Install tape drive and FC HBA
3. Restore from make_tape_recovery.
4. The system is up and running so far.
-The make_tape_recovery was made BEFORE the LUNs were assigned to this server.
a) How do i recover or import data from the EMC LUNs? I don't have the LVM map and I don't know what VGxxx is inside the EMC storage? Is it possible to import data from SAN without knowing anything related to the LVM or VG config/setup?
Thank you for your kind assistance
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2010 09:44 PM
10-18-2010 09:44 PM
Re: Importing VG from a failed server
hi,
Do assign the same EMC LUNs to the new server. Recognize all the LUNs in newserver from ioscan.
#ioscan -fnKC disk
Create a script with the following contents to get the VG info. Here created the script in filename /usr/bin/vgid.
# cat /usr/bin/vgid
echo " Disk Name CPU ID PV ID CPU ID VG ID"
echo " ---------------------------------------------------------"
for i in `ioscan -FnkCdisk | grep dsk`
do
echo $i
done | grep rdsk |while read DSKNAME
do
echo "Disk : $DSKNAME `xd -An -j8200 -N16 -tx $DSKNAME 2> /dev/null || echo --- Failed to read. Please check`"
echo " "
done | sort -k 7 | grep Disk | sed 's/rdsk/dsk/'
Change the permission to this script file using below command.
# chmod a+x /usr/bin/vgid (this command will add execute permission for all users)
Execute the script
# vgid
From the output of above, number of VG and associated LUNs (PV) can be identified by VGID. VGID is unique for each Volume Group. So now the VG configuration can be collected and conclude that which LUN (PV) belong to which VG.
Then go for vgimport for each volume group with the associated LUNs (PV).
# mkdir /dev/vgnn
# mknod /dev/vgnn/group c 64 0xhh0000
vgimport -v /dev/vgnn pvanmes assosiated with vgnn
Here all LVs under this vgnn are getting created in default names like LV1 and LV2... etc.
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
#fstyp LVname
#mkdir DIR
#mount LVname DIR
Add the entries in /etc/fstab.
Repeat the each steps to all VGs.
#fstyp /dev/vg01/lvol1
Reg \ Vel
Do assign the same EMC LUNs to the new server. Recognize all the LUNs in newserver from ioscan.
#ioscan -fnKC disk
Create a script with the following contents to get the VG info. Here created the script in filename /usr/bin/vgid.
# cat /usr/bin/vgid
echo " Disk Name CPU ID PV ID CPU ID VG ID"
echo " ---------------------------------------------------------"
for i in `ioscan -FnkCdisk | grep dsk`
do
echo $i
done | grep rdsk |while read DSKNAME
do
echo "Disk : $DSKNAME `xd -An -j8200 -N16 -tx $DSKNAME 2> /dev/null || echo --- Failed to read. Please check`"
echo " "
done | sort -k 7 | grep Disk | sed 's/rdsk/dsk/'
Change the permission to this script file using below command.
# chmod a+x /usr/bin/vgid (this command will add execute permission for all users)
Execute the script
# vgid
From the output of above, number of VG and associated LUNs (PV) can be identified by VGID. VGID is unique for each Volume Group. So now the VG configuration can be collected and conclude that which LUN (PV) belong to which VG.
Then go for vgimport for each volume group with the associated LUNs (PV).
# mkdir /dev/vgnn
# mknod /dev/vgnn/group c 64 0xhh0000
vgimport -v /dev/vgnn pvanmes assosiated with vgnn
Here all LVs under this vgnn are getting created in default names like LV1 and LV2... etc.
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
#fstyp LVname
#mkdir DIR
#mount LVname DIR
Add the entries in /etc/fstab.
Repeat the each steps to all VGs.
#fstyp /dev/vg01/lvol1
Reg \ Vel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2010 03:23 AM
10-19-2010 03:23 AM
Re: Importing VG from a failed server
assign the disks to the new server , then do
a ioscan -fnC disk to check whether the disks are attached to the server or not.
Then do a vgscan to scan for the disks on the server , it will prompt you to create a vg and import them .
a ioscan -fnC disk to check whether the disks are attached to the server or not.
Then do a vgscan to scan for the disks on the server , it will prompt you to create a vg and import them .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2010 06:24 PM
10-19-2010 06:24 PM
Re: Importing VG from a failed server
Hi,
Do you have any idea how may vg was there earlier??
you can do vgscan and try.
Chandra
Do you have any idea how may vg was there earlier??
you can do vgscan and try.
Chandra
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