Leo:
I wish we had zVM but that will have to wait until next year. zVM seems to
make life so much easier.
This is what I have been doing without zVM. My problems are around LVM
issues.
1) I use DF/DSS to take a backup (clone master down) of the SLES volumes
(no the LVM volumes). Then a DF/DSS to restore in new clone volumes.
2) I IPL the master clone volume and bring on-line the root and boot file
system of the new clone volumes. Then mount them followed by chroot into
the new clone volumes.
3) I change the /etc/zipl.conf of the new clone to use the new address of
the volumes where the new clone was restored. I also remove any
references to LVM in my /etc/fstab.
4) Then, mkinitrd and zipl.
5) I go and IPL the new clone system after making sure that no system is
running out of the Master Clone system volumes.
6) Then, I go and via yast re-do my OSA, Hipersockets and vary offline
volumes that are not needed by the new LPAR. I play with my OSA's by
signing up to eth2 (my Master Clone OSA port), removing hipersocket and so
on. Then I edit my quagga/ospfd.conf and bingo.
7) I re-ipl, verify everything if OK and I am ready to proceed with my
LVM's. But here I am stuck.
Problems:
1) The new clone (with updates, fixes, and so on), has to be able to use
the LVM groups defined from before cloning. I can't pvcreate because that
would destroy the physical content of my logical volumes. I can't
vgcreate because no pv's exist yet.
2) If I define the pv's in the Master Clone along with the vg and lv's,
then the new clone expect those volumes from the master clone to be there.
I tried a entire set of permutations to test my ideas but nothing is
convincing yet. What I have been doing is backing up my "logical volumes"
before cloning, then go throug the pvcreate, vgcreate and lvcreate process.
Then, I restore my volumes.
Any suggestions or best practices will be greatly appreciated.
Regards,
[EMAIL PROTECTED]
NCCI
Boca Raton, Florida
561.893.2415
greetings / avec mes meilleures salutations / Cordialmente
mit freundlichen Grüßen / Med vänlig hälsning
Leonard Janus
<[EMAIL PROTECTED] To:
[email protected]
om21.de> cc:
Sent by: Linux on Subject: AW: Cloning SLES-9
under LPAR's - correction
390 Port
<[EMAIL PROTECTED]
IST.EDU>
06/20/2005 08:49
AM
Please respond to
Linux on 390 Port
hmm - I was too fast, no VM at all I thing ?!
If you have a standalone DDR tape you can at least IPL this program and do
the copy of the original image.
Leonard
-----Ursprüngliche Nachricht-----
Von: Uriel Carrasquilla [mailto:[EMAIL PROTECTED]
Gesendet: Samstag, 18. Juni 2005 00:18
An: [email protected]
Betreff: Cloning SLES-9 under LPAR's
hi guys!
is anybody familiar with the process of cloning one SLES zLinux so I don't
have to re-install everything from scratch when I bring up a second LPAR.
I created my first LPAR from CD's. Then I went an added a very extensive
list of files, volumes and Logical Volume Groups (2 of them).
I need to create an exact replica but using different OSA addresses,
different DASD for all the zLinux and the Logical Volume Groups.
I got as far as replicating the system volume / the hipersockets / the eth
interfaces to the OSA with a combination of manual procedures and yast.
However, one I tried to recreate the logical volumes using yast, I can't
seem to find a way to do it. The system thinkgs they are already defined
(they are in /dev), so it refuses to re-use the same names.
if anybody has a step by step procedure I will be for ever happy.
Regards,
[EMAIL PROTECTED]
NCCI
Boca Raton, Florida
561.893.2415
greetings / avec mes meilleures salutations / Cordialmente
mit freundlichen Grüßen / Med vänlig hälsning
The information contained in this e-mail message is intended only for
the personal and confidential use of the recipient(s) named above. This
message may be an attorney-client communication and/or work product and
as such is privileged and confidential. If the reader of this message
is not the intended recipient or an agent responsible for delivering it
to the intended recipient, you are hereby notified that you have
received this document in error and that any review, dissemination,
distribution, or copying of this message is strictly prohibited. If you
have received this communication in error, please notify us immediately
by e-mail, and delete the original message.
----------------------------------------------------------------------
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 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
The information contained in this e-mail message is intended only for
the personal and confidential use of the recipient(s) named above. This
message may be an attorney-client communication and/or work product and
as such is privileged and confidential. If the reader of this message
is not the intended recipient or an agent responsible for delivering it
to the intended recipient, you are hereby notified that you have
received this document in error and that any review, dissemination,
distribution, or copying of this message is strictly prohibited. If you
have received this communication in error, please notify us immediately
by e-mail, and delete the original message.
----------------------------------------------------------------------
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
