Don't create the LVM. You copied the existing LVM when you copied the packs. If
you DDR the packs after creating a new LVM you will wipe out the new LVM and
replace it with the old LVM.
[EMAIL PROTECTED] wrote:
If I create an LVM after I ddr the packs, won't that wipe out whatever
is on those packs ?
Alan Levy
W: 718-403-8020
C: 347-401-4629
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Stephen Frazier
Sent: Tuesday, May 02, 2006 12:54 PM
To: [email protected]
Subject: Re: upgrading to sles9
That sounds like the safe way to do it. But why don't you DD all 29
volumes in
step 3 and skip steps 1, 5, 6, and 7? You don't need to format the
volume before
you do the DDR copy to it.
[EMAIL PROTECTED] wrote:
I currently have a sles8 server in production with an LVM of 208 gig
(29
mod-9 in total, 28 for the LVM).
Filesystem 1K-blocks Used
Available Use% Mounted on
/dev/dasda1 708568 403132
269444 60% /
/dev/dasdc1 2365444 1457024
788260 65% /usr
/dev/system/vol1 208097872 181917960 15609160
93% /usr/local
I would like to migrate this to a sles9 server. I cannot upgrade the
server in place due to a number of
customized installed products which may break during the update. Since
this is a production server, I
cannot afford an outage (it gets about 1 million hits per day).
I would like to create a new sles9 server and then do a conversion but
am not sure about the best
way of accomplishing this. Is the following feasible?
1. Get 29 new mod-9 packs and cp format them
2. Create a new userid with 29 packs in the VM directory.
3. Clone an exising sles9 server (ddr existing server to first new
pack)
4. Bring up server & configure it (different IP address than
production,
different OSA addr, etc)
5. Activate the 28 new packs with yast.
6. Create lvm with the 28 packs
7. Shut down the new server and DDR the production 28 packs to the new
server.
8. Install software needed for the new server.
9. Bring up server and test
10. Shut down production server & change ip & osa addresses of new
server
11. Bring up new server as the new production server.
Does anyone have other suggestions or a better way of doing this ?
TIA
----------------------------------------------------------------------
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
--
Stephen Frazier
Information Technology Unit
Oklahoma Department of Corrections
3400 Martin Luther King
Oklahoma City, Ok, 73111-4298
Tel.: (405) 425-2549
Fax: (405) 425-2554
Pager: (405) 690-1828
email: stevef%doc.state.ok.us
----------------------------------------------------------------------
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
--
Stephen Frazier
Information Technology Unit
Oklahoma Department of Corrections
3400 Martin Luther King
Oklahoma City, Ok, 73111-4298
Tel.: (405) 425-2549
Fax: (405) 425-2554
Pager: (405) 690-1828
email: stevef%doc.state.ok.us
----------------------------------------------------------------------
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
