Re: LPar, backup, standard procedures info.

[Pete Helgren <Pete@xxxxxxxxxx>]

John,

I have a customer that has that exact setup.  They are a school district 
with their own small development staff.  We initially upgraded to the 
i5, bringing everything over from the 720 and then we restored a backup 
of the "Production" partition to the "Development" partition.

First challenge was to quickly remove all source code from the 
production side so that the programmers wouldn't accidentally log on to 
the wrong partition and update the wrong source.  Second we installed 
and configured the licensed program 5722SS1 Option 22  OS/400 - 
ObjectConnect.  That allows us to do SAVRSTOBJ, SAVRSTLIB between the 
two partitions and, since we set up the routing to use the internal 
virtual network adapter, the transfers scream.

They don't have a CMS, they just have versioning and naming conventions 
that help identify and apply changes to the production objects. Again, 
they are a small shop (their two programmers plus our 3 or 4 depending 
upon the project we are helping them with).

HMC was the only challenge in the setup and it appears, for now, that it 
is stable (thankfully).

HTH,

Pete Helgren
Timpanogos Technologies, Inc



John Wallroff wrote:

> Anyone with any ideas on this subject?
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Wallroff
> Sent: Tuesday, June 21, 2005 10:04 AM
> To: midrange-l@xxxxxxxxxxxx
> Subject: LPar, backup, standard procedures info.
>
> We are implementing LPAR on our i5.  We are planning on having a
> Production Side and a Development/Testing Side.  I'd like some advice
> and I'd like to be able to do some reading on how to handle this simple
> type of installation.  Are there any good books or articles out there?
> We will be sharing a tape drive between the two partitions so any info
> on backing up each side would be greatly appreciated.  What is the
> simplest/best way to promote new and changed code from the
> Development/Testing Side to the Production Side?
>
>
>
> I would think that our situation would be one of the simpler and more
> common ways of using LPAR.  Any suggestions would be wonderful. 
>
>
>
>