Mark, Thanks, that is a good point, there is a difference in the sizes from the Occupancy view of the stgpools. What I don't understand is how the data was changed from the original, unless a policy expired the versions.
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stapleton, Mark Sent: Tuesday, June 01, 2004 1:21 PM To: [EMAIL PROTECTED] Subject: Re: Renaming file spaces From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bradberry, Kenneth >The problem is that I select to view the active / inactive files and all >I see is the active for that renamed file space. The retention was >changed retain 5 version for 35 days, and the renamed space hasn't had a >backup written to it since it was created. The renamed file space is >about the same size as the original space, so I would expect to see both >the active and inactive files. Remember that the filespace specs comes from the size of the filespace (UNIX & NetWare) or the drive (Windows) reported by the client to the server. If you want to know how much data is being handled by the TSM server, use OCCUPANCY instead: query occupancy <node_name> stgpool=<primary pool> -- Mark Stapleton
