Environment: TSM 4.2.x on an AIX 4.3.3 ML10 server (660-6H1) with a 3584-L32
and a 3584-D32 expansion frame.

In the process of setting it up, which is a luxury that I'll have only once
to get it right. :) So, some questions (since I am still coming up to speed
on *SM).

1) Is there any particular reason to set a max file size for a disk stgpool?
   (Assuming a setup where disk stgpool will migrate to tape stgpool)

2) Should the TSM server have its own stgpool for backing up itself?

3) I've heard mixed things about 358x firmware version 22UD... I think we
   have 18N2 (but not near it right now to confirm), although what I've
   heard about 22UD is generally (but not 100% in agreement) positive. Stable?

4) Whom is supposed/allowed to upgrade firmware? IBM CE only?

5) The only docs for firmware upgrade references a NT/2000 box and the
   NTUtil application, whereas I'm in an all-UNIX (AIX and Solaris, although
   I do have a laptop with Linux and Windows XP if need be) environment, so
   wonder how to upgrade the firmware without Windows if it's even possible.

6) To *SM, all backups are incrementals (except for the first backup of a
   new client), is my general understanding. Is there a way to force a full
   backup of a particular client as an one-time operation? I'm guessing maybe
   not, but thought I might try asking, anyway. :)

7) The biggest single question... I don't have a real good understanding of
   the purpose of copy stgpools. I've read a lot of documentation -- hundreds
   of pages of multiple docs, re-read, read old adsm-l mail, Google searches,
   etc... but still just don't quite 'get it'. I can set up HACMP clusters,
   debug really obscure things, but this eludes me. ;)

   What I want to do is:

   client -> TSM server -> disk stgpool -> (automatically migrate to tape
   based on space utilization of disk stgpool) tape stgpool

   That's the general concept of what I want to achieve. Is a copy stgpool
   really needed, to be attached to either one of the primary stgpools?

   I was under the impression that a copy stgpool was something you wanted
   when you wanted to copy a primary stgpool so that you could send it to
   another stgpool when ready (based on whatever trigger...space, date),
   such as in a disaster recovery scenario?

-Dan Foster
IP Systems Engineering (IPSE)
IP Systems Engineering (IPSE)
Global Crossing Telecommunications