From: Eric Watson (ewatson@law.harvard.edu)
Date: Fri Jul 19 2002 - 08:33:44 EDT
Thanks to the two respondents - Bill Hassel and John Adams. To summarize, I
basically got it right except for I should create a map file with the "-s
option" when I vgexport, and use the map file when recreating the volume
group. I also need to take into account /etc/lvmpvg, which I do use for
vg02. Also, I need to delete the old device files when done, preferably
using "rmsf -H".
>From Bill:
"Correct. To save some time, specify a mapfile *and* the -s option
which is very cryptically described in the man page. It simply add
the LVM serial number to the mapfile which means that vgimport is
quite simple--no need to specify the new device files as the disks
will be scanned and added to the volume group.
As always with major changes, do a full backup of vg02 and just to
make sure, run make_tape_recovery too."
>From John:
"The map file is just a table, containing the logical volume number and
"name", and really only matters if you've named any of your LVs; if you've
accepted the default "lvol1, lvol2" it should import just fine. I recommend
it anyway, every once in a while you'll find that the previous admin got
"creative" and you'll have two filesystems mount backwards.
Also, if your system has an /etc/lvmpvg file, you may want to make a copy
before the export then edit it back into place after the import. May be
faster than fiddling with the vgimport bits. /etc/lvmpvg is where the
"physical volume group" lives, and is really only needed if you do mirroring
at the logical volume level. Odds are, you won't even have one, but if you
do it'll need "cleaning"."
Eric
************************************
Eric P. Watson
Supervisor of System Administration
Services
Harvard Law School 617-496-6518
************************************
-----Original Message-----
From: hpux-admin-owner@DutchWorks.nl
[mailto:hpux-admin-owner@DutchWorks.nl]On Behalf Of
ewatson@law.harvard.edu
Sent: Thursday, July 18, 2002 7:47 AM
To: hpux-admin@DutchWorks.nl
Subject: [HPADM] Changing SCSI addresses of FC60/SC10
Hardware: K570, FC60, (2) SC10 arrays
O/S: HP-UX 10.20
I am adding two processors to my K570 (it already has 4). I have to use the
slot that can be used for either additional processors or expansion i/o to
hold the new processors. That slot currently contains a HSC with two
tachlite cards that are the fibre connection to the FC60. I'm going to
move the two tachlite cards to the other expansion i/o slot, retiring two
SCSI cards in the process. This of course will change the SCSI addresses of
the FC60 and the disk drives in the SC10s.
The FC60 is currently configured as RAID1, with drive 1 in array 1 mirrored
to drive 1 in array 2; drive 2 in array 1 mirrored to drive 2 in array 2,
etc. I believe that the RAID1 LUN information is stored in the disk headers
and is separate from LVM header data.
The 10 LUNs of the FC60/SC10s are the only drives in volume group vg02.
vg02 has two logical volumes, which contain our OpenMail message store.
I think that this is what I need to do to migrate the LVM stuff to the new
SCSI addresses:
* First we unmount the 2 OpenMail file systems and comment them out in
/etc/fstab.
* Then we vgexport vg02, deleting the volume group.
* Then we shut down, move the Tachlite cards, and install the processors.
* Then we boot, creating the new device files for the FC60, and make sure
that the processors work.
* Then we create a new vg02 with mkdir and mknod, using the same magic
number for the vg02 group file.
* The we vgimport the 10 primary drives of vg02 into vg02. This will give
us the volume group and the two logical volumes.
* Then we vgextend the 10 alternate links into vg02.
* We remove the comments in /etc/fstab, and mount the file systems.
Does this make sense? Comments?
Eric
************************************
Eric P. Watson
Supervisor of System Administration
Services
Harvard Law School 617-496-6518
************************************
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact
majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner:
owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse
only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse &
search)
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:16 EDT