Unsolved
1 Rookie
•
73 Posts
0
133
August 26th, 2023 04:24
Connection timed out backup failure
Hi Team,
One of client backup is going to hing state ,it is in waiting to run state only ,ping ,telnet looks good .
When I run from client side I am getting following error.
Unable to connect to target media device through nsrmmd
Tried initiating the backups in other devices but issue same
No Events found!
bbeckers1
2 Intern
•
191 Posts
0
August 28th, 2023 13:24
that does not say anything about the communication between backup server and NW client? So what about:
nsrrpcinfo -p <other_system>
So from nw server to client and from client to nw server?
Or using :
nsradmin -s <other_system> -p nsrexecd
So the very basics determining if both can communicate with each other? Not being restricted by a (locally running) firewall or whatever?
What are the involved OS'es, NW versions on both ends? So actual context or anything to go by, that goes beyond ping?
What do you mean with telnet looking good? What kinda connectivity check did you perform?
Do you have a support contract, and because of that access to the Dell KB, to sift through, looking into some triage guides and various KB articles stating what kind of checks to test and perform?
Djobine_f8450a
5 Posts
0
August 29th, 2023 16:08
Try the nsrrpcinfo -p <client>
between Server, client, and storage node. It should be ok between all.
It seems problem is with your storage node...
Brahmaiah E
1 Rookie
•
73 Posts
0
August 30th, 2023 16:39
@Djobine_f8450a ,find the output in attached image
Brahmaiah E
1 Rookie
•
73 Posts
0
August 30th, 2023 16:41
Brahmaiah E
1 Rookie
•
73 Posts
0
August 31st, 2023 15:45
@bbeckers1 nsradmin working wife from both the sides. telnet working fine means 7937 and 7938 ports are enabled bidirectioally
After long run it got failed with follwoing error.
Unable to find any full backups of the save set 'oralinux128:/var' in the media database. Recommending that a full backup be performed.
bbeckers1
2 Intern
•
191 Posts
0
September 12th, 2023 12:34
@Brahmaiah E that is not an error, just a message that there is no full backup yet, hence it will start making a full backup. The schedule likely is trying to make an incremental backup and that will be turned into a full backup.
NW will use more than the two ports you mentioned.
OS and NW versions involved might also give a bit more insight what we are dealing with here?
Also what about starting a client initiated backup from client end? Does that work? So doing an dtrying the very basics? So for example using https://www.dell.com/support/kbdoc/en-us/000010035?lang=en "NetWorker: How to Debug Backup Operations" as a reference? And do things like running the backup in verbose (backup command "save -D9" ro running the workflow via nsrworkflow/nsrpolicy cli commands using debug option " -D9").
https://www.dell.com/support/kbdoc/en-us/000010289 "How to use the NetWorker nsrpolicy command"
So start with the very minimal basics therefor?
(edited)