8 Krypton

Using scanner command

Hi

Question regarding scanner command.

Info:

Windows 2008 R2

EMC NetWorker server 8.1.1.2 Build 280

Reinstall NW server and reconfig manually (not using bootstrap)

small environment (less than 10 clients) & rather messy install earlier - the reason for not using bootstrap.

NW server with new name, ip and hostid

Clients reconfigured retaining client_id

Licenses rehosted @powerlink

Added AFTD devices, ran scanner on them

scanner -i \\hostname\device001

Scanner works and scans and links the SSIDs to correct client

when doing "Media -> Save sets -> save set list" the savesets are displayed correctly with all info

"Media -> Indexes" Shows indexes not zero size

"Media -> Indexes -> Show savesets" displays correct saveset info

But, when doing "Media -> Disk Volumes -> Show savesets" on the scanned volumes I get: "There are no savesets on this volume"

The mminfo command gives the same result: "no matches found for the query"

Any ideas why ?

And possibly a solution ?

Thanks

Regards

Eivind Antonsen

0 Kudos
7 Replies
8 Krypton

Re: Using scanner command

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=<VOLUME NAME> -r name

If that doesn't show anything, do:

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

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

0 Kudos
8 Krypton

Re: Using scanner command

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.

0 Kudos
Highlighted
kshariprakash
6 Indium

Re: Using scanner command

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.

0 Kudos
8 Krypton

Re: Using scanner command

Hello

Thank you for your replies.

1. mminfo:

mminfo -q volume=<VOLUME NAME> -r name

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

mminfo -avot -q volume=<VOLUME NAME> -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

0 Kudos
8 Krypton

Re: Using scanner command

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).

0 Kudos
8 Krypton

Re: Using scanner command

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

0 Kudos
8 Krypton

Re: Using scanner command

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

0 Kudos