Have you defined COPYSTGpool and COPYContinue=No on the primary pool?
If copypool is out of space and COPYC=N the whole write will fail.

Zlatko Krastev
IT Consultant



Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        TSM storage problem

We just got a TSM server up and running (still in a testing phase but
it's running).
I recently tried to backup a new node I created and got this error -
ANS1329S Server out of data storage space

Now, the server only has an 80GB partition for data storage at the
moment.  That is split into 7 10GB files and one 4GB.
The 4GB is 95% full but the others are around 30 - 40% full.

Storage pool info --

STORAGE       DISK             76,480.0      41.7      41.7       90 70

X:\SERVER1\SP1               STORAGE       DISK            10,240.0
34.2     On-Line
X:\SERVER1\SP2               STORAGE       DISK            10,240.0
41.0     On-Line
X:\SERVER1\SP3               STORAGE       DISK            10,240.0
37.8     On-Line
X:\SERVER1\SP4               STORAGE       DISK            10,240.0
34.0     On-Line
X:\SERVER1\SP5               STORAGE       DISK            10,240.0
31.4     On-Line
X:\SERVER1\SP6               STORAGE       DISK            10,240.0
39.0     On-Line
X:\SERVER1\SP7               STORAGE       DISK            10,240.0
49.1     On-Line
X:\SERVER1\SP8               STORAGE       DISK             4,800.0
96.4     On-Line

Why would I get this error if there is more than enough room for a backup?
I'm new to TSM administration so maybe I'm missing something.

sim
And keep in mind it could be something REALLY stupid that I just forgot
about.