Markus,

do you have collocation on the copy pool? This might explain why small 
chunk of data resides alone on a virtual volume.
Another possibility is that your virtual volumes devclass at that time had 
maxcap=500MB or 1000 MB and you later modified it to be 10GB.

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:        Antwort: Re: Very small server to server volumes

Hi,
thanks for the tip about space reclamation and the value for the mount 
limit.
That is OK now.
I still don't understand why I get all these small server to server 
volumes.
I've got one ba stg job running once daily,
when the data is backed up, one server volume should be mounted, there is 
a
constant stream of data to fill the volume close to its estimated 
capacity, I
can't see how  it should send 500 kb, close the volume and mount a new 
one.

Mit freundlichen Grüßen / Best Regards

Markus Veit

_________________________________________
Bayer AG
IM-CTS-PSO-SBB
Leverkusen, W  5
Tel.: +49(0)214/30-71254
Fax:  +49(0)214/30-9671254
E-Mail:  markus.veit.mv AT bayer-ag DOT de
Internet :  http://www.bayer-ag.de




  
  
  
                                               An: ADSM-L AT VM.MARIST DOT EDU  
  
 
                                               Kopie:    
                                               Thema:   Re: Very small 
server to server volumes 
  
             owner-adsm-l AT VM.MARIST DOT ED   
             U  
             Received :  28.08.2002   
             15:44   
             Bitte antworten an "ADSM:   
             Dist Stor Manager"   
  
  




Sure...
what you'll find is that for each ~operation~ in a server to server
enviornment, once that operation finishes, it closes out a virtual 
volume"."
So say you have an Est Cap of 10 GB but your backup stgpool to the remote
server /virtual volume only pushes 2 GB.  Then that virtual volume will be 
2
GB and won't have any more data written to it.

For your reclamation not working, check into the "mountlimit" of the 
device
class of device "server".




Dwight E. Cook
Software Application Engineer III
Science Applications International Corporation
509 S. Boston Ave.  Suite 220
Tulsa, Oklahoma 74103-4606
Office (918) 732-7109



-----Original Message-----
From: Markus Veit [mailto:markus.veit.mv AT BAYER-AG DOT DE]
Sent: Wednesday, August 28, 2002 4:25 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Very small server to server volumes


Hi TSM'er
2 x TSM Server 4.2.1.9
OS W2k SP2

we have on both  servers a  server to server  copy storagepool, as well as 
a
local copy storagepool.
One of the servers keeps generating server to server volumes that look 
like
this.

BY0O83.BFS.026016225      CP_TO_CROSS  LTOCROSSD-        1.0   76.2 Full
BY0O83.BFS.027744232      CP_TO_CROSS  LTOCROSSD-        0.5   64.6 Full
 this means that the estimated capacity of that volume is 0.5 MB and is 
used
64.6%, the volume contains data.
The space reclamation doesn't seem to work. ( it should, shouldn't it). 
The
volumes are set to be 10GB.

When I try to do a move data on a volume I get the following message.
 ANR1145W Move data process terminated for volume
  BY0O83.BFS.026585208 - insufficient number of mount
  points available for removable media.

Anyone got an idea what that could be, or which strategy I can use to have 
a
copy storagepool at a different site.
I was thinking of something like library sharing. Anyone got any 
exoirience
with
library sharing?
Thanks

Mit freundlichen Grüßen / Best Regards

Markus Veit

_________________________________________
Bayer AG
IM-CTS-PSO-SBB
E-Mail:  markus.veit.mv AT bayer-ag DOT de
Internet :  http://www.bayer-ag.de