I agree,
a move data works on offsite tapes, the primary stgpool volumes are used, just
as space reclamaition.
I had a call open with TSM support were space reclamation always failed on
several volumes with a database error.
The funny thing was when you did a move data on the offsite pool it was
successfull, but the next time a backup storagepool was run on the primary
storagepool, TSM wanted to backup that file to the copypool. ????
The problem only dissapeared after the files on these volumes expired, so what
went wrong could not be traced back by 2nd level TSM support
Mit freundlichen Gr��en / Best Regards
Markus Veit
An: [EMAIL PROTECTED]
Kopie:
Thema: Re: Move Nodedata starts and
ends without doing anything
[EMAIL PROTECTED]
Received : 11.11.2003
21:17
Bitte antworten an "ADSM:
Dist Stor Manager"
I concur. I have done MOVE DATA on copypool tapes. TSM simply recopies
the original onto new copypool tapes since it knows the real "copy pool
tapes" are offsite !
Richard Sims <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
11/11/2003 02:05 PM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Move Nodedata starts and ends without doing anything
>Don't think you can do a move nodedata for a copy pool. Must be done on
=
>a primary pool.
Says the reference manual:
"The data can be located in either a primary or copy storage pool."
The problem with the attempted operation was Offsitedness and TSM
documentation and programming shortcomings.
Richard Sims, BU
