Hi Lisa,

I'm not certain why this is happening, but here are some thoughts (I know,
some of these are probably silly...):

- You showed the copy group from the COMPAQ01 policy set, but not
STANDARD. Do they match (i.e. did you make any policy set changes that
need to be activated)?

- Are all the volumes in the disk storage pool online and set for
read/write access?

- You say that the data is being bound to the correct management class;
have you actually confirmed this by querying the archived data?

- Are there any messages on the server indicating a problem with the
storage pool?

- Are you sure this node is in the COMPAQ01 policy domain and not in
another domain with a like-named management class that goes to tape?

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Lisa Cabanas <CABANL AT MODOT DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
01/17/2003 11:42
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        how can I determine why an archive is not going to disk?



Hello *,

I am at a loss how to determine why a client is not going to disk for an
archive.

The archived data is going to the correct management class.

The management class specifies that the archive copy group points to the
ARCHIVE storage pool destination

Policy Domain Name COMPAQ01
Policy Set Name COMPAQ01
Mgmt Class Name ARAN_DATA
Copy Group Name STANDARD
Retain Version 1825
Copy Serialization SHRSTATIC
Copy Destination ARCHIVE
Last Update Date/Time 2002-12-05 11:38:48.000000
Last Update by (administrator) CABANL

and the storage pool does not have a max size threshold

Storage Pool Name ARCHIVE
Storage Pool Type PRIMARY
Device Class Name DISK
Estimated Capacity (MB) 180579.0
Pct Util 0.0
Pct Migr 0.0
Pct Logical 100.0
High Mig Pct 80
Low Mig Pct 40
Migration Processes 1
Next Storage Pool ARCHIVETAPE
Maximum Size Threshold -
Access READWRITE
Description -
Overflow Location -
Cache Migrated Files? NO
Collocate -
Reclamation Threshold -



But every time I try to do an archive, it (even for 20KB files) mounts a
tape to write to.

tsm: TSM_HQ_2>q se 15138 f=d

              Sess Number: 15,138
             Comm. Method: Tcp/Ip
               Sess State: MediaW
                Wait Time: 17 S
               Bytes Sent: 345
              Bytes Recvd: 583
                Sess Type: Node
                 Platform: WinNT
              Client Name: GHSMARAN01
      Media Access Status: Waiting for mount of output volume 820516 (17
                            seconds).
                User Name:
Date/Time First Data Sent: 01/17/2003 11:01:00AM





WHY????? What have I missed?

thanks, lisa