yampam
ADSM.ORG Member
- Joined
- Dec 19, 2006
- Messages
- 101
- Reaction score
- 0
- Points
- 0
Hi all ,
I'm using TSM v5.4 with DRM Virtaul volumes .
I've got this massage on many volumes on my remote stgpool any time reclamation process starts:
ANR1163W Offsite volume NEWR.BFS.133705358 still contains files which could not be moved .
Move data on this volume works -but insted of using the primary stgpool like on reclamation ,it move the data direcdly from this vol to a new virtual volume.-How can I know if the primary STGpool data is stil valid ? I assume that this is the reason the "files could not be moved" .
I think Expiration works fine , but yet the copy pool of the virtual volumes is 3 times bigger then the copy stgpool !!! -maybe (again) becouse of this volumes that cannot be moved .
I tried audit volume fix=yes on one of the volumes that couse this massage - no damaged files detected .
I'm using TSM v5.4 with DRM Virtaul volumes .
I've got this massage on many volumes on my remote stgpool any time reclamation process starts:
ANR1163W Offsite volume NEWR.BFS.133705358 still contains files which could not be moved .
Move data on this volume works -but insted of using the primary stgpool like on reclamation ,it move the data direcdly from this vol to a new virtual volume.-How can I know if the primary STGpool data is stil valid ? I assume that this is the reason the "files could not be moved" .
I think Expiration works fine , but yet the copy pool of the virtual volumes is 3 times bigger then the copy stgpool !!! -maybe (again) becouse of this volumes that cannot be moved .
I tried audit volume fix=yes on one of the volumes that couse this massage - no damaged files detected .
