firewall issues - Veritas Net Backup

This is a discussion on firewall issues - Veritas Net Backup ; Initiating a database backup from a client behind firewall using the SQL Backtrack netbackup OBSI module. This backup should go to jukebox attached to master server (not behind firewall). Regular UNIX filesystem dumps of the client initiated from the master ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: firewall issues

  1. firewall issues


    Initiating a database backup from a client behind firewall using the SQL Backtrack
    netbackup OBSI module. This backup should go to jukebox attached to master
    server (not behind firewall). Regular UNIX filesystem dumps of the client
    initiated from the master are fine, but db backups initiated from client
    are getting "exit status code 54 - timed out connecting to client".
    current firewall rules are as follows:
    Bidirectional TCP 512-1024 traffic between master and client
    One Way TCP 13782 from master to client
    One way TCP 13720 from client to master

    Trying to determine what other ports need to be opened.

    thnxs


  2. Re: firewall issues


    "Reggie" wrote:
    >
    >Initiating a database backup from a client behind firewall using the SQL

    Backtrack
    >netbackup OBSI module. This backup should go to jukebox attached to master
    >server (not behind firewall). Regular UNIX filesystem dumps of the client
    >initiated from the master are fine, but db backups initiated from client
    >are getting "exit status code 54 - timed out connecting to client".
    >current firewall rules are as follows:
    >Bidirectional TCP 512-1024 traffic between master and client
    >One Way TCP 13782 from master to client
    >One way TCP 13720 from client to master
    >
    >Trying to determine what other ports need to be opened.
    >
    >thnxs
    >


    Reggie,

    I had a similar issue. The problem turned out to be that the client could
    not resolve the name or IP of the media server making the request. That's
    because even though the client and media server shared a -bak backup network,
    the authentication requests go over the front-end and the client's front-end
    was pointing to a different DNS server than the backup server was. Since
    the resolution could not occur, the handshake could not be completed and
    the backup failed.

    So log in to the client and see if you can resolve the media server's name
    and IP. Furthermore, go in to

    /usr/openv/netbackup/bin

    and run

    bpclntcmd -pn

    bpclntcmd -hn media_server_name

    bpclntcmd -ip media_server_IP

    and make sure the results come back positive.


    Scott

+ Reply to Thread