Because only the DB of TSM1 knows what is in that virtual volume. From
TSM2's perspective this is single file and that's it. If that file was
Oracle data file, would you expect TSM to know what is the content of it?!

Zlatko Krastev
IT Consultant






John C Dury <jdury AT DQE DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
08.10.2003 07:31
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        space reclamation on a server storage pool?


We have 2 systems. TSM1 and TSM2. TSM2 is used solely as an offsite system
to backup our primary tape storage pool on TSM1. When I run reclamation on
the server storage pool on TSM1, the process requests a mount on TSM2 and
a
mount on TSM1. It appears to be copying data from the mount on TSM1 to
TSM2. Why wouldn't reclamation mount 2 tapes on TSM2 and copy the data
that
way instead of through the network which is going to be much slower.
Essentially it seems like it is going to copy the exact same data from
TSM1
to TSM2 two times because it gets copied once during the BACKUP STG
command, and then again during the space reclamation of the server storage
pool. This seems like a great waste of time when the exact same data
should
already be on the TSM2 system and could be moved directly from 1 tape to
another where it would be considerably faster.
Does this make sense? Why would it be done this way?
John