Exchange restore failing with media read error

[charan]

exchange restore failing with media read error, kindly help on this.

18:48:59 14/04/2019: Restore Started

18:49:05 (1394571.xxx) Found (561,710) files in (8) images for Restore Job ID 1394571.xxx

18:52:14 (1394578.xxx) Found (561,710) files in (8) images for Restore Job ID 1394578.xxx

18:52:14 (1394578.xxx) Media id AWS851 is needed for the restore.

18:52:14 (1394578.xxx) Media id AWS180 is needed for the restore.

18:52:21 (1394578.xxx) Searched (      6) files of (561,710) files for Restore Job ID 1394578.xxx

18:52:21 (1394578.001) Restoring from copy 3 of image created 11/08/2018 00:59:33 from policy MER_IWP_EXCG_MBXDAG

18:54:38 (1394578.001) INF - If Media id AWS851 is not in a robotic library administrative interaction may be required to satisfy this mount request.

18:55:25 (1394578.001) INF - Waiting for mount of media id AWS851 on server AWSNBUMER004.bk.globalinfra.net for reading.

18:56:22 (1394578.001) INF - Waiting for positioning of media id AWS851 on server AWSNBUMER004.bk.globalinfra.net for reading.

18:56:24 (1394578.001) INF - Beginning restore from server AWSNBUMER004.bk.globalinfra.net to client AWSEXMMER001 (client_hostname AWSEXMMER001).

18:56:24 (1394578.001) TAR - Microsoft Exchange Database Availability Groups:\

18:56:24 (1394578.001) TAR - Microsoft Exchange Database Availability Groups:\AWSMBXDAG.globalinfra.net\

18:56:24 (1394578.001) TAR - Microsoft Exchange Database Availability Groups:\AWSMBXDAG.globalinfra.net\Microsoft Information Store\

18:56:24 (1394578.001) TAR - Microsoft Exchange Database Availability Groups:\AWSMBXDAG.globalinfra.net\Microsoft Information Store\AWSUSERMBXDB4\

18:56:24 (1394578.001) MNR - The file was renamed to the following:

18:56:24 (1394578.001) UTF - Microsoft Exchange Database Availability Groups:\AWSMBXDAG.globalinfra.net\Microsoft Information Store\RDB1\

18:57:07 (1394578.001) TAR - Microsoft Exchange Database Availability Groups:\AWSMBXDAG.globalinfra.net\Microsoft Information Store\AWSUSERMBXDB4\Database

18:57:07 (1394578.001) MNR - The file was renamed to the following:

18:57:07 (1394578.001) UTF - Microsoft Exchange Database Availability Groups:\AWSMBXDAG.globalinfra.net\Microsoft Information Store\RDB1\Database

15:21:28 (1394578.001) The following files/folders were not restored:

15:21:28 (1394578.001) UTF - /Microsoft Exchange Database Availability Groups/AWSMBXDAG.globalinfra.net/Microsoft Information Store/AWSUSERMBXDB4/Database

15:21:28 (1394578.001) UTF - /Microsoft Exchange Database Availability Groups/AWSMBXDAG.globalinfra.net/Microsoft Information Store/AWSUSERMBXDB4/Logs_1533931350

15:21:31 (1394578.001) INF - There are no jobs remaining for this restore request. Exchange database recovery will be performed.

15:21:32 (1394578.001) Status of restore from copy 3 of image created 11/08/2018 00:59:33 = media read error

15:21:35 INF - Server status = 85

15:21:36 (1394578.xxx) INF - Status = media read error.

15:21:37 INF - Server status = 5

[Marianne]

@charan 

You need bptm log on media server AWSNBUMER004.... to see if there is more info about the 'media read error'.

Level 3 bptm log should give sufficient info. 

If bptm log folder does not exist under ...\NetBackup\logs, please create the folder, increase logging level for BPTM for this media server, then retry the restore. 

[charan]

thanks for your assistence, as per suggestion i'll check the btm log folder..
but i have a doubt here if i increase the verbocity and start the restore i should i know the job will select on this media server.. please clear this one

[Marianne]

In the case of tape, the media is 'owned' by the the media server that wrote the backup copy. 
Here the media is owned by the media server that you can see in Job Details. 
Restore instruction from images that are written on these tapes will therefore be sent to the 'owning' media server.

You can always confirm with 'Tape List Report'. 

If you want to restore using a different media server, it has to be configured manually. 
It will not happen automatically.