- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Shipping internal drives between servers
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
Forums
Discussions
Discussions
Forums
Discussions
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
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
10-24-2008 09:03 AM
10-24-2008 09:03 AM
rp4440
hp-ux 11.11
Anyone have a procedure for writing data to an hot pluggable internal hp drive, removing and shipping the drive cross country and then inserting this drive into another hp server and reading the data?
Please, no responses about nfs, ftp, tapes etc.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2008 09:17 AM
10-24-2008 09:17 AM
Re: Shipping internal drives between servers
Why not creating a VG and a LVOL, wite the data to this lvol and then export the VG?
Now you can vgimport this disk (VG) on another system.
(IMHO this is a job for a tape, because it is made for this and more robust while shipping)
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2008 10:00 AM
10-24-2008 10:00 AM
Re: Shipping internal drives between servers
Make the drive into a separate VG that contains only that one PV. For maximum compatibility, use LVM, not VxVM.
Create a single LV that will encompass the entire disk, for simplicity. When you mkfs/newfs it, make sure you use a vxfs version that is readable by the destination host (consider HP-UX version and patchlevel). Use the "-o version=N" option of mkfs if necessary.
Mount the disk anywhere you like. Write data into it.
Unmount, deactivate the VG and export it. Run "sync" for safety, make sure any the access LED of the disk is not lit, then yank the disk.
(Depending on patch level, HP-UX 11.11 may or may not allow you to use "pvchange -a N" to totally stop the disk access in preparation for hot removal. As the VG is deactivated, omitting this step is not crucial.)
Use "rmsf -a /dev/dsk/
(The map file is not really needed in a case this simple, and it won't always be possible to transfer it; thus, this procedure won't rely on it.)
Transport the disk to the destination host. Use anti-static packaging for ESD protection and anything suitable for protection against shocks. Multiple layers of bubble wrap are nice.
At the destination, insert the disk, run "ioscan -fnCdisk" and "insf". Note the device name of the disk: it probably won't be the same as on the source host unless your hardware configuration is *exactly* the same.
Pick an unused VG minor number, referring to site documentation and/or "ll /dev/vg*/group" output. Create the /dev/vgNAME directory and the /dev/vgNAME/group device node ("mkdir /dev/vgNAME; mknod /dev/vgNAME/group c 64 0xNN0000"). The VG name does not need to be the same as on the source host.
Run vgimport: "vgimport vgNAME /dev/dsk/
You're done.
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2008 10:04 AM
10-24-2008 10:04 AM
Re: Shipping internal drives between servers
I don't know why ...
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2008 10:18 AM
10-24-2008 10:18 AM
Re: Shipping internal drives between servers
We've been through this before.
Sitting on the forum all day answering every question that comes in like a chat session response is not a solution. You put no effort into your work and expect points, not going to happen.
Matti
No -s option neccessary?
No reboot needed with a hot pluggable internal drive?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2008 11:51 AM
10-24-2008 11:51 AM
SolutionI assume you mean with vgexport/vgimport?
Well, you _can_ use it if you wish... but then you'll have to transfer the VG map file by some other means. If the map file is on the disk you're transporting, you can't get at it before you've imported the VG without it. Which kind of defeats its purpose.
If you do have the map file (created by "vgexport -s -m
The use of "vgexport -s" does not mandate a corresponding "vgimport -s".
Basically at the vgimport time, you must *either* have the map file (created using vgexport -s) *or* specify the correct disk device.
> No reboot needed with a hot pluggable internal drive?
If a reboot was needed, that would be a pretty useless implementation of "hot pluggable", right?
However, after plugging the disk in, you should wait for it to spin up before running ioscan. 30 seconds to one minute should be plenty of time.
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2008 04:44 PM
10-24-2008 04:44 PM