SEO

Hi,

can anybody explain why HP-UX 11.31 needs that much space in /stand? The
manual sys 1.9GB are required and 7% of that are used. I had about 350MB free,
but an upgrade was not possible. Similar numbers are for / (1 GB), 28% used.

Another question is: Why doesn't the latest Data Protector (6.0) support the
installation of a Data Protector Client on HP-UX 11.31 (I learned today)?
Because different teams develop the software at HP? In the past at least the
HP stuff was compatible with itself.

The other thing is this: a few months after release of Data Protector 6.0, the
amount of needed patches did exceed the capacity of one CD. In the previous
release (Data Protector 5.50), HP never released new installation media, even
though the amount of patches exceeded the amount of the initial installation.

Is it still true: Don't use HP software until it's release is more than two
years ago! Why can't HP produce software that works? I mean: The release
schedule for HP-UX 11.31 was known to HP (and the Data Protector people) at
least for a year, and all the older HP-UX software will still run, so why were
they unable to release a Data Protector that works with HP-UX 11.31?

Considering the prices I could bang my head against something solid.
If Linux isn't better, it's at least cheaper...

Regards,
Ulrich

Ulrich Windl wrote:
> Hi,
>
> can anybody explain why HP-UX 11.31 needs that much space in /stand? The
> manual sys 1.9GB are required and 7% of that are used. I had about 350MB free,
> but an upgrade was not possible. Similar numbers are for / (1 GB), 28% used.


The default sizes of /stand and / had not changed prior to 11.31 release
for very many years. These sizes were no longer ideal for 11.11 and
would not work well for 11.23 and 11.31. As a result, a default 11.11 or
11.23 system in many cases will not have enough space for new 11.31
kernels. Also, automated cold installs via Ignite-UX require the
install kernel and install file system to be placed in /stand to start
the install process. Again, default 11.11 sizes were so small that
automated cold install of later releases was not possible in many cases.
Since 11.11 is mature at this point we do not plan to make default
config changes.

Therefore, default sizes have been increased for 11.31 and recent
updates to 11.23. These sizes correctly implement policies for space
for multiple kernels and to handle 11.23 -> 11.31 -> future release updates.

Because /stand must be contiguous and must be on the boot disk, making
volume size changes after install is very difficult, often requiring
reinstalling the system. Thus, running out of space is a tough problem.

Ulrich's comments appear to be based on the default sizes. Note that
these sizes are defaults and may be reduced during install or set via
custom config content to automate install. An administrator might want
to use a customized confg.local file to provide site-specific defaults.


From Ignite-UX product release notes, /opt/ignite/share/doc/release_note:

C.7.3
- This Ignite-UX release includes minor changes to default system
configuration for HP-UX B.11.31. In particular, conditions based on
memory size have been modified to consider memory reserved by
system firmware so that default configuration is less sensitive to
minor firmware differences. Significant default system configuration
changes are not planned for future releases at this time.
....
C.7.2
- This Ignite-UX release introduces significant changes to default
system configuration for HP-UX B.11.23. These changes are needed to
support software that has been added to HP-UX after initial release,
better handle larger mass storage devices and support future update
to other HP-UX releases. In particular, the default sizes of /stand
and / have been increased. Default primary swap size has also been
increased for some configurations. These changes are consistent with
support for future update to HP-UX B.11.31.
....
C.7.0
- Default file system sizes, primary swap size and other default system
configuration settings have been changed in HP-UX 11i v3 as compared
to prior HP-UX releases. This was important to better adjust to
Operating Environment software and computer system hardware. Further
tuning of these configuration defaults may be done in a future
Ignite-UX release. As before, it may be necessary or appropriate to
create custom configurations specific for your systems. Such custom
configurations or recovery configurations will not be affected by
future default configuration tuning.
....
Prior Ignite-UX versions included notice that default config changes
would be coming this year.

From /opt/ignite/data/Rel_B.11.31/config &
/opt/ignite/data/Rel_B.11.23/config:

# The /stand volume should be at least large enough to hold
# 5 kernels to support multiple configs and debugging.
# The /stand volume absolutlely needs to be large enough to
# hold 2 kernels.
#
# Note that for PA-RISC systems /stand must be no larger than
# 2000MB to avoid firmware addressing issues. The end of the
# /stand volume must be < 2GB into the disk. Some space for
# initial boot LIF content and volume overhead must be
# considered in sizing /stand for PA-RISC systems. In addition,
# physical extent rounding may add up to physical_extent_size.
# Thus, the size should be some mutiple of the largest physical
# extent size that is less than 2000MB.

There are Ignite-UX disk space impacts that will limit minimum /stand
size to be at least ~1GB for 11.31 and ~500MB for 11.23. Also, it’s
important to note that estimated % full numbers that show during install
will not be correct for /stand since the kernel is built during install
and is not file content that is loaded from depots. Thus, install disk
space analysis will not account for this space. Ignite-UX uses disk
space impacts to reserve space needed for building new kernels. Also,
remember that /stand needs to contain space for downloading install
kernels and install filesystems during future network-based installs,
including restoring make_net_recovery archives.

I do not have any information about Data Protector.



Best Regards,

Al Miller