Its not entirely clear what you are doing here - which client/server are you running this from?
Secondly you have said you are recovering a big file but the restore indicates you are recovering a directory:
Requesting remaining 76 file(s)
There appears to be some kind of communication issue going on here but it will help to know what is going on first. Also where does the client you are recovering (PSLAVE) backup to?
PSLAVE is where the data is living. and I want to recover the data to BAK. ./var/ibdata4 is the 20G file. and after that there are 76 files need to recover. also failed. when i try to recover ibdata4 file I got the following message. recover> recover Recovering 1 file from /data/mysql3306/var/ into /bak Volumes needed (all near-line): 000002 at ADIC@0.0.1 Total estimated disk space needed for recover is 20 GB. Requesting 1 file(s), this may take a while... ./ibdata4 4131:recover: Could not send indication to jobd. 39078:recover: SYSTEM error: Connection reset by peer
5041:recover: Unable to read checksum from save stream
4131:recover: Could not send indication to jobd. 39078:recover: SYSTEM error: Invalid argument
16294:recover: Encountered an error recovering ./ibdata4
16304:recover: Message from NSR server `BackupServer': bad rsid 4131:recover: Could not send indication to jobd. 39078:recover: SYSTEM error: Invalid argument
4131:recover: Could not send indication to jobd. 39078:recover: SYSTEM error: Connection reset by peer
jobd is the job daemon which starts and keeps track of Networker processes; if you are having problems communicating with it then you will have problems.
I would suggest restarting the Networker client where you are doing the restore; also can you verify that the Networker storage node is on the same version of Networker as the backup server?
DavidHampson
2 Intern
•
1.1K Posts
0
July 3rd, 2009 01:00
Secondly you have said you are recovering a big file but the restore indicates you are recovering a directory:
Requesting remaining 76 file(s)
There appears to be some kind of communication issue going on here but it will help to know what is going on first. Also where does the client you are recovering (PSLAVE) backup to?
DIDI4
2 Posts
0
July 3rd, 2009 02:00
and I want to recover the data to BAK.
./var/ibdata4 is the 20G file. and after that there are 76 files need to recover. also failed.
when i try to recover ibdata4 file I got the following message.
recover> recover
Recovering 1 file from /data/mysql3306/var/ into /bak
Volumes needed (all near-line):
000002 at ADIC@0.0.1
Total estimated disk space needed for recover is 20 GB.
Requesting 1 file(s), this may take a while...
./ibdata4
4131:recover: Could not send indication to jobd.
39078:recover: SYSTEM error: Connection reset by peer
5041:recover: Unable to read checksum from save stream
4131:recover: Could not send indication to jobd.
39078:recover: SYSTEM error: Invalid argument
16294:recover: Encountered an error recovering ./ibdata4
16304:recover: Message from NSR server `BackupServer': bad rsid
4131:recover: Could not send indication to jobd.
39078:recover: SYSTEM error: Invalid argument
52973:recover: Didn't recover requested file ./ibdata4
Received 0 file(s) from NSR server `BackupServer'
Recover errors with 1 file(s)
Recover completion time: Thu 02 Jul 2009 08:43:57 PM CST
DavidHampson
2 Intern
•
1.1K Posts
0
July 3rd, 2009 02:00
4131:recover: Could not send indication to jobd.
39078:recover: SYSTEM error: Connection reset by peer
jobd is the job daemon which starts and keeps track of Networker processes; if you are having problems communicating with it then you will have problems.
I would suggest restarting the Networker client where you are doing the restore; also can you verify that the Networker storage node is on the same version of Networker as the backup server?