Funny enough, we don't have a server with that name so I don't know what server 
it is referring to...here is another example where I can actually determine the 
name of the server:



nsrck: checking index for 'tempus'

nsrck: D:\nsr\index\app5 contains 3853741 records occupying 442 MB

nsrck: checking index for 'APP6'

nsrck: D:\nsr\index\uchedir contains 8603136 records occupying 1165 MB

nsrck: checking index for 'UCHFRAMESQL1'



nsrcnks:r cDk::\ nDs:r\\nisnrd\eixn\dteaxm\vtaepmppiubse xc0o1n tcaoinntsa 
i7n9s5 824552 8r4e2c2o6r drse coocrcdusp yoicncgu p9y9i nMgB

937 MBn

rck: cnhsercckki:n gc hiencdkeixn gf oirn d'etxe mfpours d'bT'A

VAPPLBI01'



nsrck: D:\nsr\index\uchsdidbsvr contains 893098 records occupying 119 MB



Fortunately for me, I recognize a part of the name of the server in this 
example, which is TAMVAPPLBI01.  I can put it together from the last part of 
the "garble".  Unfortunately, this does not happen every time and the hostname 
is not always clear.  I checked your suggestion on the server mentioned in this 
email and none of the volumes have a non-standard character in the name.



C:\ = Local Disk

D:\ = Data

P:\ = Page







Bryan B



-----Original Message-----
From: Stanley R. Horwitz [mailto:stan AT temple DOT edu]
Sent: Monday, February 11, 2013 2:25 PM
To: EMC NetWorker discussion; Bowersock, Bryan
Subject: Re: [Networker] Strange Output From "nsrim -X"



I wonder if that ricnkd server have a disk drive (the e:\ volume) with a name 
in non-standard characters that NetWorker does not support or render properly.



On Feb 11, 2013, at 2:02 PM, "Bowersock, Bryan" <Bryan.Bowersock AT AHSS DOT 
ORG<mailto:Bryan.Bowersock AT AHSS DOT ORG>>

wrote:



> Hello all,

>

> I ran the command "nsrim -X" on our Networker server today and noticed some 
> strange output.  We are running Networker 8.0.0.1 and the NMC is on the same 
> server.  The OS is Windows 2008 R2 64-bit SP1 and is a physical host.  I am 
> logged into the server as the same account (domain service account and is 
> also a local administrator of the Networker server) that I always have which 
> is also the account that is set to run the Networker Backup and Recover 
> Server service and the Networker Remote Exec service.  Has anyone ever seen 
> this?  This happens more than once during the run of the command where the 
> output comes up as "garble"...thoughts?  Last week I did a consistency check 
> of all of the CFI by running "nsrck -L6" and everything appeared to be fine.  
> I'm wondering if this is a permissions issue in Networker, in Windows, a 
> corrupt index, or even worse, a corrupt media database.  Everything in 
> Networker is currently running fine.  Below is an example:

>

>

> nsrck: D:\nsr\index\adserver1 contains 1249138 records occupying 163 MB

> nsrck: D:\nsr\index\lawsonapp contains 27026525 records occupying 4120 MB

> nsrck: D:\nsr\index\openlinksvr2 contains 1038638 records occupying 133 MB

>

> nsrck: checkinngs ricnkd:e xc hfeocrnk si'rnTcgAk M:iV nVcndIhseDerxWcc 
> EkkfBi:no0n sr1gcr ' hc'

> nc:Adk MeicVxnhA gePf cPoikCrniA dnC'egSax 0d i1sfn'eod

> v xe' rLf2ao'wr

> o'nOdPbL'C

> STR'

>

> nsrck: D:\nsr\index\oplclstr contains 592 records occupying 95 KB

> nsrck: checking index for 'OPLGRPA'

> nsrck: D:\nsr\index\tamvappcacs01 contains 32870 records occupying 3802 KB

> nsrck: checking index for 'TAMVAPPCACS02'

> nsrck: D:\nsr\index\oplgrpa contains 41093 records occupying 5239 KB

> nsrck: checking index for 'OPLGRPB'

> nsrck: D:\nsr\index\oplgrpb contains 17275 records occupying 2278 KB

> nsrck: checking index for 'OPSXP-IS-MC'

> nsrck: D:\nsr\index\lawsondb contains 4563100 records occupying 734 MB

> nsrck: checking index for 'LBISVR'

> nsrck: D:\nsr\index\lbisvr contains 2816421 records occupying 427 MB

>

>

> Thanks in advance.

>

> Bryan B.

> Storage / Backup Administrator