NDMP Restore Failed with server not allowed access

[Ramkumar_S]

Hi,

I am going to restore the NDMP Data which has been Backedup on different Backup domain.

I added the NDMP Host and configured the credentials and verified the same.

E:\Program Files\Veritas\Volmgr\bin>tpautoconf -verify ndmphost

Connecting to host "ndmphost" as user "ndmp"...

Waiting for connect notification message...

Opening session--attempting with NDMP protocol version 4...

Opening session--successful with NDMP protocol version 4

  host supports TEXT authentication

  host supports MD5 authentication

Getting MD5 challenge from host...

Logging in using MD5 method...

Host info is:

  host name "server_2"

  os type "DartOS"

  os version "EMC Celerra File Server.T.6.0.70.4"

  host id "abc1997"

Login was successful

Host supports LOCAL backup/restore

Host supports 3-way backup/restore

--------------------------------------------------------------------------------------------------------------------

When performing the restore i'm getting the error "server not allowed access"

[Marianne]

Please tell us how backup images were moved/imported on new master from where restore is done?

Was source NAS filer also EMC Celerra?

Please show us all text in Job details of failed restore.

Please ensure that bprd log folder exists on master where you are trying to restore.
If not, create folder under ...\netbackup\logs and restart NBU Request service.

Retry restore, then copy bprd log to bprd.txt and post as File attachment along with answers to above questions.

[Ramkumar_S]

1. Exported the catalog images with the command cat_export.exe –backupid and imported on new Master server cat_import.exe –backupid

2. I’m restoring on the same EMC filer, where we have taken the Backup. Only the Master and media server is different.

3. attached Bprd logs in attachment.

Logs from Backup, Archive and Restore Window:

17:19:38 12/12/2013: Restore Started

17:19:38 (275.xxx) Media id TB2560 is needed for the restore.

17:19:39 (275.001) Restoring from copy 1 of image created 12/30/2012 6:26:03 PM

17:19:39 (275.001) Status of restore from copy 1 of image created 12/30/2012 6:26:03 PM = server not allowed access

17:19:39 (275.001) The following files/folders were not restored:

17:19:39 (275.001) UTF - /FSONE/BGS_MT_HELPDESK/MIS/

17:19:40 (275.xxx) INF - Status = NDMP policy restore error.

Logs From Job details in activity monitor:

12/12/2013 5:19:38 PM - begin Restore

12/12/2013 5:19:38 PM - media TB2560 required

12/12/2013 5:19:38 PM - restoring image XXXXXXXXXX_1356872163

12/12/2013 5:19:39 PM - Info bprd(pid=6516) Restoring from copy 1 of image created 12/30/12 18:26:03    

12/12/2013 5:19:40 PM - end Restore; elapsed time: 00:00:02

NDMP policy restore error(2813)

[Marianne]

Your catalog export and import method will still have original media server as owner of backup image.

You need to add 'Media Host Override' in Host properties -> master -> General Server on new master server.

[Ramkumar_S]

Hi Marianne,

 I have already added those entry in my Master server Host properties and restarted the NetBackup services.

Eventhough the Restoration got failed.

[mnolan · Accepted solution]

Here is what I see from your bprd log.

17:19:39.845 [6516.6312] <2> ConnectToBPCD: bpcd_connect_and_verify(ctsintbmsfbc.cts.com, ctsintbmsfbc.cts.com) failed: 46
17:19:39.845 [6516.6312] <2> start_brm: BPCD on ctsintbmsfbc.cts.com exited with status 46: server not allowed access

Is ctsintbmsfbc.cts.com the old media server?

If so, run

bpimage -newserver newmediaservername  -backupid CTSINTBMCELB_1356872163

If ctsintbmsfbc.cts.com is the media server in this environment, then it seems it may not have the master servers name listed in the bp.conf (or the name seen on the interface the master would be communicating to the media server via).  If the bp.conf does not list the first server as the master, add it.  If that is already set, then check the bpcd log on the media server to see what name is coming across from the master.  This could be added as another server as well or looked into further from a name resolution side to see if that is correct or not.