Re: Reallocate storage

[Jason Abreu <jason.abreu@xxxxxxxxxxxxxxxxxxxx>]

The Development and Disaster Recovery LPARS on the same System i.
Our Development LPAR is running at ~55% capacity, whereas the Disaster 
Recovery LPAR is running at 70%+ capacity, but it is only a selection of 
pieces from the production environment.

I am trying to present a solution that would make the DR environment a 
mirror of our production environment, but that would put the DR LPAR at 
89%+ capacity.  I was trying to determine what would be involved in 
deallocating from one LPAR and reallocating to another LPAR, on the same 
System i.

I guess I didn't realize moving disks was involved since I'm working 
with Logical Partitions on the same System i.


Jason Abreu
Abreu Innovations, Inc.
jason.abreu@xxxxxxxxxxxxxxxxxxxx
http://www.abreuinnovations.com/

On 3/10/2011 11:36 AM, rob@xxxxxxxxx wrote:
> By storage I'll assume you mean disk storage.
>
> The steps to remove and add back to the other can be done, as Chris said.
> Ask yourself this however, how many hours do you want to add in a DR
> situation to:
> - Remove data on your Development box to free up space by saving to tape
> and deleting data.
> - Remove the drives on your development lpar and readd them to the DR
> lpar.  Verify with your BP that your DR lpar can accept additional drives.
> - Add the drives to raid and the storage pool.  This can take a few hours.
> Not counting the time already reserved for your data restoration.
>
> By guesting you can remove the need to physically move drives and verify
> raid and I/O cards but you'll still have the time to format and whatnot in
> three of the four steps above.
>
> I suggest you run this through a DR test and see if you can really afford
> the time.  If you do not have the time to test, it won't work.  Do you
> really want to figure this out during a disaster, when you are sleep
> deprived?  Unless it's only important that this work in theory so that
> you'll pass an audit.  Much like a local company with a DR box and Mimix
> that hasn't tested it since install and didn't even notice for a few days
> that their DR box had powered off.
>
> Also, the stuff you deleted off the development partition to make room;
> will that halt support and development?  For example, if I had to delete
> all my source files, and I keep no source on production, then it's really
> tough to work on some stuff stuck in a MSGW.  (Please, no debate on tricks
> like DBGVIEW, merits of keeping source on production and other stuff -
> allow me to use this as an example.)
>
>
> Rob Berendt