Hi Eric, For your example, \\MOLSON\C$\DATA\status.txt, the correct criteria would be:
filespace_name='\\MOLSON\C$' and hl_name='\DATA\' and ll_name='STATUS.TXT' For Windows, note that: - All components are stored in upper case, regardless of how they appear on the client machine. - The hl_name begins and ends with a backslash (unless it is the drive root, in which case there is only one backslash). - When you concatenate filespace_name, hl_name, and ll_name, they should form a proper path. Regards, Andy P.S. Suggestion: Selecting from the BACKUPS table can take a very long time. If you plan to do a lot of data mining from it, consider selecting all output from the table and redirecting to a file (make sure you have tons of free disk space), then use an external tool to mine the data. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 2005-02-27 17:54:07: > This is something I was also looking for. > Normally I go to the client machine and query the backups to see the > history of a file. > From what I can tell and I'm not very good at the "select" SQL > statements is the following a correct interpretation of the statement if > I was looking for a single files backups. > ---------------------------------------------- > Select * from backups where node_name='MOLSON" and > FILESPACE_NAME='\\MOLSON\C$' and HL_NAME='C:\DATA\' and ll_name like > 'status.txt' > -------------------------------------- > MOLSON - client node > FILESPACE_NAME - FILESPACE where file is located > HL_NAME - Directory where file is located > ll_name - actual file you are looking for > > Thanks > Eric
