ADSM-L

Moving data targets

2004-06-08 09:57:52
Subject: Moving data targets
From: Tab Trepagnier <Tab.Trepagnier AT LAITRAM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 8 Jun 2004 08:54:42 -0500
Server: TSM 5.1.9.0 on AIX 5.2 ML-2
Clients: TSM 5.1.7.0 on Windows 2000 SP3

Several months ago I reconfigured our TSM system to delay the purchase of
yet another tape library, making liberal use of the MigDel parameter. Now,
when the "front end" resources fill up, clients are not redirected to
subsequent storage pools despite the configuration that says that they
should.

Specifically, the backup data path now is like this:

Client -> disk -> 3575 -> LTO -> DLT -> shelf

Because "disk" and "3575" are of limited capacity, I have assigned MaxSize
and MigDel on both.
Disk = 60 MB max size, MigDel = 2 days, MigCont = Yes, NextStg=3575
3575 = 2GB max size, MigDel = 14 days, MigCont = No, NextStg=LTO
LTO accepts everything

In practice, if the 3575 fills up, the client sessions "FAIL" rather than
shift to the LTO.  Yet, if the disk fills up, the client sessions do shift
to the 3575.

This is making it a real challenge to maintain reliable system operation
until we decide what we want to do regarding storage expansion.

Is this normal?  Or have I encountered a bug?

Thanks.

Tab Trepagnier
TSM Administrator
Laitram, L.L.C.

<Prev in Thread] Current Thread [Next in Thread>
  • Moving data targets, Tab Trepagnier <=