Recover data from cluster windows

studro

Active Newcomer
Joined
Dec 15, 2008
Messages
8
Reaction score
0
Points
0
PREDATAR Control23

Hi,

I want to recover data from a cluster windows. But I have the following error message :

C:\Users\Admserv>recover -s hefrbck06-226.hefr.ch -c hefrsql03.sofr.hefr.lan -R hefrdb03.sofr.hefr.lan -iR
No index was found for C:\Users\Admserv\. The current working directory is /.
recover> cd u:\backup\bande
recover> changetime 06/24/2014
18361:recover: time changed to 06/24/2014 23:59:59 (mm/dd/yyyy)
recover> add SAFEQDB_backup_2014_06_23*.bak
1 file(s) marked for recovery
recover> recover
Recovering 1 file into its original location
Volumes needed (all near-line):
USRS25L4 at SL500
Total estimated disk space needed for recover is 73 MB.
Requesting 1 file(s), this may take a while...
Recover start time: 7/10/2014 10:51:20a
Requesting 1 recover session(s) from server.
53363:recover: Recover of rsid 21859 failed: Port mapper failure - RPC receive operation failed
73724:recover: One or more recover threads failed to exit successfully
73731:recover: Parent recover thread exited with errors
52973:recover: Didn't recover requested file U:\backup\bande\SAFEQDB_backup_2014_06_23_012731_0331209.bak

Received 0 file(s) from NSR server `hefrbck06-226.hefr.ch'
Recover completion time: 7/10/2014 10:55:41a
recover> quit

I need an urgent help.

Regards
/Olivier
 
PREDATAR Control23

Studro,
Where are you running this restore from? I would suggest you to run it from the destination server, in you case on hefrdb03.sofr.hefr.lan. Also ensure that the Remote access filed on Globals 2 of 2 of the client properties of hefrsql03.sofr.hefr.lan contains *@hefrdb03.sofr.hefr.lan.
 
PREDATAR Control23

Hi,

It's the same status after test your configuration. The problem is with the port mapper. The server Networker can not able to use the port 111 on the same IP address using to do the backup. My server has multiple interfaces.

Regards
/Olivier
 
PREDATAR Control23

By "My Server" i assume you mean your backup server ! Why not give the correct IP of the backup server with the recover command. Id there was a problem with the port mapper the backup should not happen either.
 
PREDATAR Control23

Yes my server equals the backup server. When I use the IP address or the FQN of the server with the commande recover, it's the same result.

exemple:

recover -vvv -s hefrbck06-226.hefr.ch -c hefrsql03.sofr.hefr.lan -R hefrdb03.sofr.hefr.lan -iN

the server hefrbck06 has 6 interfaces

regards
/Olivier
 
PREDATAR Control23

You source and target client have the domain hefr.lan and that of you backup server is hefr.ch. I hope all these are in the same VLAN or alteast have full access to each other.
 
PREDATAR Control23

It's the same VLAN. The name of the VLAN is indicate on the FQN of the server, 226. hefrbck06-226 = 10.98.226.191

But the default route of the networker server is 10.98.2.1 with the name hefrbck06. And the default route of the client hefrsql03 equal 10.98.226.1.

Regards
/Olivier
 
PREDATAR Control23

53363:recover: Recover of rsid 21859 failed: Port mapper failure - RPC receive operation failed that indicates connection problem not Networker itself. All those questions from other users about you VLAN's are coming from this. Verify entries in DNS then in local /etc/hosts or windows path. Check connectivity before : from the client: nsradmin –s <server_name> -p 390113 and from the server : nsradmin –s <client_name> -p 390113. Then post us output of those.
 
Top