Re: "q occ" and "q backup" show huge differences

Hi, thanks for your postings: The problem is resolved. I made my queries from a linux client. The node was an aix client. When I do the same queries from aix I get the correct results. regards, Volker Am Donnerstag, den 23.02.2006, 09:31 -0500 schrieb Paul Zarnowski: > Keep in mind that Q OCC

Re: "q occ" and "q backup" show huge differences

You could also run a select: dsmadmc -tab -id=xxx -pass=xxx "select * from backups where nodename=''" > sel.bkp This will take a while to run, but shouldn't be too bad. At 10:17 AM 2/23/2006, Richard Sims wrote: Volker - Given that this data came in all at once in an Import (from an unusual

Re: "q occ" and "q backup" show huge differences

Volker - Given that this data came in all at once in an Import (from an unusual server type, VM), it is probably concentrated on a few volumes. To settle the issue, I would perform a Query CONtent on the volume(s), to a disk file, and browse that listing to see what's actually out there. (Query C

Re: "q occ" and "q backup" show huge differences

Yes, but "q backup -inact -subdir=yes /filespace/" includes directories and files both active and inactive. And the number of files and directories I get from this command isn't even the half of what q occ shows for the primary stgpool. Am Donnerstag, den 23.02.2006, 09:31 -0500 schrieb Paul Zarn

Re: "q occ" and "q backup" show huge differences

Keep in mind that Q OCC is showing "objects", not "files". This includes directory objects. At 02:10 AM 2/23/2006, Volker Maibaum wrote: The strange thing is, that q occ shows me that there should be 441.000 files in the primary stgpool and q backup (-inact -subdir=yes) shows only 190.000 files

Re: "q occ" and "q backup" show huge differences

Hi, yes there are two lines for that specific filespace. One for primary and one for the copy stg pool. The strange thing is, that q occ shows me that there should be 441.000 files in the primary stgpool and q backup (-inact -subdir=yes) shows only 190.000 files. Am Mittwoch, den 22.02.2006

Re: "q occ" and "q backup" show huge differences

Query OCCupancy reports primary and copy storage pool populations. The client is obviously unaware of copy storage pools, which are exclusively the server's interest. The output of the Query OCCupancy *should* include one line for each storage pool instance. Something may be awry if that is not t