SUMMARY: Server Upgrade/Solaris 2.6 space needs/migration issues...

From: Marc S. Gibian (
Date: Fri Dec 05 1997 - 16:29:40 CST

I asked a number of questions related to a major server upgrade. Most
respondents only responded to the first of these, asking how to do a
sophisticated survey of disk space usage on the old server. Answers were limited

-. find /* -type d -exec du -sk {} \;

-. An old perl script called dutree (haven't tried it yet)

-. Use quot command

-. Use xdu, an old tool to graphically display du output

-. Use vtree (haven't tried it yet)

-. A few "just use du", though I already knew that was more primitive than I was
   going for.

My thanks to:

"V. Q. Hoang" <>
Rich Kulawiec <> (Kevin Sheehan {Consulting Poster Child})
Jeff Woolsey <>
David Thorburn-Gundlach <>
Mark Bergman <bergman@hercules.PHRI.NYU.EDU>


Marc S. Gibian
COMSYS Information Technology Services phone: (617) 377-6350
PRISM/TFS email:
                           or is it:
                        well, maybe:
              and if all else fails:

attached mail follows:

I am in the process of final planning for migration of my server from a
SPARCstation 20 running Solaris 2.5, to an Ultra 2 to run Solaris 2.6. One issue
I have is determining how to layout the filesystems on the new server.

I am quite familiar with using "du -dsk *" and "df -k -F ufs" to look at space
usage in a particular directory and at a filesystem level. I was wondering if
anyone knows of a tool that constructs a usage tree such as one might manually
create by walking the directory tree and performing repeated du commands?

Unfortunately, I do not have the hardware to leave the old server behind
performing some of its prior tasks, except for a short upgrade period, so I need
to be sure I have the disk space arranged well to permit me to move everything
to the new server and move to old machine into its "new" role.

Other questions include:

1. Can I setup a custom jumpstart to install Solaris 2.5.1 on my Solaris 2.6
machine? While I like 2.6 (though, I've already in 1/2 a day on my test server
crashed some key tools), my team must generate software for Solaris 2.5.1 and up
and thus all developer workstations (all but the server do compiles, links, etc)
will be upgraded to 2.5.1 for now. I will eventually move these system to 2.6,
and at that time will need to upgrade this server to jumpstart 2.6, but for now
I need to determine if I can support the jumpstart of the earlier release on the
2.6 server.

2. How do I migrate Solstice backup to a new server? I also need to upgrade
Solstice backup from its current version 4.1.3 to 4.2.6. What order is best for
this upgrade and most safely protects my index files?

3. Any hints on moving a NIS+ root master (2.5) to a new server (2.6)? I am
almost ready to just manually create a new NIS+ domain for the new server and
2.5.1 clients and migrate everyone just as I did when I upgraded from a SunOS
4.1.3 NIS environment to the current Solaris 2.5 NIS+ (this included a major uid
change as I found the original uids had been assigned in the reserved range and
corrected that during the upgrade to 2.5).

Finally, I need to do this with minimal disruption to the team, and a minimum of
off-hour work (as I am also needed by the team during normal hours and I will be
performing all upgrade work).


Marc S. Gibian
COMSYS Information Technology Services phone: (617) 377-6350
PRISM/TFS email:
                           or is it:
                        well, maybe:
              and if all else fails:

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:11 CDT