NSRSTAGE command line trouble

Something seems to be corrupted. The best thing would be to have someone put its hands on that. Support should be able to connect via Webex and check what is the problem. Simply escalate your problem and ask for Webex session for someone to see and check what is really going on.

The output you sent from nsrstage is not staging anything - usually it will list ssids to be staged. In your case it just reported some space would be recovered and nothing else.

What do you see when you do following:
mminfo -av -q volume=nexan -r ssid,cloneid,copies,ssflags,sumflags,name,client,sumsize

This will give you list of savesets and few more details for each ssid on that disk volume. Then let's see what happens when we try one to stage.

I just realized that staging source is on backup server and data is being staged to remote storage node. Given that nsrstage and nsrclone "share" same thing I must say I have no idea if you should configure clone storage node field too. If yes, go to properties of backup server client (backupserver) and in field called clone storage node put backupserver2.

Actually you did. Just found it so sorry for the repost. This is what I get when I run the command:

Obtaining media database information on server backupserver
obtaining volume information
recovering space from volume (nexsan)
Refer to daemon.log for any space recoverd

I know this worked but let me try a little better to break it down. Here are my devices:

e:\legato nexsan
e:\legato_AF_readonly nexsan.RO
rd=backupserver2:\\.\ backupserver_c.101 (my currently loaded tape)

Tape is mounted and tells type.

My problem is I can't get the volume percentage down from 94% on my nexsan (not the nexsan.RO). My tape hasn't been written to in two days. For some reason it's not writing off to my tape. Any ideas

Is your staging enabled at all? (trying to be funny)

Well, I believe I did write this somewhere else, perhaps even for you at some other topic, but here we go again:
nsrstage -s nsrstage -s backupserver -v -m -bPUT_TARGET_POOL_NAME_HERE -S `mminfo -av -q volume=DISK_VOLUME_NAME_HERE -r ssid`

You are correct. I checked the daemon.log and found a SSID that says it's inpro since april 17th. I've restarted that server 3 times since then!! My question is how to I delete a specific SSID. This seems to be wha't holding things up

With ssid gone, mminfo should not report it anymore at all. So, to exclude cache issues try to stop NetWorker server, delete /nsr/tmp and then start it again. Hopefully this time it will work. If not, then list ssids and simply stage them - your list won't have offending ssid so it should work.

This is the command I entered:

nsrmm -dy -S 23876773192 /cloneid

It tells me '-S and volume names are mutually exclusive'

what'd I do wrong

I'll give it a try. Sorry for all the stupid questions but I have one more. When you say 'list ssids' how do I do that. Thanks


If not, then list ssids and simply stage them - your list won't have offending ssid so it should work.

Think I got somewhere. I did nsrmm -d -S 2386773192

It asked if I wanted to delete file and media index entries for save set. I said Yes. Looked ok so I did nsrstage and got same as before:


I looked in daemon.log again and saw this:

cannot clone save set 2386773192 series is corrupted. When I went back and looked on my e:\ nexsan the SSID IS gone. Is there something else (since it says series is corrupt) or do I need to like restart the server or somethng? I do appreciate all of your help greatly

Actually, use nsrmm -dy -S ssid/cloneid

If you just use ssid then you will delete staged instance too (check copies and volumes for that ssid).

You are missing cloneid.

Do first: mminfo -av -q ssid=23876773192 -r cloneid,sumflags,name,client,ssflags,sumflags,savetime,copies,volume,pool

If in media database use nsrmm eg. nsrmm -dy -S ssid.

I would advise to run mminfo -av -q ssid=your_ssid -r "ssid(60)" This will report ssid in long format and that name will be the same as filename on disk volume containing that (short) ssid.

Do mminfo -av -q volume=nexan -r ssid > ssid.lst and then nsrstage -s backupserver -m -v -bPOOL -S -f full/path/to/file/from/previous/command/called/ssid.lst

Well gotten further. I go to the backupserver itself and type this:

nsrstage -v -s backupserver-b defaultclone -C -V nexsan
obtaining media database information on server backupserver
obtaining volume informaion
recovering space from volume (nexsan)
nsrstage: adv_file disk e:\legat0\_AF_readonly is ready for reading.

seems ok. When I go to the monitor tab I see this:

media info: suggest manually labeling a new writable volume for pool 'default'
media waiting event: waiting for 1 writeable volumes to backup pool 'default' disk(s) or tape(s) on backupserver2.

The tapes I have are all blank. Not sure what it's asking for

When I try either of those I get:

only save set migration is allowed. i'm wondering it it's not connected to my stupid other error

?? But you are migrating the savesets... Oh, back to earlier plan - make a list of ssids in the file and run it manually. That should work. That must work. Otherwise you have either gremlins or something is really really messed up there.