- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- VM - Raw disk Migration
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
Discussions
Discussions
Forums
Discussions
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
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
04-02-2013 07:35 AM
04-02-2013 07:35 AM
All
I have just been given an HP-UX 11iv3 server with two VM's on RAW partitions. I need to know if i can migrate the VM''s that are on these partitions to a new SAN? and how? i have migrated the two other servers that were setup as LUN's but i have no idea how to do RAW partitions.
any direcitons or help would be greatly appreciated.
thank
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2013 10:32 AM
04-02-2013 10:32 AM
Re: VM - Raw disk Migration
Can you provide more details on what you mean by "RAW partitions"? Are these whole disks or whole LUNs? Are these RAW partitions on local storage? Is it only the boot volumes for the VMs you're concerned about?
If what you have today are VMs booting from a whole disk on local storage and you want to migrate the boot disks to a SAN, my suggestion would be to use DRD. I would present the new SAN LUN to the VM (either directly using NPIV or indirectly via presenting the LUN to the VSP and assigning the disk to the VM) and then use DRD to clone the boot disk to the new SAN lun. Once the clone is done you should be able to do a setboot to change your VM boot device and boot the VM on the new SAN-based storage.
Regards,
Dave
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Tags:
- DRD
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2013 10:40 AM
04-02-2013 10:40 AM
Re: VM - Raw disk Migration
when i saw RAW i mean they are LUN's from a SAN that are not part of a volume group and are not logical volumes. I need to migrate everything that is on this LUN from one SAN to another SAN.
Each LUN is setup as a VM, 75G each, so VM 1 is a 75G lun VM 2 is another 75G LUN. they are not mounted anywhere, not part of a logical volume,
this is all i see.
64000/0xfa00/0x9 /dev/disk/disk5 HPVM - 4 0.00 DGC CX4-480WDR5
64000/0xfa00/0xa /dev/disk/disk6 HPVM - 4 0.00 DGC CX4-480WDR5
here is what hpvmstatus tells me.
khepx007:/opt/hpvm/bin# ./hpvmstatus -P khepx020
[Virtual Machine Details]
Virtual Machine Name VM # OS Type State
==================== ===== ======= ========
khepx020 2 HPUX On (OS)
[Authorized Administrators]
Oper Groups :
Admin Groups :
Oper Users :
Admin Users :
[Virtual CPU Details]
#vCPUs Entitlement Maximum
====== =========== =======
2 10.0% 100.0%
[Memory Details]
Total Reserved
Memory Memory
======= ========
4096 MB 64 MB
[Storage Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
disk avio_stor 0 0 0 1 0 disk /dev/rdisk/disk5
[Network Interface Details]
Interface Adaptor Name/Num PortNum Bus Dev Ftn Mac Address
========= ========== ========== ======= === === === =================
vswitch avio_lan VLAN104 1 0 1 0 1e-fb-3e-61-cf-2f
[Misc Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
serial com1 tty console
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2013 10:45 AM
04-02-2013 10:45 AM
Re: VM - Raw disk Migration
Dave
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2013 10:54 AM
04-02-2013 10:54 AM
Re: VM - Raw disk Migration
I will start reading up on waht all of that means, but what about this?
Change the virtual disk with hardware address 0,0,4 to a different
physical device, /dev/rdisk/disk1:
# hpvmmodify -P myguest2x -m disk:scsi::0,0,4:disk:/dev/rdsk/c2t2d1
- Tags:
- hpvmmodify
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2013 10:56 AM
04-02-2013 10:56 AM
Re: VM - Raw disk Migration
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2013 10:58 AM
04-02-2013 10:58 AM
Re: VM - Raw disk Migration
that was just an example in the man pages, could I do
:
# hpvmmodify -P myguest2x -m disk:/dev/disk/disk15 :disk:/dev/disk/disk13
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2013 11:49 AM
04-02-2013 11:49 AM
SolutionMy suggestion is you present the new boot LUN from the new SAN to the VM Host (VSP). As an example, let's say this disk is identified as /dev/disk/disk6. You would then modify the existing guest to use this new LUN *in addition to* the existing disk from the old SAN:
VM HOST> hpvmmodify -P khepx020 -a disk:avio_stor::disk:/dev/rdisk/disk6
After making this change the hpvmstatus output for this VM should show both disks:
[Storage Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
disk avio_stor 0 0 0 1 0 disk /dev/rdisk/disk5
disk avio_stor 0 0 0 1 0 disk /dev/rdisk/disk6
You then log into the VM as a root user and do an ioscan to see how the VM guest sees this new disk. It will also assign it an agile device file. For this example, let's say the old SAN LUN was identified inside the VM as /dev/rdisk/disk1 and the new LUN is seen inside the guest as /dev/rdisk/disk2. You would then use DRD to clone the contents of /dev/rdisk/disk1 (old LUN) to the new LUN:
Inside VM> /opt/drd/bin/drd clone -p -t /dev/disk/disk2 -x overwrite=true -x verbosity=3
The -p option is a "preview" option so you can see if the command will complete without error. Once you are ready to perform the clone operation, issue the above command without the -p option. This will take the contents of the old SAN boot disk and copy it to the new SAN boot disk.
Once complete you can use setboot to point to the newly created boot disk on the new storage:
Inside VM> setboot -p /dev/disk/disk2
That sets the primary boot path to the newly cloned disk. Reboot the VM and ensure that it booted on the new LUN and comes up without error. When you're sure you don't need the old LUN anymore you can use rmsf to remove the agile device files associated with the disk:
Inside VM> rmsf -H <hardware path of the old SAN boot disk>
Then you can log back into the VM host and remove the old SAN boot disk from the VM guests' configuration:
VM HOST> hpvmmodify -P khepx020 -d disk:avio_stor::disk:/dev/rdisk/disk5
You can then do whatever you like with the old SAN LUN because the VM guest is no longer referencing it.
Regards,
Dave
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2013 05:30 AM
04-03-2013 05:30 AM