Good TSM design indicates that you should put a maximum file size filter on the 
storage pool; doing so will cause any file that violates the filter to go to 
that storage pool's NEXTSTGPOOL parameter, which would be the tape pool.
 
--
Mark Stapleton (mark.s AT evolvingsol DOT com)
Senior consultant

________________________________

From: ADSM: Dist Stor Manager on behalf of Gill, Geoffrey L.
Sent: Wed 2/14/2007 4:09 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Another Failed 12



I was wondering if anyone knows if this would cause a failed 12 report.
Makes sense to me that it would NOT, but my common sense gets the best
of me most of the time. This file is larger than the disk pool allows
and needs to go to tape, which reports happened, but I just don't see
how that would cause the failure, and since there looks to be no other
issues in the log I'm left scratching my head again. The server side
shows no problems, instead it does show the media mount and dismount
normally after the file has been transferred.



Since reported failures are sent to the TEC, and tickets created, it
takes time to investigate only, at least it looks like in this case, to
find no problems. So I'm left with disgruntled administrators as you can
imagine.



02/13/07   03:00:38 Normal File-->    65,247,232,000
/d4/backup/PSPRD/b_g2i9tkss_1_1  ** Unsuccessful **

02/13/07   03:00:38 ANS1114I Waiting for mount of offline media.

02/13/07   04:16:21 Retry # 1  Normal File-->    65,247,232,000
/d4/backup/PSPRD/b_g2i9tkss_1_1 [Sent]     



Geoff Gill
TSM Administrator
PeopleSoft Sr. Systems Administrator
SAIC M/S-G1b
(858)826-4062
Email: geoffrey.l.gill AT saic DOT com