The change for /stand is required. You can't use your current usage in /stand as a guide because 11i (I am assuming 11iv1, not 11iv2, also known as 11.23) has a lot different kernel structure and /stand will not have exactly the same files as your 11.00 system. 200 megs is probably OK for small systems but 300 is quite safe.
/var recommendation is based on general usage where email, printer spooling, patches, large logfiles, performance logs, etc are fairly large. Remember that if /var is full, almost *EVERYTHING* on your system will have problems. /var also has /var/tmp which can be abused by anyone on your system. Now if you manage /var by separating potential runaway directories with separate mountpoints, have a 500 meg /var with separate /var/mail, /var/adm, /var/spool, and /var/tmp makes a lot of sense.
But as many others have advised, upgrades have had a 99% failure rate for the last 10+ years. Most upgrades seem desirable because the 'rest of the software' doesn't need to be installed and configured. But in general, that isn't true. Your current applications and/or database engines may need a newer version installed in order to work. Many HP products such as mirroring, Online JFS, compilers, etc will need new versions (and codewords) to be compatible. And there are all those "wish we had time to fix" problems with disk layouts, mountpoints, etc.
So toss the upgrade documents and plan for a cold install, ideally on a test system so you can install everything including the new application versions and test offline before going into production. This is not much different in the PC world -- upgrades are seldom successful in WinNT, Win2k, WinXP and now Vista.
Bill Hassell, sysadmin
