Just a guess.. could the size of data you are trying to backup is greater
than Storage?
Like backing up file size which is greater than what's available. I
can't recall, but I am thinking if the file is too large to be backed up
it would terminate before writing to storage pool and finding out later
that it doesn't have enough storage pool. I could be wrong.
Sung Y. Lee
E-mail [EMAIL PROTECTED]
"Damron, Nancy
E." To: [EMAIL PROTECTED]
<Nancy.Damron@PSH cc:
S.NET> Subject: Re: TSM storage problem
Sent by: "ADSM:
Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
07/30/2002 09:43
AM
Please respond to
"ADSM: Dist Stor
Manager"
No its not a license error....
-----Original Message-----
From: Simeon Johnston [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 09, 2002 1:22 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM storage problem
Did all that. Everything looks fine. It's all Read/Write.
Here's a silly question. Would this problem occure is, say, the license
check failed?
I just noticed that it says
Server License Compliance: FAILED
Is this the problem? I'd think this would be a different error.
sim
Gerald Wichmann wrote:
>Do a "q vol f=d" and check the "Access" field on your disk volumes. They
>should all be "ReadWrite". If they are "ReadOnly" then this would explain
>why TSM isn't writing to them and telling you the storage pool is full
even
>though at first glance it appears it isn't.
>
>TSM can change the access automatically to "ReadOnly" or even something
else
>if an event occurs the warrents it. E.g. if TSM loses access to the
>filesystem It's likely to mark all the volumes on that filesystem to
>"unavailable". There are also cases where it'll change it to some of the
>other values. To see why it did so you have to scan through the activity
log
>(e.g. do a "q act begind=today-7 search=sp1" or something similar).
>
>The other possibility is the max size threshold which someone else
>mentioned. Also, although remote, check the stgpool access parameter (q
stg
>f=d) to ensure it's readwrite.
>
>Gerald Wichmann
>Senior Systems Development Engineer
>Zantaz, Inc.
>925.598.3099 (w)
>
>-----Original Message-----
>From: Simeon Johnston [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, July 09, 2002 11:36 AM
>To: [EMAIL PROTECTED]
>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.
>
>
