- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: EMC 5830 --> EMC 8530 Migration
Operating System - HP-UX
1820750
Members
3664
Online
109627
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
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
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
04-24-2003 11:58 AM
04-24-2003 11:58 AM
This is a continuation from an old thread, I just wanted to throw the steps I'm going to take out for review.
I'm migrating data from an existing EMC 5830 to a new EMC 8530, and also switching SCSI to Fiber. I will have the luxury of having both Symms presented to me for a week. I'm going to go with a host based copy rather than the array based copy so I can change some of my LVM settings.
- Shut down database.
- BACKUPS!
- Unmount all affected filesystems.
- Deactivate VGs.
- Export VGs (using -v -s -m)
- Create temporary VGs (mkdir/mknod).
- Import original VGs to the temporary VG space.
- Create temporary mount points and mount the original LVs to them.
- Create the new VGs/LVs with better LVM settings, mount them to the original mount points.
- Copy the data.
- Remove the original VGs and temporary mount points.
Unrelated:
Does rdist still have a 2G file size limit?
Anybody have a good document outlining the steps to mirror a root disk (there are probably plenty out there, just haven't had time to search)?
Thanks in advance.....and thanks to those that directed me in my previous thread.
Jim Mallett
I'm migrating data from an existing EMC 5830 to a new EMC 8530, and also switching SCSI to Fiber. I will have the luxury of having both Symms presented to me for a week. I'm going to go with a host based copy rather than the array based copy so I can change some of my LVM settings.
- Shut down database.
- BACKUPS!
- Unmount all affected filesystems.
- Deactivate VGs.
- Export VGs (using -v -s -m)
- Create temporary VGs (mkdir/mknod).
- Import original VGs to the temporary VG space.
- Create temporary mount points and mount the original LVs to them.
- Create the new VGs/LVs with better LVM settings, mount them to the original mount points.
- Copy the data.
- Remove the original VGs and temporary mount points.
Unrelated:
Does rdist still have a 2G file size limit?
Anybody have a good document outlining the steps to mirror a root disk (there are probably plenty out there, just haven't had time to search)?
Thanks in advance.....and thanks to those that directed me in my previous thread.
Jim Mallett
Hindsight is 20/20
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2003 12:35 PM
04-24-2003 12:35 PM
Solution
to mirror a root disk on 11.0 (be sure to adjust the /dev/ references for your particular system):
reduced all lvols on the disk: lvreduce -m 0 /dev/dsk/c2t2d0
removed the disk from the volume group: vgreduce /dev/vg00 /dev/dsk/c2t2d0
reserve a boot area on the disk: pvcreate -B /dev/rdsk/c2t2d0
make the boot area: mkboot -v /dev/dsk/c2t2d0
copy the boot files: mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/dsk/c2t2d0
add the disk back to the volume group: vgextend /dev/vg00 /dev/dsk/c2t2d0
verify that the disk is bootable:
lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t2d0 (0/0/1/1.2.0) -- Boot Disk
/dev/dsk/c2t2d0 (0/0/2/0.2.0)
Boot: lvol1 on: /dev/dsk/c1t2d0
Root: lvol3 on: /dev/dsk/c1t2d0
Swap: lvol2 on: /dev/dsk/c1t2d0
Dump: lvol2 on: /dev/dsk/c1t2d0, 0
verify that the boot information is there:
lifls -Cl /dev/dsk/c2t2d0|pg
volume ISL10 data size 7984 directory size 8 99/10/28 15:23:53
filename type start size implement created
===============================================================
ISL -12800 584 240 0 99/10/28 15:23:53
AUTO -12289 824 1 0 99/10/28 15:23:53
HPUX -12928 832 800 0 99/10/28 15:23:53
PAD -12290 1632 1700 0 99/10/28 15:23:54
LABEL BIN 3336 8 0 02/05/28 10:08:10
add the logical volumes back to the disk:
lvextend -m 1 /dev/vg00/xxxxx /dev/dsk/c2t2d0
The first three lvol's have to be:
/stand
/
/swap
(confirm by comparing output from lvlnboot -v & bdf)
repeat for each remaining logical volume in the volume group
HTH
mark
reduced all lvols on the disk: lvreduce -m 0 /dev/dsk/c2t2d0
removed the disk from the volume group: vgreduce /dev/vg00 /dev/dsk/c2t2d0
reserve a boot area on the disk: pvcreate -B /dev/rdsk/c2t2d0
make the boot area: mkboot -v /dev/dsk/c2t2d0
copy the boot files: mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/dsk/c2t2d0
add the disk back to the volume group: vgextend /dev/vg00 /dev/dsk/c2t2d0
verify that the disk is bootable:
lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t2d0 (0/0/1/1.2.0) -- Boot Disk
/dev/dsk/c2t2d0 (0/0/2/0.2.0)
Boot: lvol1 on: /dev/dsk/c1t2d0
Root: lvol3 on: /dev/dsk/c1t2d0
Swap: lvol2 on: /dev/dsk/c1t2d0
Dump: lvol2 on: /dev/dsk/c1t2d0, 0
verify that the boot information is there:
lifls -Cl /dev/dsk/c2t2d0|pg
volume ISL10 data size 7984 directory size 8 99/10/28 15:23:53
filename type start size implement created
===============================================================
ISL -12800 584 240 0 99/10/28 15:23:53
AUTO -12289 824 1 0 99/10/28 15:23:53
HPUX -12928 832 800 0 99/10/28 15:23:53
PAD -12290 1632 1700 0 99/10/28 15:23:54
LABEL BIN 3336 8 0 02/05/28 10:08:10
add the logical volumes back to the disk:
lvextend -m 1 /dev/vg00/xxxxx /dev/dsk/c2t2d0
The first three lvol's have to be:
/stand
/
/swap
(confirm by comparing output from lvlnboot -v & bdf)
repeat for each remaining logical volume in the volume group
HTH
mark
the future will be a lot like now, only later
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