There is no inconsistency in the data between the TSM server and client, in that the client maintains no information about archived files: all information is in the TSM server database.
The common reasons for not seeing files from the client are that the files belong to a different node or username than is being employed in the client lookup operation. If operating on someone else's files, be superuser in order to accomplish it. And you will not see Archive files in Restore, because they require Retrieve. I'd recommend performing a 'dsmc query archive' operation, meaning command line, rather than using the GUI, for best results. Note that some of the objects you may be trying to remove could be directories rather than files, so allow for that. There have been some unusual circumstances with Archive files over TSM releases, as you can see in APARs research, which sometimes require running special utility commands; but eliminate trivial causes of your lookup issue before contemplating looking into that. Richard Sims at Boston University On Dec 21, 2009, at 7:06 AM, Geert De Pecker wrote: > Hi, > > We are having problems to remove old archives: > > On a weekly basis, we are running a script as below: > "select node_name, description as \"Archive Description\" ,count(*) as > \"#Files\" from archives group by node_name,description" > > This should give us all archives that are kept by TSM. This list however > contains a lot of archives that do not show > up in the client GUI (either in the "Delete archive data" or in the > "Restore"). > > I am assuming there is some inconsistency in the data between the client > and the server. > > Is there a way to synchronize this? > > Thanks, > > Geert
