Forum Discussion

perez_cmz's avatar
perez_cmz
Level 6
7 years ago

SQL restore from client failed

Getting the following message on a newly built server; os backup completes successfully

Error initializing NetBackup Catalog. This could be caused by a missing or expired NetBackup license key

  • Apologies, I was not alerted to everyones response. It seems the issue for me was the way SQL was installed on our server build image

6 Replies

  • OS backup is different. Comms is initiated by the media server. Database backup and restore comms is initiated by the client.
    Client needs to connect via pbx to bprd on the master server.

    Check forward and reverse name lookup between master and client as well as connectivity on port 1556 in both directions.
    • Michael_G_Ander's avatar
      Michael_G_Ander
      Level 6

      Can you do a file restore initiated from the client ?

      Are there any dedicated firewalls in the path ?  If that is the case, you often need any port -> pbx (1556) rules in both directions in my experience.

      Is the client set allowed to browse in the client attributes in the master server properties ? (It will need to have both browse and restore permissions to be able to restore SQL)

  • 1) verifiy name resolution between Master & client.

    ALso confirm SQL backups for these databases are working fine?

    Is it restore on same client or alternate client ?

    Check Dbclient, bpcd logs on client and bprd logs on matser server.

    Also check if client has permission to browse and restore data.

    Use following command to verify it : 

    /usr/openv/netbackup/bin/admicmd/bpclient -client client_name -L

    inoutput following two must be allowed.

    Free Browse: Allow
    List Restore: Allow Both

     

    if it is not there then, try /usr/openv/netbackup/bin/admicmd/bpclient -client client_name -list_restore 1

    Then try restor

      • perez_cmz's avatar
        perez_cmz
        Level 6

        Apologies, I was not alerted to everyones response. It seems the issue for me was the way SQL was installed on our server build image