Preparing your system for integration

Deployment options: Netezza Performance Server for Cloud Pak for Data System

Learn how to prepare Netezza Performance Server for integration with NetBackup.

Procedure

  1. Obtain the external DNS name and or external IP address of the Netezza Performance Server host.
  2. Replace the HOSTNAME value in /nz/data/config/backupHostname.txt with the DNS name or external IP address.
  3. Open the 1556,13782, and 13724 NetBackup TCP ports on the Netezza Performance Server client.
    The Netezza Performance Server client must be able to communicate with the NetBackup server for backup and restore operations.
    From Veritas NetBackup 8.1 and later, you can open only port 1556 to establish communication between the client and server.
    Note: Only one Netezza Performance Server instance per Cloud Pak for Data System can be set up this way.
    1. On a bare metal node, open /etc/firewalld/zones/appliance.xml and add the TCP ports if they are not already available.
      <!--NETBACKUP-->
      <port protocol="tcp" port="13782"/>
      <port protocol="tcp" port="1556"/>
      <port protocol="tcp" port="13724"/>
    2. Restart the firewall service.
      systemctl restart firewalld
  4. Install the NetBackup client software on the Netezza Performance Server host.
    Tip: To check the version and release date of the NetBackup software, view the /usr/openv/netbackup/bin/version file.
  5. Set the CLIENT_CONNECT_TIMEOUT and CLIENT_READ_TIMEOUT variables in /usr/openv/netbackup/bp.conf to 18000. If the variables are not in the file, add them.
    CLIENT_CONNECT_TIMEOUT = 18000
    CLIENT_READ_TIMEOUT = 18000
    Tip: The timeout settings are important. If a database restore fails with the following error, the problem can be that CLIENT_READ_TIMEOUT on the NetBackup server expired before the restore finished.
    Connector exited with error: 'ERROR: NetBackup getObject() failed with 
    errorcode (-1): Server Status: Communication with the server has not been
    initiated or the server status has not been retrieved from the server

    This error can occur when you are restoring a database that contains many tables with small changes. For example, frequent incremental backups, or a database that contains many objects such as UDXs, views, or tables.

    If your restore fails with this error, you can do one of the following actions:
    • Increase the CLIENT_READ_TIMEOUT value on the NetBackup server.
    • Specify certain options when you create the database backup.

      For example, when you create the database backup, you can specify a multi-stream backup by using the nzbackup -streams num option. You can also reduce the number of files that are committed in a single transaction by using the nzbackup -connectorArgs "NBC_COMMIT_OBJECT_COUNT=n" option.

    Use either or both options to avoid the timeout error. You might see this error message for other reasons, so if this workaround does not resolve the issue, contact support for assistance.

  6. Make sure that the backups that are done by one host are visible to another host.
    For example, if you have a Netezza Performance Server HA environment, the backups that are performed by Host1 must be visible to Host2.
    • You can open access to all hosts by updating the timestamp on the following file on the NetBackup main server.
      touch /usr/openv/netbackup/db/altnames/No.Restrictions

      If the touch command fails, make sure that the altnames directory exists. If necessary, create the altnames directory and rerun the command.

    • You can give Host1 access to all backups created by Host2, and Host2 access to all backups created by Host1 by updating the timestamp on two files:
      touch /usr/openv/netbackup/db/altnames/host1 
      touch /usr/openv/netbackup/db/altnames/host2
      For example, if the names of your HA hosts are nps10200-ha1 and nps10200-ha2, you would create the following files:
      touch /usr/openv/netbackup/db/altnames/nps10200-ha1
      touch /usr/openv/netbackup/db/altnames/nps10200-ha2
    Important: You must use one of the two previous methods to open access. If you skip this step, your restore does not work correctly on an HA system. This also applies to redirected restores.