Re: [Networker] Strange Output From "nsrim -X"
2013-02-11 15:53:55
Bryan,
I also recommend that you do a file system integrity check on your NetWorker
server while all the NetWorker processes are shut down.
On Feb 11, 2013, at 2:41 PM, "Bowersock, Bryan" <Bryan.Bowersock AT AHSS DOT
ORG> wrote:
> 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.
>
|
|
|