09-17-2013 03:24 AM
Master server NBU version: 126.96.36.199
Master server os: Server 2003
client NBU version: 7.1
Restore has been failed with error code 13 and no tar logs has been generated.
Please find job detail below..
9/17/2013 9:59:31 AM - begin Restore
9/17/2013 9:59:33 AM - media CIF136 required
9/17/2013 9:59:33 AM - restoring image gbsx5770_1314675566
9/17/2013 9:59:38 AM - Info bpbrm(pid=3340) gbsx5770 is the host to restore to
9/17/2013 9:59:38 AM - Info bpbrm(pid=3340) reading file list from client
9/17/2013 9:59:44 AM - connecting
9/17/2013 9:59:44 AM - Info bpbrm(pid=3340) starting bptm
9/17/2013 9:59:49 AM - Info mtfrd(pid=13452) Restore started
9/17/2013 9:59:49 AM - connected; connect time: 00:00:05
9/17/2013 9:59:49 AM - Info bptm(pid=3248) start
9/17/2013 9:59:49 AM - started process bptm (3248)
9/17/2013 9:59:49 AM - Info bpdm(pid=3248) reading backup image
9/17/2013 9:59:50 AM - Info bptm(pid=3248) using 256 data buffers
9/17/2013 9:59:50 AM - Info bptm(pid=3248) spawning a child process
9/17/2013 9:59:50 AM - Info bptm(pid=3248) child pid: 9740
9/17/2013 9:59:50 AM - Info bptm(pid=9740) start
9/17/2013 9:59:50 AM - started process bptm (9740)
9/17/2013 9:59:50 AM - Info bptm(pid=3248) Waiting for mount of media id CIF136 (copy 1) on server gbensb5502.
9/17/2013 9:59:50 AM - started process bptm (3248)
9/17/2013 9:59:50 AM - mounting CIF136
9/17/2013 9:59:50 AM - Info bptm(pid=3248) INF - Waiting for mount of media id CIF136 on server gbensb5502 for reading.
9/17/2013 9:59:50 AM - requesting resource CIF136
9/17/2013 9:59:50 AM - granted resource CIF136
9/17/2013 9:59:50 AM - granted resource HP.ULTRIUM4-SCSI.000
9/17/2013 10:00:44 AM - mounted; mount time: 00:00:54
9/17/2013 10:00:44 AM - Info bptm(pid=3248) CIF136
9/17/2013 10:00:45 AM - Info bptm(pid=3248) INF - Waiting for positioning of media id CIF136 on server gbensb5502 for reading.
9/17/2013 10:00:45 AM - positioning CIF136 to file 29
9/17/2013 10:01:03 AM - positioned CIF136; position time: 00:00:18
9/17/2013 10:01:04 AM - begin reading
9/17/2013 10:57:03 AM - Info bptm(pid=3248) waited for empty buffer 46528 times, delayed 173423 times
9/17/2013 10:57:03 AM - end reading; read time: 00:55:59
9/17/2013 10:57:04 AM - Info bptm(pid=3248) completed reading backup image
9/17/2013 10:57:04 AM - Info bptm(pid=3248) EXITING with status 0 <----------
9/17/2013 11:09:34 AM - Error bpbrm(pid=3340) socket read failed, An existing connection was forcibly closed by the remote host. (10054)
9/17/2013 11:09:34 AM - restored image gbsx5770_1314675566 - (file read failed(13)); restore time 01:10:01
9/17/2013 11:09:35 AM - end Restore; elapsed time: 01:10:04
MS-Exchange-Server policy restore error(2810)
9/17/2013 11:09:39 AM - Info mtfrd(pid=13452) done. status: 13: file read failed
9/17/2013 11:09:39 AM - Error bpbrm(pid=3340) client restore EXIT STATUS 13: file read failed
There is one physical node and two virtual nodes
09-17-2013 05:06 AM
if you trigger the restore job from the Mater server could you also show the restore log
below is the default log location if you dont chage the log path at restore
09-18-2013 05:48 AM
user id from which i fired the restore is not present there
09-18-2013 06:16 AM
09-18-2013 06:18 AM
Does this restore trigger from Exchage server , or someother server? or From Master server?
it looks like your backup is from Tue, 30 Aug 2011 03:39:26 GMT.
could you check if the backup in the tape is fine... may be you can verifiry this by using the Verify option in GUI--> catalog or from bpverify command
alternatily you can try duplcating the image to another tape or disk and try restoring from there..
09-18-2013 06:27 AM
You need to upgrade your client to 188.8.131.52 to match the Master and Media Servers - lots of bugs and support will say that for exchange restores the version and patch levels should match
09-19-2013 11:18 PM
This Restore was triggered from master server. Master server version is 184.108.40.206.
Exchange version is 2007.
During Restore i am not able to check "Redirect the Recovery Storage Group(only for exchange 2007)"
09-20-2013 03:27 AM
Just noticed one other thing here ... it looks like the restore worked but the final communication did not
There is a gap while it ran of over an hour so i am thinking that there is a firewall between the NetBackup Servers and the Exchange Server and the issue is caused by a keep alive setting on the firewall
Please confirm if this could be the case as a change in the setting of your firewall (or maybe on the servers) may well resolve your issue
In any case your client should also be 220.127.116.11