Thanks for the confirmation on the termination of the
archive.......drat......I was hoping it wasn't so.
The pool was empty when we started. Simply not enough room. I will have to
expand and/or have the user do the archive in pieces......
We don't do a lot of archiving. This is why the pool is so small. Don't
have the DASD to just sit there and not be used but once in a while...
David Longo <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
05/16/2002 02:07 PM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Archive failures due to disk storage pool filling up...
Your step number 2 is not exactly true, it won't wait for migration to
empty
space. If you are setup for client to go directly to tape, it will do
that
IF tape mounts etc are available.
And your last question is correct - it is terminated. Simplest solution
is to increase diskpool or if that's not an option, adjust schedules to
update migration percentages so pool will be emptier when this
clients schedule comes around. (I've done a good bit of this "tuning".)
David Longo
>>> [EMAIL PROTECTED] 05/16/02 01:20PM >>>
Environment: TSM OS/390 server - V4.1.4 Linux Client - V4.1.4
Been trying to archive a client node. The archive disk pool is not as
large as the amount of data to be archived.
Received a "failure" on the archive. This is one of the messages:
05/16/2002 10:43:20 ANS1228E Sending of object
'/usr/local/blackboard/docs/courses/1/INFO-360-002-2002Spring/content/_65742_1/360web_ontime2.zip'
failed
I looked into the server log and found the related message:
05/16/2002 10:43:01 ANR0534W Transaction failed for session 62 for node
ATHENA.VCU.EDU (Linux86) - size estimate exceeded and server is unable to
obtain additional space in storage pool SPARCHIVE.
Yes, I looked up the ANR0534W message. It talks about both a possible
COMPRESSION issue as well as insufficient space in the storage pool.
Yep, the compression for this session was "-5%".
So......Big deal.....I would not think this would/should cause a permanent
failure and lack of archiving of the file in question.
Yes, I realize the storagepool filled up. My understand has always been,
and please correct me if I am wrong, that is a storagepool fills
up/reaches the HI value, 2 things occur:
1. Migration is kicked off, moving data to the defined NEXTPOOL (which is
did)
2. The CLIENT is told to "Whoa......Stop Sending Data......Hang on while
I move stuff out of the storagepool to make more room....OK Client, you
can send me more data, now......"
Am I way off on this or is this some sort of problem ?
Also, the book says : "System Action: The specified session is ended and
server operation continues." Does this mean the archive was killed and
did not finish successfully ?
----------------------------------------------------------------------------------------------------
Zoltan Forray
Virginia Commonwealth University - University Computing Center
e-mail: [EMAIL PROTECTED] - voice: 804-828-4807
"MMS <health-first.org>" made the following
annotations on 05/16/02 14:22:26
------------------------------------------------------------------------------
This message is for the named person's use only. It may contain
confidential, proprietary, or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission. If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it, and notify
the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient. Health First reserves the right to monitor all e-mail
communications through its networks. Any views or opinions expressed in
this message are solely those of the individual sender, except (1) where
the message states such views or opinions are on behalf of a particular
entity; and (2) the sender is authorized by the entity to give such views
or opinions.
==============================================================================
