Forum Discussion

Arshad_Khateeb's avatar
Arshad_Khateeb
Level 5
7 years ago

Oracle database restore fail

We are trying to restore oracle database from one server to another. It all starts well but this is where it stuck.

Error bpbrm (pid=11257) cannot get server's peername on client rome_pres-bu
Error bpbrm (pid=11257) listen for client protocol error - couldn't write necessary information on /usr/openv/netbackup/logs/user_ops/dbext/logs/10774.0.1517947887

  • Arshad_Khateeb's avatar
    Arshad_Khateeb
    7 years ago

    And here is the fix that worked.....

    After plenty of troubleshooting it was found that the DBA were not using same dbid as of source client in the restore script on destination client. Also the SID was incorrect. The restore is running smooth at the moment.

    The DBA is moving to Oracle 12c and proposing to do backups their own instead of using NetBackup so that they can have control on their own on backup/restore. They are little nervous with the restore issue but it's completely due to their poor script.

    What are the benefits of using NetBackup for Database backups (to tape/disk) against DBA doing their own? This will help me talk about NetBackup in our upcoming meeting with them.

19 Replies

Sort By
Replies have been turned off for this discussion
  • Amol_Nair's avatar
    Amol_Nair
    Level 6
    7 years ago
    What is the nbu version on master and client?
    Is the restore of the control file done and then reporting this message while restoring the database or the control file restore itself seems to be reporting it..

    Please do verify basic connectivity from master to client as well as client to master and of there is a separate media server involved then the media to client and voce versa as well..

    Please provide us with more inputs as to the commands used to for the restore..

    Since this is as alternate client restore have you changed the client_name in the bp.conf file? And hope you are providing appropriate names in the send parameters used in the restore script
    • Arshad_Khateeb's avatar
      Arshad_Khateeb
      Level 5
      7 years ago

      We are running with older version of NetBackup 6.5.6 on master, media and client.

      Connectivity looks good from all side. Yes, we are restoring to different client and using different media server. We have changed client name on destination server with the name of original server and tried but all different attempts comes to an end at the error mentioned in my previous post.

      Restore RMAN script is created by DBA guys and we have configured policy to call that script.

      • Amol_Nair's avatar
        Amol_Nair
        Level 6
        7 years ago
        6.5...
        Its been ages that version ran out of support.. Why wasn’t nbu upgraded.. so now you can’t even reach out to us with a support case

        could we get the details of the script used by your DBA.. I would be more interested on the send parameters they are using..

        Since you mentioned that it is a different media server as well did you verify connectivity from the media server to the client as well.. hope it wasn’t just a simple ping command that you used and concluded that connectivity is good but also verified forward and reverse lookups and whether ports are open bidirectionally