This post is more than 5 years old
9 Posts
0
6158
Recovering with no client
Hello,
I am brand new to using Networker, and inherited a v. 8 server with a bunch of expired tapes. With a lot of reading, I was able to make the expired savesets browseable (yay!), but am getting this error when I recover a few files: "No matching devices on 'server' for recover by client 'clientname'"
The server is the original server, but I had to use a different tape library (old one doesn't work anymore). The client doesn't exist anymore. I read in another discussion (https://community.emc.com/thread/119521?tstart=0 ) that I'd need to make a dummy client, but I am not sure how.
Is there another way to recover a few files without the client present?
Many thanks for your thoughts!
wlee
263 Posts
0
January 22nd, 2018 20:00
I see 2 devices. One is the \\.\Tape#### (correct path to the new library) and the other device is the serverfqdn:\\.\Tape#### path
Since both drives are the server drives... this seems to be a tape drive configuration issue. Because of this confusion, this could be the reason why NetWorker is unable to find a device to use to read the tape.
I had to use a different tape library (old one doesn't work anymore).
Is the old tape library still defined in NetWorker? Is it still connected? Is the new tape library defined and configured in NetWorker?
Required volume [tape barcode]'s status is near-line
near-line usually means that NetWorker has access to the tape, but it is unable to find a free device to load and mount the tape onto. What type of tape media is this? Do you currently have a tape drive that supports loading and reading this type of media?
Suggestion.
Even though you are running NetWorker 8.0.2, this is a recovery issue, so you can try to open a support ticket for assistance with the recovery.
bingo.1
2.4K Posts
1
January 15th, 2018 03:00
Just create an valid name entry in the hosts file. After that you will be able to create the client resource.
And do not forget that you might have enabled your pool for certain devices. Of course the ones not selected here are automatically disabled.
dangapinski
9 Posts
0
January 16th, 2018 06:00
Thanks for your response Bingo!
I have a valid entry name in hosts for this backup server. I also have a hosts entry for the dummy client (named as the old client), which pings ok.
OK, now I have a slightly different error:
53365:winworkr:NSR server 'serverfqdn': no matching devices on 'server'
71739:winworkr:Warning: Required volume [tape barcode]'s status is near-line
71740:winworkr:Waiting 30 seconds and then retrying
This tape is reloaded and if I look at the Management Console under the servers, I see 2 devices. One is the \\.\Tape#### (correct path to the new library) and the other device is the serverfqdn:\\.\Tape#### path
not sure where to take this - I still need help. Thanks for your time
dangapinski
9 Posts
0
January 17th, 2018 07:00
I should clarify that this message ("53365:winworkr:NSR server 'serverfqdn': no matching devices on 'server'"), 'serverfqdn' is a real fqdn to the backup server. Where the message says 'server', I did not translate - it merely says that. So I'm not sure where to look at 'server' to find its devices.
bingo.1
2.4K Posts
0
January 18th, 2018 11:00
Look at your client's recover storage node list and add the appropriate entry here.
Also verify whether you have restricted the pool for special/other devices.
dangapinski
9 Posts
0
January 18th, 2018 12:00
Fail on both things that I tried - i.e., same error when I change the client's recovery storage node to just the backup server hostname (not FQDN) and checking the tape drive in the pools. Any other thoughts? Here are images of my config, if it helps:
dangapinski
9 Posts
0
January 18th, 2018 12:00
being new to this, I want to make sure my terminology is right. (A line from one of my favorite video games: "Pretend you're talking to a small and perhaps a very stupid child.")
OK in the Recovery storage node for the client (that I'm trying to recover data for), I added the backup server fqdn. No change when I started restoring. I will try using just the backup server hostname and see what happens
By restricting the pool, do you mean if I have any libraries checked in the config? I do not. I will try checking and see what happens.
Thanks for your help!
dangapinski
9 Posts
0
January 22nd, 2018 06:00
[bump] - still in great need of help
bingo.1
2.4K Posts
1
January 22nd, 2018 09:00
If you have not defined any device for the pool, your secret is obviously with the 'storage node affinity list" (in the
"globals (2 of 2)" tab):
- Your storage node for the backup is the NW server (nsrserverhost)
- Your storage node for the recovery is "iausbak01". So this is where the NW server expects the media to be mounted.
If you delete this entry, you should be able to mount wherever a compatible device is available.
dangapinski
9 Posts
0
January 22nd, 2018 11:00
I really do appreciate your sticking with me on this problem!
I hate to say it, but that's not it. If I remove the server from the client's storage node for recovery, then I get the same no matching devices on 'server' error. I also tried further removing the tape drive being checked in the pool properties, to no change as well. Anything else you might suggest? I will post screens as they stand now in a few minutes
dangapinski
9 Posts
0
January 22nd, 2018 11:00
I can say one odd thing though - the tape volume does not appear in Media \ Tape Volumes. I just noticed that and I'm not sure if it means anything.
Anonymous User
12 Posts
0
January 22nd, 2018 20:00
1. question....the original pool still exist? if not please create it.
2. use mminfo to get the SSID of the backup that you want to restore and do it by CLI:
recover -c "source client name" -R "destination client name" -iR "destination_path"
send us the output of the command (verbose is ON by default)
SurajPujari
155 Posts
0
January 23rd, 2018 04:00
sometime NetWorker forgets to create the pool out of the media which it has scanned, browse and see if you are able to see that pool in there.
bingo.1
2.4K Posts
0
January 23rd, 2018 05:00
"... the tape volume does not appear in Media \ Tape Volumes. I just noticed that and I'm not sure if it means anything."
If this is true, then NW does not know the tape in the media index. And of course, it cannot recover.
However, in your opening statement you said that you made "... the backups browsable again."
This of course is contradictionary information.
Load the tape into a drive. Then run the following command on the storage node:
D:\>scanner -mnv \\.\Tape########
8909:scanner: using '\\.\Tape########' as the device name
9000:scanner: \\.\Tape########: opened for reading
9003:scanner: \\.\Tape########: rewinding
9067:scanner: Rewinding done
8968:scanner: Reading the label...
8969:scanner: Reading the label done
8936:scanner: scanning LTO Ultrium-5 tape 000001L5 on \\.\Tape########
96367:scanner: volume id 3427880261 record size 262144 bytes
created 12/14/16 14:46:45 expires 12/14/18 14:46:45
8939:scanner: LTO Ultrium-5 tape 000001L5 already exists in the media index
9003:scanner: \\.\Tape########: rewinding
9067:scanner: Rewinding done
8973:scanner: setting position from fn 0, rn 0 to fn 2, rn 0
.....
^C
D:\>
As you can see here, there is a clear message about the media index.
If the tape is unknown, you must rescan it again otherwise you will not be able to mount it which is mandatory for a recovery.
dangapinski
9 Posts
0
January 23rd, 2018 08:00
THANK YOU WALLACE!!!
I saw the part about deleting the library in another post, but I didn't want to do it without a backup first, so huge thanks on both counts. Also, explaining to me what near-line meant helped a great deal, as that term in the context of that message meant almost nothing to me. I really do appreciate the intuition shared.
It is restoring - I have files now!!!