× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I'll answer my original question #1:
1. How much headroom do you all like to allocate for the LS disk size so as
not to box yourselves in?
As of 2018 for Client LPARs of IBM i hosting i, I found Jim say 50GB, and
Rob say 70GB.
https://archive.midrange.com/midrange-l/201812/msg00569.html
https://archive.midrange.com/midrange-l/201812/msg00549.html

Revised questions:
1. Do you follow a storage ratio for SYSBAS to IASP, as mentioned in
SG247811, or would you say that information is outdated?

https://www.redbooks.ibm.com/abstracts/sg247811.html
Page 44, Section 3.2.2, Subtitle "Capacity":
"The size relationship between *SYSBAS and an independent disk pool is
important. The ratio of one to two (1:2) or one to three (1:3) for disk arms
can be a good start for sizing disk capacity. If 30 GB of disk is required
in the independent disk pool, then 10 GB of disk is required for the system
ASP. Keep in mind that all temporary objects for applications residing on an
independent disk pool are created in the system ASP."

2. Any benefits to dedicating an NWSD purely for the IASP residing in a
partition?

Feel free to chime in with any experience using IASPs in i Hosting i.

-------------
Jacob
-------------

-----Original Message-----
From: Jacob
Sent: Tuesday, August 27, 2024 6:03 PM
To: 'midrange-l@xxxxxxxxxxxxxxxxxx' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Conserving or Minimizing Disk Space on ASP 1 (SYSBAS) when Using
Independent ASPs (iASPs)

***IBM i playground questions***

I am doing testing on IBM i client partitions that will hold all user/app
data in independent ASPs (iASPs).
The goal is to contain all library and IFS data on iASPs, while the Load
Source and SYSBAS remain on ASP 1.
I'd like to condense multiple development and testing areas onto one LPAR,
while still giving each environment a dedicated space to work in via
separate iASPs.
(Whether this is feasible/preferred over separate LPARs is another
discussion.
Feel free to chime in on that point though.)

If minimum Load Source rules are followed, I would use 40GB for the disk.
Multiply that by 6 disks and you've got 240GB.
If I give myself headroom, I could use 80GB. Over 6 disks, this equals
480GB.
(Mind you, I'm assuming best practice is to keep all the disks the same
size.)

I already asked IBM these questions, and in a nutshell, they said, "It
depends".

Questions:
1. How much headroom do you all like to allocate for the LS disk size so as
not to box yourselves in?
2. In a scenario such as the one described above, do you feel that
allocating between 240GB-480GB
is overkill for ASP 1 if all user and app data will be stored in iASPs?

Maybe I'm just being stingy with storage.

-------------
Jacob
-------------



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.