And if you want zVM to take care of the disk label, you can dedicate the current dasds, add a new set of dasds to the vg, and use the pvmove (man pvmove) command to migrate data seamlessly from the old dasds to the new ones.
We did this, in production, on the db2 servers, without taking anything down. Servers up, clients connected and transactions flying. Absolutely no problem, no hassle. After the pvmove finishes, you can put the old dasds offline, recreate the initrd, and run zipl. On Apr 25, 2016 21:55, "Rick Troth" <[email protected]> wrote: > If it's the same DASD, then you should not need vgexport/vgimport. Just > point and shoot. The system will see the signatures on the disks and > recognize the volume group. > > -- R; <>< > > > On Apr 25, 2016 8:48 PM, "Dave Myers" <[email protected]> wrote: > > I am migrating a server from LPAR SLES10 (bare metal) to zVM Guest and a > new SLES11 server. > I need to migrate some existing LVMs. > > I know I need to DEDICATE the 3390s in the zVM USER DIRECT for the SLES11 > guest and I think I need to maybe VGEXPORT and VGIMPORT ?? > > Can someone please give me some steps ? > Thanks, > Dave > > > From: Dave Myers > Sent: Wednesday, April 20, 2016 9:37 PM > To: '[email protected]' <[email protected]> > Subject: RE: Install not working for SLES11 SP4 thru TRUNKED VSWITCH > > Hi all, > I appreciate your help......please keep suggestions coming. > Marcy, the last post from you was not readable on the list. > Thanks, > Dave > > From: Dave Myers > Sent: Wednesday, April 20, 2016 9:29 PM > To: '[email protected]' <[email protected]<mailto: > [email protected]>> > Subject: RE: Install not working for SLES11 SP4 thru TRUNKED VSWITCH > > VLAN def in system config is: > define vswitch vsw1 rdev 400.p1 vlan 229 > > In LNXDFLT profile we have: > > COMMAND SET VSWITCH VSW1 GRANT &USERID VLAN 229 > COMMAND DEFINE NIC 300 TYPE QDIO > COMMAND COUPLE 300 TO SYSTEM VSW1 > > When we logon to the guest from which we are executing the SLES11SP4, we > get positive msgs that the vnic is coupled to the vswitch. > > > > [cid:[email protected]] > > Dave Myers | Senior Systems Engineer - System z > Office: 303.996.7125 | Mobile: 303.619.0782 | [email protected] > <mailto:[email protected]> > Sirius Computer Solutions | www.siriuscom.com<http://www.siriuscom.com/> > 10100 Reunion Place, Suite 500, San Antonio, TX 78216 > > > > From: Dave Myers > Sent: Wednesday, April 20, 2016 8:56 PM > To: '[email protected]' <[email protected]<mailto: > [email protected]>> > Subject: RE: Install not working for SLES11 SP4 thru TRUNKED VSWITCH > > The define VSWITCH and the COUPLE both produce no errors. That part looks > good. > Yes. We are using this VLAN for some z/OS interfaces, so it is not new. > > The SLES11SP4 EXEC does not show any errors. > The only message we get, after a 1-2 minute hang in the SLES11SP4 EXEC is: > " unable to find ... repository". > > When I switch to a different VLAN that is not trunked and I keep the same > NFS location of the repository is works OK and finds my NFS server. > > > > From: Dave Myers > Sent: Wednesday, April 20, 2016 7:19 PM > To: '[email protected]' <[email protected]<mailto: > [email protected]>> > Subject: Install not working for SLES11 SP4 thru TRUNKED VSWITCH > > I am trying to install SLES11 SP4 under zVM VSWITCH. > The VSWITCH is attached to an OSA that is TRUNKED to a switch port. > We defined VLAN ID on the VSWITCH def and also on the GRANT ACCESS > statement for the guest. > We cannot connect when we run the SLES11SP4 EXEC. > > Does anyone know if this is supported for install by the SLES11 SP4 RAM > system? > Or does anyone know how to debug this connection from the SLES11SP4 EXEC ? > > Thanks, > Dave > > > This message (including any attachments) is intended only for the use of > the individual or entity to which it is addressed and may contain > information that is non-public, proprietary, privileged, confidential, and > exempt from disclosure under applicable law. If you are not the intended > recipient, you are hereby notified that any use, dissemination, > distribution, or copying of this communication is strictly prohibited. This > message may be viewed by parties at Sirius Computer Solutions other than > those named in the message header. This message does not contain an > official representation of Sirius Computer Solutions. If you have received > this communication in error, notify Sirius Computer Solutions immediately > and (i) destroy this message if a facsimile or (ii) delete this message > immediately if this is an electronic communication. Thank you. > > Sirius Computer Solutions<http://www.siriuscom.com> > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
