Could be just GUI.  I don't trust GUI - it is like make up - I'm more interested in things beneath.  What you did translates to following command:

mminfo -q volume= -r name

If that doesn't show anything, do:

mminfo -avot -q volume= -r name,ssid,ssflags,sumflags,clflags,group,client,savetime

If that doesn't show anything - then something is wrong big time.

Before you do anything else, verify that the info from the GUI matches the one from the command line.

One possible issue is that you have choosen a shorter retention policy than our old setup. As a consequence, NW might have run the cleanup procedure (nsrim) in the interim and may have deleted older save sets (on an AFTD).

Hope that the save sets still exist. If so,

- increase the rention policy for your clients apprpriately and

- rescan the mdia.

Otherwise, i am afraind that the save sets have been deleted from your AFTD.

You can verify that if you search for all files on the AFTD location.

Hi,

Since the networker server is hosted with a different name , Can you perform a scanner for a single SSID & post the result.

scannerr -vvv -i "device_name"

Regards

Hari Prakash.

Hello

Thank you for your replies.

1. mminfo:

mminfo -q volume= -r name

Result:6095:mminfo: no matches found for the query

mminfo -avot -q volume= -r name,ssid,ssflags,sumflags,clflags,group,client,savetime

Result: 6095:mminfo: no matches found for the query

2. Retention:

Browse/retention is set to year/year for all clients so that should not be the issue

3. scanner -vvv -i "device_name"

Reran scanner on one of the volumes, here are examples of the output

32334:scanner: (ssid 331996587) hostname:/path/to/file @ time 1388961194 not found in index

32333:scanner: (ssid 2362887434) hostname:/path/to/file off 1847065960, size 912

32336:scanner: (ssid 1908914241) hostname:/path/to/file.lock @ time 1388820543 confirmed in index

32336:scanner: (ssid 2362887434) hostname:/path/to/file @ time 1389808931 confirmed in index

32333:scanner: (ssid 331996587) hostname:/path/to/file.log off 1114116740, size 142832

32333:scanner: (ssid 3763098515) hostname:/path/to/file.pdf off 1843562800, size 2252772

32333:scanner: (ssid 1908914241) hostname:/path/to/file.lock off 18052432, size 272

32334:scanner: (ssid 331996587) hostname:/path/to/file.log @ time 1388961194 not found in index

32336:scanner: (ssid 3763098515) hostname:/path/to/file.pdf @ time 1380733842 confirmed in index

32336:scanner: (ssid 1908914241) hostname:/path/to/file.lock @ time 1388820543 confirmed in index

32333:scanner: (ssid 3763098515) hostname:/path/to/file.msg off 1845815572, size 25600

32333:scanner: (ssid 1908914241) hostname:/path/to/file.lock off 18052704, size 252

32336:scanner: (ssid 3763098515) hostname:/path/to/file.msg @ time 1380733842 confirmed in index

32336:scanner: (ssid 1908914241) hostname:/path/to/file.lock @ time 1388820543 confirmed in index

32333:scanner: (ssid 1908914241) hostname:/path/to/file.lock off 18052956, size 272

32336:scanner: (ssid 1908914241) hostname:/path/to/file.lock @ time 1388820543 confirmed in index

Please note (I should have put this in the original post maybe):

These devices are extremely large dedupe AFTD devices. (logical size that is)

The scanner takes days to complete for each volume

and, in the GUI "media - > disk volumes" lists the affected volumes as zero size

Thanks

Eivind

Pick one ssid and do query, for example:

mminfo -q ssid=331996587 -r volume,ssbrowse,ssretent,name,client,ssflags,sumflags,clflags

I find a bit strange that volume query showed nothing, but perhaps volume name used was not correct (above command will give you volume name in first column).

Hi

The above command displays the expected results.

What I'll do next is re-run scanner and see if that helps.

I'll update this post after that has been done, may take over a week to complete.

Cheers

Eivind

Hello

The scanner command ran for 11+ days on each device.

After new successful scan the devices now show data as expected.

Unsure why they didn't before.

Cheers

Eivind A